Skip to main content
Aiven

API requests failing/timing out

Degraded Lasted 16h 40m · started · Aiven's page

Level
confirmed
Worst impact
Degraded
Down Index
31of 100

Summary

Aiven says that timeouts and 500 errors occurred when accessing its APIs, starting 2026-11-05 at 11:59 UTC. It says the issue was mitigated at 12:51 UTC and a permanent fix was deployed; the incident is marked resolved as of 2026-11-06 at 04:39 UTC.

Written by anthropic/claude-haiku-5.5 from Aiven's own updates.

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 16h 40m it lasted.

    Anything that failed between 2026-11-05 11:59 UTC and 2026-11-06 04:39 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. investigating

    You may experience timeouts and 500 errors when accessing Aiven APIs. We're currently investigating API performance to mitigate the issue.

    provider

  2. identified

    The issue has been mitigated, and our Engineering team is working on a permanent fix.

    provider

  3. resolved

    A permanent fix for the issue has been deployed. Should any further issues be encountered, please reach out to support via the Aiven console. We apologise for the inconvenience caused by this problem.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

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

Questions about DWN-8e87f49d7a

Is Aiven still down?

No, this incident was resolved 2026-11-06 04:39 UTC. For Aiven's live state, see https://down.guide/aiven.

How long did it last?

16h 40m, from 2026-11-05 11:59 UTC to 2026-11-06 04:39 UTC, by the times Aiven posted.

What caused it?

Aiven hasn't published a root cause. If it does, it shows here.

Where does this come from?

Aiven's official status page, https://status.aiven.io, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.