Aiven reported "Aiven Console and API are down" on its status page at 2026-09-22 00:55 UTC.

Aiven did not name the affected components. The updates on this page have the details.

When did the incident start and end?

It started at 2026-09-22 00:55 UTC and ended at 2026-09-22 08:05 UTC. It lasted 7 h 10 min.

How do I get alerts for Aiven?

Subscribe to the Aiven live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of Aiven. outages.live reads it every few minutes and keeps every update.

AivenIncident · 2026-09-22 00:55 UTC

Aiven Console and API are down

ResolvedOfficial update

This incident is now resolved. Earlier today a certificate problem affecting our public API endpoints caused sign-in failures and errors for customers using the Aiven Console, the Aiven API, the CLI, the Terraform provider and other API-based integrations. A corrected certificate has been in place across all API nodes since 02:05 UTC, and we have seen no further errors during our monitoring period. We are following up with a permanent fix to prevent this from recurring. We apologize for the disruption. If you are still seeing problems, please contact Aiven support at [support@aiven.io](mailto:support@aiven.io)

The latest update from Aiven.

State

Resolved

Started

41 d ago

2026-09-22 00:55 UTC

Lasted

7 h 10 min

until 2026-09-22 08:05 UTC

Worst impact

Partial outage

Timeline

5 updates

00:5502:4204:3006:1708:05

Partial outageUpdate postedTimes in UTC

Investigating

1 h 34 min 22%

Identified

3 h 25 min 48%

Monitoring

2 h 11 min 30%

Updates

Times in UTC

As posted by Aiven

Resolved2026-09-22 08:05 UTC

Monitoring2026-09-22 05:54 UTC

This incident is now resolved. Between approximately 00:10 and 02:05 UTC on 22 September, an issue affecting our public API endpoints caused sign-in failures and errors for customers using the Aiven Console, the Aiven API, the CLI, the Terraform provider and other API-based integrations. The issue was corrected and we have seen no further errors during our monitoring period. We are following up with additional changes to prevent this from recurring. We apologise for the disruption. If you are still seeing problems, please contact Aiven support.

Identified2026-09-22 03:36 UTC

The rollout of the fix is still progressing across our API nodes. Most customers should now find the Aiven Console, API, CLI and Terraform provider working normally, and we expect any remaining errors to clear as the rollout completes. We will confirm here once it is complete. Thank you for your patience.

Identified2026-09-22 02:28 UTC

We have identified the cause of this issue and a fix is now being rolled out across our API nodes in stages. The Aiven Console and API are already working again for some customers. Until the rollout completes you may still see intermittent sign-in failures, or errors when creating, modifying or querying services via the Console, CLI, Terraform provider or direct API calls. Retrying will often succeed. We will confirm here once the rollout is complete. Thank you for your patience.

Investigating2026-09-22 00:55 UTC

We are aware of an issue affecting the Aiven API. The Aiven Console, the Aiven CLI, the Terraform provider and any custom scripts or integrations all run through this same API, so customers may see errors across any of them. You may experience being unable to load or sign in to the Console, and failures when creating, modifying or querying services. Our engineering team is investigating and work to restore service is underway. We will provide a further update within 30 minutes, or sooner if there is news to share. We apologise for the disruption.

Aiven in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

9 h 1 min

This incident

20% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

14 days

median 9 h 1 min

90 days agoToday

Other Aiven incidents

All incidents

Aiven·Google Cloud VPN incident affecting services

This incident has been resolved. A power outage in Google Cloud's europe-west2-b zone disrupted services running in the europe-west2 region. Nodes in the affected zone were rebooted when the zone recovered. Some affected Aiven for Apache Kafka, Aiven for OpenSearch, Aiven for PostgreSQL and Aiven for Valkey services needed extra recovery steps or node replacement before they returned to normal operation. All affected services have now been restored. We apologise for the disruption.

Resolvedresolved 12 d ago

Aiven·Unable to spin up nodes in vultr-ewr

We have resolved the underlying issues of nodes creation and replacement in the **vultr-ewr** cloud region. Should any further issues be encountered, please reach out to support via the Aiven console. We apologise for the inconvenience caused by this issue, and commit to analysing and improving our platform to avoid future incidents similar to this one.

Resolvedresolved 14 d ago

Aiven·Issues starting new service nodes

This incident has been resolved. New service nodes are able to start normally again, and running nodes were not affected at any point during the incident. We apologize for any inconvenience this may have caused.

Resolvedresolved 16 d ago

Aiven·Issues with spin up node in google asia-southeast1 region

We have resolved the underlying cause of this issue in Google's asia-southest1 region. Should any further issues be encountered, please reach out to support via the Aiven console. We apologise for the inconvenience caused by this issue.

Resolvedresolved 16 d ago

Aiven·Issue with PostgreSQL major version upgrade

All customer services affected by this issue have been restored, and no further action is needed on your side. It is now safe to proceed with PostgreSQL major version upgrades. We apologise for the disruption this caused.

Resolvedresolved 33 d ago

Follow Aiven

Your coding agent knows when Aiven is down, and tells you when a failure is theirs, not yours. You can also get Aiven incidents in a feed reader or in Slack.

Prompt

Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "aiven" and tell me if Aiven has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS

https://outages.cc/feed.xml?providers=aiven

Slack

/feed subscribe https://outages.cc/feed.xml?providers=aiven

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane