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.
The latest update from Aiven.
State
Resolved
Started
33 d ago
2026-09-29 20:14 UTC
Lasted
4 h 27 min
until 2026-09-30 00:41 UTC
Worst impact
Notice
Timeline
5 updatesInvestigating
1 h 45 min 39%
Identified
2 h 31 min 57%
Monitoring
11 min 4%
Updates
Times in UTCAs posted by Aiven
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.
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.
PostgreSQL major version upgrades can be performed again. A small number of services affected by an earlier failed upgrade are now being repaired. We will contact customers directly if any action is needed on their side, and we'll post another update here once the repairs are complete.
We have a mitigation that we are rolling out for the issue affecting Major version upgrade on Aiven for PostgreSQL services. Please continue to refrain from triggering major version upgrades for the moment. Affected services are being restored as the mitigation is deployed. We will provide further updates as the rollout progresses. We apologize for the inconvenience.
We are currently investigating an issue affecting Aiven for PostgreSQL services, where a major version upgrade can leave the service in an unusable state. We advise customers not to initiate a PostgreSQL major version upgrade at this time. If you have already started a major version upgrade and your service is not responding, please contact our support team at support@aiven.io. Our engineering teams are actively working to identify the root cause and restore affected services. We will provide further updates as soon as more information is available. We apologize for the inconvenience.
Aiven in the last 90 days
Full historyIncidents in 90 days
9
Days with an incident
25
Median duration
9 h 1 min
This incident
51% shorter than the median
Other Aiven incidents
All incidentsAiven·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.
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.
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.
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.
Aiven·Aiven Console and API are down
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)
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.
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.
https://outages.cc/feed.xml?providers=aiven/feed subscribe https://outages.cc/feed.xml?providers=aivenFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane