Aiven experienced a minor incident on September 30, 2026, lasting —. The incident has been resolved; the full update timeline is below.
Update timeline
- investigating Sep 29, 2026, 08:14 PM UTC
Status: Investigating 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 [email protected]. 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.
- identified Sep 29, 2026, 09:59 PM UTC
Status: Identified 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.
- identified Sep 29, 2026, 11:50 PM UTC
Status: Identified 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.
- monitoring Sep 30, 2026, 12:30 AM UTC
Status: Monitoring 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.
- resolved Sep 30, 2026, 12:41 AM UTC
Status: Resolved 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.