https://approjects-vendor-status-watch.static.hf.space/v/aiven.htmlIncidents from Aiven's public status page, polled daily.Wed, 16 Sep 2026 12:28:20 +0000https://status.aiven.ioaiven:2026-09-16T12:21:27ZWed, 16 Sep 2026 12:21:27 +0000We are investigating issues with creating new nodes for services on the Aiven platform currently. The effect is slower creation time for new nodes. Any any event where a new node is created are impacted such as failovers, switchovers, upgrades and maintenance updates. Our engineers are currently investigating the root cause and working on a fix for the issue. We apologise for the inconvenience caused by this issue. We will provide a further update as our team continues on the solution for this situation.https://status.aiven.ioaiven:2026-08-08T21:28:11ZSat, 08 Aug 2026 21:28:11 +0000New 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 continuing to monitor the infrastructure to ensure stable provisioning. The incident is now resolved. Thank you for your patience.https://status.aiven.ioaiven:2026-07-29T14:29:15ZWed, 29 Jul 2026 14:29:15 +0000Our team has successfully applied the appropriate mitigation to all impacted nodes, and the fix has been deployed to prevent future occurrences.https://status.aiven.ioaiven:2026-07-02T23:24:59ZThu, 02 Jul 2026 23:24:59 +0000We 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 analysing and improving our platform to avoid future incidents similar to this one.https://status.aiven.ioaiven:2026-06-25T10:16:16ZThu, 25 Jun 2026 10:16:16 +0000The 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.https://status.aiven.ioaiven:2026-06-23T14:18:37ZTue, 23 Jun 2026 14:18:37 +0000The 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 experiencing any issues, please contact support.https://status.aiven.ioaiven:2026-06-11T15:25:40ZThu, 11 Jun 2026 15:25:40 +0000The issue has been resolved. All affected functionality is operating normally.https://status.aiven.ioaiven:2026-06-09T15:10:00ZTue, 09 Jun 2026 15:10:00 +0000The monitoring period has passed without further evidence of the issue occurring. Incident has been declared resolved.https://status.aiven.ioaiven:2026-05-25T02:29:06ZMon, 25 May 2026 02:29:06 +0000We 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 inconvenience caused by this issue, and commit to analysing and improving our platform to avoid future incidents similar to this one.https://status.aiven.ioaiven:2026-05-20T01:15:06ZWed, 20 May 2026 01:15:06 +0000This 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.https://status.aiven.ioaiven:2026-05-14T06:55:15ZThu, 14 May 2026 06:55:15 +0000We 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 issue, and commit to analysing and improving our platform to avoid future incidents similar to this one.https://status.aiven.ioaiven:2026-03-01T23:12:45ZSun, 01 Mar 2026 23:12:45 +0000The 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 the affected regions to prevent further impact. We recommend our customers to migrate their services to a stable region as part of their disaster recovery plan. As there are no further actions we can take at this time, we are moving this incident to a resolved state on our status page. The recovery of these regions is fully dependent on AWS. We will make **ME-CENTRAL-1** and **ME-SOUTH-1** regions available again for Aiven services once AWS confirms they are fully restored and stable. We recommend customers continue to monitor the official AWS Health Status Page for updatehttps://status.aiven.ioaiven:2025-12-12T11:33:23ZFri, 12 Dec 2025 11:33:23 +0000The 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 completed all remediation steps and confirmed the stability of the platform.https://status.aiven.ioaiven:2025-12-08T03:48:30ZMon, 08 Dec 2025 03:48:30 +0000We 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 extended monitoring.https://status.aiven.ioaiven:2025-12-05T07:19:24ZFri, 05 Dec 2025 07:19:24 +0000We 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. https://status.aiven.ioaiven:2025-12-04T17:12:15ZThu, 04 Dec 2025 17:12:15 +0000The 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 support team and we’ll be happy to assist.https://status.aiven.ioaiven:2025-11-24T03:39:21ZMon, 24 Nov 2025 03:39:21 +0000We 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.https://status.aiven.ioaiven:2025-11-19T22:05:11ZWed, 19 Nov 2025 22:05:11 +0000We 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 apologise for the inconvenience caused by this issue. https://status.aiven.ioaiven:2025-11-18T12:08:38ZTue, 18 Nov 2025 12:08:38 +0000Cloudflare 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 via the Aiven console.https://status.aiven.ioaiven:2025-11-06T04:24:09ZThu, 06 Nov 2025 04:24:09 +0000The 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 PostgreSQL services, please contact our support team for assistance.https://status.aiven.ioaiven:2025-10-31T11:32:28ZFri, 31 Oct 2025 11:32:28 +0000**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.https://status.aiven.ioaiven:2025-10-29T17:04:42ZWed, 29 Oct 2025 17:04:42 +0000RESOLVED: 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.https://status.aiven.ioaiven:2025-10-20T09:30:50ZMon, 20 Oct 2025 09:30:50 +0000AWS 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 "https://health.aws.amazon.com/health/status") Should any further issues be encountered, please reach out to support via the Aiven console.https://status.aiven.ioaiven:2025-10-17T00:29:08ZFri, 17 Oct 2025 00:29:08 +0000Digital 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, please open a ticket with support team. Thank you for your patience and we apologize for any inconvenience.https://status.aiven.ioaiven:2025-09-30T21:47:50ZTue, 30 Sep 2025 21:47:50 +0000We 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 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.https://status.aiven.ioaiven:2025-09-26T01:49:29ZFri, 26 Sep 2025 01:49:29 +0000Service user logging pipelines are now operating as per normal. If you continue to experience delays, please reach out to Aiven Support.