Aiven

Failure mode: A zone, region or data center became unavailable. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

Started during Google Cloud: Multiple services are experiencing issues in the europe-west2 region..

1. investigating 2026-10-20 06:43 UTC

   We are investigating an ongoing Google Cloud VPN incident affecting the europe-west2 and africa-south1 regions. This is impacting network connectivity between nodes and may affect the availability and performance of clustered Aiven services in the affected regions. Our team is...

2. investigating 2026-10-20 06:51 UTC

   We are investigating an ongoing Google Cloud networking incident. Google Cloud engineers have confirmed an issue with Virtual Private Cloud (VPC) networking affecting communication between virtual machines, including communication over internal IP addresses, IPv6, and other...

3. investigating 2026-10-20 08:44 UTC

   The latest information identifies europe-west2 and the europe-west2-b zone as affected locations. The incident involves Virtual Private Cloud (VPC) networking issues that can disrupt communication between virtual machines. This may affect connectivity between nodes and the...

4. investigating 2026-10-20 11:10 UTC

   The latest information identifies `europe-west2` and the `europe-west2-b` zone as affected locations. The incident involves Virtual Private Cloud (VPC) networking issues that are disrupting communication between virtual machines in the affected location, which is impacting the...

5. investigating 2026-10-20 14:10 UTC

   We are continuing to respond to the Google Cloud incident affecting the europe-west2 region. The underlying Google Cloud issue — a power outage in the europe-west2-b zone has been mitigated by Google, and recovery of most workloads has been in progress since 15:10 EEST. Services...

6. monitoring 2026-10-20 18:10 UTC

   All PG and Kafka services known to be affected by the Google Cloud incident in europe-west2 have been recovered. We are currently recovering and fixing known Opensearch services. We are continuing to monitor all services in the region to confirm they remain healthy. If you are...

7. monitoring 2026-10-20 18:55 UTC

   All Aiven services known to be affected by the Google Cloud incident in europe-west2 have been recovered. After Google mitigated the power outage in the europe-west2-b zone, we restored the affected Aiven for Apache Kafka, Aiven for OpenSearch and Aiven for PostgreSQL services...

8. resolved 2026-10-20 19:30 UTC

   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...

Excerpts are shortened. Read the full incident on Aiven's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-18 10:54 UTC

   Creation and replacement of nodes in the **vultr-ewr** cloud region are experiencing issues and may take longer than normal to come up. Services that are already running are not affected. Our engineering team is actively working on this, and we will provide another update as...

2. resolved 2026-10-19 04:06 UTC

   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...

Excerpts are shortened. Read the full incident on Aiven's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-16 08:40 UTC

   We are currently experiencing an issue with starting new service nodes for almost all service types. The running nodes are not affected. Our engineering team is actively working on a fix and we will provide another update as soon as we have more information.

2. monitoring 2026-10-16 09:56 UTC

   A fix has been implemented and we are currently monitoring the results. New service nodes are able to start again, and running nodes were not affected at any point. We will provide further updates once we have confirmed the issue is fully resolved.

3. resolved 2026-10-16 13:31 UTC

   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.

Excerpts are shortened. Read the full incident on Aiven's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

1. investigating 2026-10-12 00:04 UTC

   We have issues in the google asia-southeast1 region where we cannot spin up nodes. This is due to an upstream cloud provider issue that we are working on. We are currently investigating and will update further details in the next 30 minutes.

2. investigating 2026-10-12 03:09 UTC

   We are investigating an issue preventing node creation in asia-southeast1. The issue is only affecting some users. Engineering is actively engaged with GCP support. Next update in 30 minutes.

3. identified 2026-10-16 05:04 UTC

   We have identified the root cause of the issue preventing node creation in asia-southeast1. Our team is working with GCP to implement a fix. We will provide another update as soon as more information becomes available.

4. resolved 2026-10-16 14:38 UTC

   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.

Excerpts are shortened. Read the full incident on Aiven's status page.

Failure mode: A schema or data migration caused the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-29 20:14 UTC

   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...

