Availability affected for some PG read replica nodes.

What to do

• Check whether your product depends on Aiven. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 1h 59m it lasted.

  Anything that failed between 2025-11-24 03:39 UTC and 2025-11-24 05:38 UTC may need a replay.

• Subscribe to Aiven's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=aiven works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Aiven 3

1. investigatingNov 24, 2025, 3:39 AM UTC

   We are currently investigating an issue affecting the availability of some PostgreSQL read-replica nodes. A mitigation procedure is being applied to affected services, while we continue investigating the root cause. We will provide status updates for this incident as more information becomes available.

   provider

2. monitoringNov 24, 2025, 4:51 AM UTC

   The root cause for the issue was identified (some credentials were disabled as part of a previous incident). After enabling the credentials back there is no PG replicas reporting the issue. If you find any problem with your PG replicas please contact Aiven support.

   provider

3. resolvedNov 24, 2025, 5:38 AM UTC

   We have confirmed that the incident has been resolved, and all the PG replicas are operating normally. We apologise for the inconvenience caused by this issue.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.