Aiven Outage History

26 incidents recorded over the last 365 days, 26 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Aiven status99.20% uptime history

Every Recorded Aiven Incident

Aiven incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Aug 8, 2026Delayed VM CreationNew VM creation has returned to normal across all cloud providers, including DigitalOcean. * VM provisioning is operating normally across all regions. * The upstream DigitalOcean incident has been resolved. * We are…9h 0mResolved
Jul 29, 2026Aiven Dynamic Disk Sizing (DDS) failuresOur team has successfully applied the appropriate mitigation to all impacted nodes, and the fix has been deployed to prevent future occurrences.2h 37mResolved
Jul 2, 2026Delayed Service Operations Affecting All Cloud Providers (MySQL Unaffected)We have resolved the underlying cause of this issue. 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…6h 3mResolved
Jun 25, 2026Terraform & Kubernetes operators - List Databases API Error (400)The issue has been resolved. Terraform & Kubernetes operator users should no longer experience `400` errors when using `aiven_pg_database`. We apologize for any inconvenience caused.2h 58mResolved
Jun 23, 2026Kafka upgrade to 3.9 pausedThe issues affecting KRaft migrations during Kafka 3\.8 to 3\.9 upgrades have been resolved. Fixes have been deployed, migrations have been re-enabled, and services have remained stable during monitoring. If you are…45h 19mResolved
Jun 11, 2026Kafka upgrades to 3.9 are pausedThe issue has been resolved. All affected functionality is operating normally.115h 40mResolved
Jun 9, 2026Backup and restore failures affecting some Aiven for PostgreSQL servicesThe monitoring period has passed without further evidence of the issue occurring. Incident has been declared resolved.1h 47mResolved
May 25, 2026Service operations affected in AzureWe have resolved the underlying cause of the issue affection service operations in our Azure regions. Should any further issues be encountered, please reach out to support via the Aiven console. We apologise for the…1h 25mResolved
May 20, 2026Issue affecting services in DigitalOcean NYC3 regionThis issue is now resolved. Should any further issues be encountered, please reach out to support via the Aiven console. We apologise for the inconvenience caused by this issue.1h 23mResolved
May 14, 2026Multiple Aiven for Apache Kafka services experiencing disruptionWe have resolved the underlying cause of the kafka service disruption. Should any further issues be encountered, please reach out to support via the Aiven console. We apologise for the inconvenience caused by this…40h 18mResolved
Mar 1, 2026Amazon Web Services (AWS) ME-CENTRAL-1 and ME-SOUTH-1 region statusThe underlying issues with Amazon Web Services (AWS) in the **ME-CENTRAL-1** and **ME-SOUTH-1** regions are ongoing, and AWS continues to work on recovery. We have disabled the creation of new services and nodes in…756h 10mResolved
Dec 12, 2025Delays in Service Provisioning on UpCloudThe issue affecting node creation on the UpCloud cloud platform has been fully resolved. New services and replacement nodes are now provisioning successfully across all UpCloud regions. Our engineering team has…122h 25mResolved
Dec 8, 2025Delay for new nodes coming onlineWe are confirming that the platfom has remained **stable** following the resolution of the DNS update performance issue, and the system is handling expected load variations well. We are now closing the incident after…16h 52mResolved
Dec 5, 2025Investigating connectivity issues in Azure Norway West regionWe have confirmed that all the Aiven services running on the Microsoft Azure region are operational. If you face any further issues please contact Aiven support.20h 15mResolved
Dec 4, 2025Metrics API OutageThe issue affecting metrics retrieval has been fully resolved. All metrics APIs and the Metrics page in the console should now be functioning normally. If you continue to experience any problems, please reach out to our…2h 5mResolved
Nov 24, 2025Availability affected for some PG read replica nodes.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.1h 59mResolved
Nov 19, 2025Issue preventing power on of PostgreSQL servicesWe have identified a mitigation to resolve the issues causing PostgreSQL services not being able to be powered on after being powered off. We are continuing to monitor closely to ensure no further problems. We…2h 2mResolved
Nov 18, 2025Aiven Console and aiven.io downCloudflare has resolved the issues on their side and our platform has returned to normal operation. No impact was observed on any running services. Should any further issues be encountered, please reach out to support…6h 57mResolved
Nov 6, 2025PostgreSQL nodes unable to startThe root cause of this incident has been fixed. All impacted PostgreSQL 18 nodes are operating normally. We apologize for any inconvenience this may have caused. If you continue to experience any issues with your…3h 11mResolved
Oct 31, 2025Multiple service types cannot start**Resolved** -  The issue with starting up new nodes has been resolved, and all services are now operating normally. We apologize for any inconvenience this may have caused.2h 3mResolved
Oct 29, 2025Nodes struggling to spin in BYOC environmentsRESOLVED: We have identified and applied a fix for the issue where services in BYOC environments were struggling to spin up new nodes. All affected services should now be able to create and rebalance nodes normally.4h 13mResolved
Oct 20, 2025New services or replacement nodes can not be created in AWS us-east-1 (United States, Virginia) due to an AWS outage.AWS has recovered and declared their incident as resolved. See the AWS status page for a timeline on the issue: [https://health.aws.amazon.com/health/status](https://health.aws.amazon.com/health/status…14h 26mResolved
Oct 17, 2025Issue affecting several servicesDigital Ocean Engineering team has confirmed that the IPv6 connectivity issue has been fully resolved across all regions. Users should no longer face IPv6 connectivity issues. If you continue to experience problems…4h 36mResolved
Sep 30, 2025Customer using legacy MD5 password cannot connect through pgbouncerWe have resolved the underlying cause of issue affecting our customers using legacy MD5 password cannot connect through pgbouncer. Should any further issues be encountered, please reach out to support via the Aiven…8h 0mResolved
Sep 26, 2025Delay in service user logsService user logging pipelines are now operating as per normal. If you continue to experience delays, please reach out to Aiven Support.4h 15mResolved
Sep 17, 2025Issues with the privatelink-availability APIWe have resolved the underlying cause of effecting our privatelink-availability API. Should any further issues be encountered, please reach out to support via the Aiven console. We apologise for the inconvenience…1h 44mResolved

How to Read This Aiven Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Aiven acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Aiven outage in this window ran 31d 12h, against a mean recovery of 1d 22h. If you depend on Aiven in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.