2. identified 2026-09-29 21:59 UTC

   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...

3. identified 2026-09-29 23:50 UTC

   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...

4. monitoring 2026-09-30 00:30 UTC

   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.

5. resolved 2026-09-30 00:41 UTC

   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.

Excerpts are shortened. Read the full incident on Aiven's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-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...

2. identified 2026-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...

3. identified 2026-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....

4. monitoring 2026-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...

5. resolved 2026-09-22 08:05 UTC

   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...

Excerpts are shortened. Read the full incident on Aiven's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-21 04:57 UTC

   We are currently investigating reports of users being unable to log in to the Aiven console. We will share further updates as soon as possible.

2. investigating 2026-09-21 05:27 UTC

   We are still investigating an issue affecting the Aiven Console. Customers are currently unable to create or submit new support tickets directly through the portal. If you require assistance with an urgent issue unrelated to the Aiven Console being down, please send an email to...

3. monitoring 2026-09-21 06:01 UTC

   A fix has been deployed for Aiven Console and portal functionality is restored. We are currently monitoring performance. If you encounter any issues, please email [support@aiven.io](mailto:support@aiven.io)

4. resolved 2026-09-21 08:25 UTC

   This incident has been resolved. Aiven Console login and support ticket creation through the portal are fully functional again. We continued to monitor performance and have seen no further issues. If you encounter any problems, please email...

Excerpts are shortened. Read the full incident on Aiven's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-16 12:21 UTC

   We 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...

2. monitoring 2026-09-16 13:58 UTC

   We are monitoring our mitigating actions to issues with creating new nodes for services on the Aiven platform. Our engineers have done mitigating steps and we see improvements in the node creation, but we'll continue investigating and monitoring of the issue. We apologise for...

3. monitoring 2026-09-16 15:04 UTC

   We have completed our mitigating actions and the creation of new nodes for services on the Aiven platform has returned to normal. Customers can now proceed with any operations that were delayed during this issue, including service creation, scaling, upgrades, maintenance updates...

4. resolved 2026-09-30 06:35 UTC

   We have resolved the underlying cause of the new node creation and new nodes are able to be created without issues. 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...

Excerpts are shortened. Read the full incident on Aiven's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-08-08 21:28 UTC

   We are currently experiencing delays in the creation of new virtual machines, which may affect the provisioning of new services and nodes. An ongoing incident with an upstream cloud provider (DigitalOcean) is preventing new VM creation in all DigitalOcean regions. Additionally,...

2. investigating 2026-08-08 21:50 UTC

   New VM creation across most cloud providers is now recovering, and provisioning times are slowly returning to normal. Services that were previously delayed should now be creating successfully soon. **Current status** • **All clouds except DigitalOcean:** New VM creations are...

3. resolved 2026-08-09 06:28 UTC

   New 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...

Excerpts are shortened. Read the full incident on Aiven's status page.

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-29 14:29 UTC

   We are investigating an issue affecting Dynamic Disk Sizing (DDS), where resize operations may fail for a small subset of newly created nodes. Mitigations are currently underway.

2. identified 2026-07-29 15:17 UTC

   Issue has been identified and fixes are being applied. Thank you for your patience.

3. resolved 2026-07-29 17:07 UTC

   Our team has successfully applied the appropriate mitigation to all impacted nodes, and the fix has been deployed to prevent future occurrences.

Excerpts are shortened. Read the full incident on Aiven's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS, Azure, Google Cloud.

1. investigating 2026-07-02 23:24 UTC

   We are currently investigating an issue affecting services running on DigitalOcean that is causing delays in node lifecycle management. As a result, any operations on DigitalOcean-hosted services that require creating, deleting, or replacing nodes will experience delays....

2. investigating 2026-07-03 02:20 UTC

   We have identified that the previously reported issue affecting node lifecycle management is not isolated to a single cloud provider, but is currently affecting services across all cloud providers. As a result, any operations that require creating, or replacing nodes will...

3. monitoring 2026-07-03 04:56 UTC

   ``` We have implemented a mitigation for the infrastructure issue affecting node lifecycle management, and we are now seeing service operations return to normal. We are closely monitoring the platform to ensure stability. Pending operations such as service creations, deletions,...

4. resolved 2026-07-03 05:28 UTC

   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 analysing and improving our platform to avoid future incidents...

Excerpts are shortened. Read the full incident on Aiven's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-06-25 10:16 UTC

   We are currently investigating an issue affecting Terraform & Kubernetes operator users receiving `400` errors when using `aiven_pg_database`. This is impacting `aiven_pg_database` and potentially other service types. The root cause has been identified and a fix is in progress....

2. monitoring 2026-06-25 12:27 UTC

   A fix has been applied and the issue is expected to be resolved. We are continuing to monitor closely as we work to restore full system operation. We apologise for the inconvenience caused by this issue.

3. resolved 2026-06-25 13:14 UTC

   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.

Excerpts are shortened. Read the full incident on Aiven's status page.

Failure mode: A schema or data migration caused the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-06-23 14:18 UTC

   We have paused Kafka 3.8 ->3.9 upgrades as we are investigating an issue with KRaft migration during the upgrade. Aiven is actively monitoring affected services and applying mitigations where required. Impact: Existing Kafka services continue to run. Customers attempting to...

2. identified 2026-06-23 15:10 UTC

   We have identified two separate problems: • An issue in migration code • An [upstream bug](https://github.com/apache/kafka/pull/19854) We are working on the fix for the migration issue and back-porting the fix for the upstream bug. If you have any issues, please contact support.

3. identified 2026-06-24 15:01 UTC

   We have identified issues affecting KRaft migrations (Kafka 3.8 to 3.9 upgrades). We have paused all migrations while we work on a fix. If you are experiencing any issues, please contact support.

4. monitoring 2026-06-25 08:06 UTC

   We have deployed fixes for the issues affecting KRaft migrations during Kafka 3.8 to 3.9 upgrades, and migrations have been re-enabled. We are continuing to monitor the situation to ensure services remain stable. If you are experiencing any issues, please contact support.

5. resolved 2026-06-25 11:38 UTC

   The 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.

Excerpts are shortened. Read the full incident on Aiven's status page.

Failure mode: A schema or data migration caused the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-11 15:25 UTC

   We have identified an issue affecting KRaft migrations during Kafka upgrades to version 3.9, and have temporarily paused those upgrades while we investigate. If you try to upgrade now, your request will be rejected with an error asking you to contact support. We will re-enable...

2. monitoring 2026-06-15 14:01 UTC

   We have a fix prepared, which is currently undergoing final verification. If validation is successful, we will proceed with deployment shortly. As a result, the incident is now moving into a monitoring phase while we observe system stability after the changes. We will re-enable...

3. resolved 2026-06-16 11:05 UTC

   The issue has been resolved. All affected functionality is operating normally.

Excerpts are shortened. Read the full incident on Aiven's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-06-09 15:10 UTC

   Aiven engineers are currently investigating a bug on Aiven for PostgreSQL that causes affected cluster fail to take backups and restore from backup. Known affected clouds are AWS and DigitalOcean. Thank you for your patience as we continue our work on this incident.

2. identified 2026-06-09 15:57 UTC

   Our team has identified a potential root cause and is working to fix the issue on the affected services.

3. monitoring 2026-06-09 16:18 UTC

   The fix has been applied to the affected services, and Aiven will continue to monitor to confirm that no further action is needed. Thank you for your patience.

4. monitoring 2026-06-09 16:36 UTC

   Correction: Aiven for Apache Kafka services as well as Aiven for PostgreSQL services were affected. All services identified to have the issue have been fixed as per the previous status message.

5. resolved 2026-06-09 16:57 UTC

   The monitoring period has passed without further evidence of the issue occurring. Incident has been declared resolved.

Excerpts are shortened. Read the full incident on Aiven's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. investigating 2026-05-25 02:29 UTC

   We are experiencing an issue affecting service operations across Azure regions. While existing services remain up and running, operations such as service creation, plan changes, and scheduled maintenance are currently failing. We are actively working on a fix to restore full...

2. identified 2026-05-25 03:48 UTC

   ``` We have identified the root cause and are currently deploying a fix to resolve the issues affecting service operations across Azure regions.While existing services remain up and running, operations such as service creation, plan changes, and maintenance updates are currently...

3. resolved 2026-05-25 03:54 UTC

   We 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...

Excerpts are shortened. Read the full incident on Aiven's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-05-20 01:15 UTC

   ``` We are experiencing performance degradation and node unresponsiveness affecting some Aiven services hosted in the DigitalOcean NYC3 region.This is tied to an underlying infrastructure issue currently being tracked by our cloud provider. You can monitor their infrastructure...

2. resolved 2026-05-20 02:38 UTC

   This 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.

Excerpts are shortened. Read the full incident on Aiven's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-14 06:55 UTC

   ``` We are currently aware of an issue affecting Aiven for Kafka services. Our teams are currently investigating the root cause as a priority. We will continue to provide status updates as they become available. ```

2. identified 2026-05-14 07:36 UTC

   We have identified the root cause of the issue affecting multiple Aiven for Apache Kafka services and are currently working to restore the affected services. Our teams are actively applying fixes and will continue to provide updates as progress is made.

3. monitoring 2026-05-14 10:49 UTC

   ``` We have applied a fix to the affected services and are seeing recovery progress. Our team is closely monitoring the platform and will continue to mitigate any remaining impact if needed. ```

4. monitoring 2026-05-14 15:13 UTC

   Our team has seen the impacted services recover, and we are now closely monitoring for any remaining impact.

5. resolved 2026-05-15 23:13 UTC

   We 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...

Excerpts are shortened. Read the full incident on Aiven's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

Started during AWS: Multiple services (UAE): Region Availability.

1. monitoring 2026-03-01 23:12 UTC

   Amazon Web Services (AWS) currently has an outage that is impacting deployments of services in the ME-CENTRAL-1 Region (mec1-az2) specifically. Aiven provides the capability to let users move their workloads off this region, and we would recommend that users do so. For more...

2. monitoring 2026-03-02 08:16 UTC

   Amazon Web Services (AWS) currently has an outage that is impacting deployments of services in the ME-CENTRAL-1 Region. Aiven provides the capability to let users move their workloads off this region, and we would recommend that users do so. For more information please see the...

3. monitoring 2026-03-02 15:38 UTC

   Amazon Web Services (AWS) currently has an outage that is impacting deployments of services in the ME-CENTRAL-1 Region. We have disabled the creation of new nodes and services in this region. AWS has advised that users run their Disaster Recovery Plans for AWS products and...

4. monitoring 2026-03-03 03:01 UTC

   Amazon Web Services (AWS) currently has an outage that is impacting deployments of services in the ME-CENTRAL-1 and ME-SOUTH-1 regions. We have disabled the creation of new nodes and services in both of these regions. AWS has advised that users run their Disaster Recovery Plans...

5. resolved 2026-04-02 11:23 UTC

   The 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...

Excerpts are shortened. Read the full incident on Aiven's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-12-12 11:33 UTC

   We are currently experiencing issues with node creation on the UpCloud cloud platform. This may result in longer than usual start-up times for new services or replacement nodes in all UpCloud regions. Our engineering team is actively investigating the issue with UpCloud to...

2. identified 2025-12-12 21:20 UTC

   Node creation operations are now performing within normal parameters across all UpCloud regions. Our team is currently working through residual issues to ensure full stability. We will continue to monitor the situation closely and provide further updates.

3. resolved 2025-12-17 13:58 UTC

   The 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...

Excerpts are shortened. Read the full incident on Aiven's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-12-08 03:48 UTC

   We are investigating a delay for new nodes coming online. Our engineers are actively working on a resolution. We apologize for any inconvenience this may cause. We will provide another update as soon as more information is available.

2. investigating 2025-12-08 16:05 UTC

   We are continuing to investigate degraded performance of our DNS updates. Customers are recommended to avoid any action which will cause a DNS update (IE: a node replacement) out an abundance of caution. Our engineers have identified the issue and are now working on potential...

3. monitoring 2025-12-08 17:25 UTC

   We have resolved the degraded performance issue affecting DNS updates. Customer actions requiring a DNS update (e.g., node replacements) can now be performed without caution. We are continuing to closely monitor the environment to ensure stability of the platform.

4. resolved 2025-12-08 20:41 UTC

   We 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.

Excerpts are shortened. Read the full incident on Aiven's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. investigating 2025-12-05 07:19 UTC

   We are currently investigating reports of degraded performance and connectivity errors impacting services hosted in the Azure Norway North region. Some services have become unreachable, creating a new service in the region doesn't work either. Although the official Azure Status...

2. investigating 2025-12-05 13:58 UTC

   We have received official confirmation from Microsoft Azure regarding the connectivity and availability issues we observed earlier. Microsoft has identified a cooling infrastructure failure in the Norway West region. To protect hardware integrity due to elevated temperatures,...

3. investigating 2025-12-05 16:53 UTC

   We have received official confirmation from Microsoft Azure regarding the connectivity and availability issues we observed earlier. Microsoft has identified a cooling infrastructure failure in the Norway West region. To protect hardware integrity due to elevated temperatures,...

4. investigating 2025-12-05 19:00 UTC

   We have received official confirmation from Microsoft Azure regarding the connectivity and availability issues we observed earlier. Microsoft has identified a cooling infrastructure failure in the Norway West region. To protect hardware integrity due to elevated temperatures,...

5. investigating 2025-12-05 20:25 UTC

   We have received official confirmation from Microsoft Azure regarding the connectivity and availability issues we observed earlier. Microsoft had identified a cooling infrastructure failure in the Norway West region. To protect hardware integrity due to elevated temperatures,...

6. monitoring 2025-12-06 03:10 UTC

   We continue monitoring the updates provide by Microsoft Azure, the current status is: **_Current Status:_** _We’ve made significant progress in restoring services within the Norway West region. Cooling and power systems are stable, along with the temperatures, and network...

7. resolved 2025-12-06 03:35 UTC

   We 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.

Excerpts are shortened. Read the full incident on Aiven's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-12-04 17:12 UTC

   We are currently experiencing problems with the APIs responsible for retrieving metrics. As a result, the Metrics page in the console and related API endpoints may be unavailable or display incomplete data. Our engineering team is actively working to identify the cause and...

2. investigating 2025-12-04 18:48 UTC

   Our engineering team is continuing the investigation and is currently taking actions to mitigate the issue. You may continue to experience problems with metrics retrieval while these mitigations are put in place. We’ll provide further updates as we make progress.

3. resolved 2025-12-04 19:17 UTC

   The 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.

Excerpts are shortened. Read the full incident on Aiven's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-11-24 03:39 UTC

   We are currently investigating an issue affecting the availability of some PostgreSQL read-replica nodes. A mitigation procedure is being applied to affected services, while we continue investigating the root cause. We will provide status updates for this incident as more...

2. monitoring 2025-11-24 04:51 UTC

   The root cause for the issue was identified (some credentials were disabled as part of a previous incident). After enabling the credentials back there is no PG replicas reporting the issue. If you find any problem with your PG replicas please contact Aiven support.

3. resolved 2025-11-24 05:38 UTC

   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.

Excerpts are shortened. Read the full incident on Aiven's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-11-19 22:05 UTC

   We're currently experiencing an issue powering on PostgreSQL services. This affects services that have been powered off and then subsequently powered back on. When this happens you will notice in the Aiven console that the nodes stay in starting. This does not currently affect...

2. investigating 2025-11-19 23:49 UTC

   We're currently investigating an issue with PostgreSQL services that have been powered off and then subsequently powered back on. When this happens you will notice in the Aiven console that the nodes stay in starting. This does not currently affect already powered on services,...

3. resolved 2025-11-20 00:07 UTC

   We 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.

Excerpts are shortened. Read the full incident on Aiven's status page.