Störungsverlauf von Aiven

1. 8. August 2026 um 21:28 UTCinvestigating

   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, we are observing delays in new VM creation across all other cloud providers. **Impact**: **DigitalOcean**: New VM creation is currently unavailable in all DO regions. **All other clouds**: New VM creation may be delayed longer than usual. Existing services are not affected and continue to run normally. This issue impacts only the creation of new VMs (e.g., new service provisioning, node replacements, and scaling operations that require new VMs). Our engineering team is actively monitoring the situation and working to reduce the provisioning backlog. We are tracking the upstream provider's recovery and will restore normal provisioning times as soon as possible. We apologize for the inconvenience caused by this issue.

2. 8. August 2026 um 21:50 UTCinvestigating

   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 slowly returning to normal pace. We are continuing to monitor to confirm provisioning times remain stable. • **DigitalOcean:** New VM creation remains unavailable in DigitalOcean regions due to the ongoing upstream provider incident. We are tracking the provider's recovery and will restore normal provisioning as soon as it is resolved. Our engineering team is actively monitoring provisioning performance across all clouds and continues to track the DigitalOcean provider's recovery. Thank you for your patience.

3. 9. August 2026 um 06:28 UTCresolved

   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 provisioning. The incident is now resolved. Thank you for your patience.

1. 29. Juli 2026 um 14:29 UTCinvestigating

   Wir untersuchen ein Problem mit Dynamic Disk Sizing (DDS), bei dem Größenänderungen für eine kleine Teilmenge neu erstellter Knoten fehlschlagen können. Derzeit laufen Abmilderungen.

2. 29. Juli 2026 um 15:17 UTCidentified

   Das Problem wurde identifiziert und Fixes werden angewendet. Vielen Dank für Ihre Geduld.

3. 29. Juli 2026 um 17:07 UTCresolved

   Unser Team hat erfolgreich die entsprechende Minderung auf alle betroffenen Knoten angewendet, und der Fix wurde eingesetzt, um zukünftige Ereignisse zu verhindern.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 2. Juli 2026 um 23:24 UTCinvestigating

   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. Impacted operations (on DigitalOcean only) include: • Creating new services • Deleting existing services • Powering services up or down • Scheduled maintenance updates • Service scaling and plan upgrades Note: Existing, running services on DigitalOcean are currently unaffected and operating normally. Services running on other cloud providers (AWS, GCP, Azure, UpCloud) are completely unaffected. Our engineering team is actively working to resolve the issue, and we will provide further updates as soon as more information is available. We apologize for the inconvenience.

2. 3. Juli 2026 um 02:20 UTCinvestigating

   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 experience significant delays regardless of the underlying cloud hosting platform. We have stopped all pending maintenance updates to help mitigate the impact. Impacted operations across all providers include: - Creating new services - Powering services up - Scheduled maintenance updates - Service scaling and plan upgrades Note: Aiven for MySQL services are completely unaffected by this issue. For all other service types, existing, running services remain unaffected and continue to operate normally. Our engineering teams are actively working to resolve the root cause across our infrastructure, and we will provide further updates as the situation develops. We apologize for the continued inconvenience.

3. 3. Juli 2026 um 04:56 UTCmonitoring

   ``` 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, and maintenance updates are beginning to process, though it may take some time to clear the remaining backlog. ```

4. 3. Juli 2026 um 05:28 UTCresolved

   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 similar to this one.

1. 25. Juni 2026 um 10:16 UTCidentified

   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. We will provide an ETA as soon as it is available.

2. 25. Juni 2026 um 12:27 UTCmonitoring

   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. 25. Juni 2026 um 13:14 UTCresolved

   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.

1. 23. Juni 2026 um 14:18 UTCinvestigating

   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 upgrade Kafka services from version 3.8 to 3.9 will not be able to complete the upgrade while KRaft migrations are paused. Next update: We will provide an update once more information is available.

2. 23. Juni 2026 um 15:10 UTCidentified

   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. 24. Juni 2026 um 15:01 UTCidentified

   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. 25. Juni 2026 um 08:06 UTCmonitoring

   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. 25. Juni 2026 um 11:38 UTCresolved

   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.

1. 11. Juni 2026 um 15:25 UTCinvestigating

   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 upgrades once the issue is resolved. **Impact:** Running Kafka services are not affected and continue to operate normally. Customers who attempt to upgrade a Kafka service to version 3.9 or later will receive an `HTTP 403` error and the upgrade will not proceed. No data or service availability is impacted.

2. 15. Juni 2026 um 14:01 UTCmonitoring

   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 Kafka upgrades to version 3.9 once we confirm the issue is fully resolved.

3. 16. Juni 2026 um 11:05 UTCresolved

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

1. 9. Juni 2026 um 15:10 UTCinvestigating

   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. 9. Juni 2026 um 15:57 UTCidentified

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

3. 9. Juni 2026 um 16:18 UTCmonitoring

   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. 9. Juni 2026 um 16:36 UTCmonitoring

   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. 9. Juni 2026 um 16:57 UTCresolved

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

1. 25. Mai 2026 um 02:29 UTCinvestigating

   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 functionality as quickly as possible. We will continue to update here on the progress of this issue.

2. 25. Mai 2026 um 03:48 UTCidentified

   ``` 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 failing. We are monitoring the deployment closely to ensure full functionality is restored as quickly as possible.We will continue to update here on the progress of this issue. ```

3. 25. Mai 2026 um 03:54 UTCresolved

   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 improving our platform to avoid future incidents similar to this one.

1. 20. Mai 2026 um 01:15 UTCinvestigating

   ``` 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 health directly on the DigitalOcean Status Page: https://status.digitalocean.com/incidents/spgd2scvttthOur engineering team is actively investigating the extent of the impact on our services and working to mitigate issues where possible. ```

2. 20. Mai 2026 um 02:38 UTCresolved

   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.

1. 14. Mai 2026 um 06:55 UTCinvestigating

   ``` 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. 14. Mai 2026 um 07:36 UTCidentified

   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. 14. Mai 2026 um 10:49 UTCmonitoring

   ``` 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. 14. Mai 2026 um 15:13 UTCmonitoring

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

5. 15. Mai 2026 um 23:13 UTCresolved

   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 avoid future incidents similar to this one.

1. 1. März 2026 um 23:12 UTCmonitoring

   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 information please see the AWS status page: https://health.aws.amazon.com/health/status

2. 2. März 2026 um 08:16 UTCmonitoring

   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 AWS status page: https://health.aws.amazon.com/health/status

3. 2. März 2026 um 15:38 UTCmonitoring

   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 services in that region and we are recommending the same. For more information please see the AWS status page: [https://health.aws.amazon.com/health/status](https://health.aws.amazon.com/health/status "https://health.aws.amazon.com/health/status")

4. 3. März 2026 um 03:01 UTCmonitoring

   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 for AWS products and services in both of these regions and we are recommending the same. For more information please see the AWS status page: https://health.aws.amazon.com/health/status

5. 2. April 2026 um 11:23 UTCresolved

   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 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 updates. https://health.aws.amazon.com/health/status

1. 12. Dezember 2025 um 11:33 UTCinvestigating

   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 resolve it as quickly as possible.

2. 12. Dezember 2025 um 21:20 UTCidentified

   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. 17. Dezember 2025 um 13:58 UTCresolved

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

1. 8. Dezember 2025 um 03:48 UTCinvestigating

   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. 8. Dezember 2025 um 16:05 UTCinvestigating

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

3. 8. Dezember 2025 um 17:25 UTCmonitoring

   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. 8. Dezember 2025 um 20:41 UTCresolved

   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.

1. 5. Dezember 2025 um 07:19 UTCinvestigating

   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 page currently reports all systems as operational, our internal monitoring and engineering teams are observing elevated error rates and latency in this region. We apologise for the inconvenience caused by this issue.

2. 5. Dezember 2025 um 13:58 UTCinvestigating

   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, Azure has proactively powered down affected compute and storage clusters. This explains the service unreachability and inability to provision new resources that we reported earlier. Current Status: Azure engineering teams are working to restore cooling. Once stable, they will begin a safe, phased power-up of the infrastructure. We are awaiting further updates from Microsoft regarding the cooling restoration and will notify you as soon as the power-up sequence begins.

3. 5. Dezember 2025 um 16:53 UTCinvestigating

   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, Azure has proactively powered down affected compute and storage clusters. This explains the service unreachability and inability to provision new resources that we reported earlier. Current Status: Cooling restoration efforts are progressing well and Azure engineering teams are currently preparing to execute a carefully phased power-up of core systems once stable conditions are confirmed. We are awaiting further updates from Microsoft regarding the cooling restoration and will notify you when the power-up sequence begins.

4. 5. Dezember 2025 um 19:00 UTCinvestigating

   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, Azure has proactively powered down affected compute and storage clusters. This explains the service unreachability and inability to provision new resources that we reported earlier. Current status: Cooling and power systems have been restored, and temperatures are now stable, according to the Azure engineering team. They are now proceeding with a controlled, staged power restoration, prioritizing network, storage, and compute resources to ensure a safe and reliable recovery. Azure network and storage resources have been powered on, and their compute power-on operations is progressing. Already 50% have been re-energized. We are awaiting further updates from Microsoft regarding the full restoration of their services.

5. 5. Dezember 2025 um 20:25 UTCinvestigating

   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, Azure proactively powered down affected compute and storage clusters. This explains the service unreachability and inability to provision new resources that we reported earlier. Current status: The Azure engineering team reports that cooling and power systems have been restored, and temperatures remain stable. Network and storage systems are fully powered, and compute resources are coming online as they complete their final validations. This process requires deliberate sequencing and validation on Azure's end to ensure safe and reliable service restoration and is time intensive. We appreciate your patience as they continue to work towards full resolution.

6. 6. Dezember 2025 um 03:10 UTCmonitoring

   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 resources are fully operational. Some of the services are seeing recovery. Event Hubs is fully recovered. Most compute resources are back online; a vast majority of Virtual Machines are also performing well, and Azure Kubernetes Service is also starting to recover. ExpressRoute circuits have seen significant recovery progress. The majority of storage clusters are also powered on and operational. Azure SQL DB is also seeing recovery._ _We’re continuing a controlled, staged recovery to ensure safety and reliability. Our teams are actively addressing this and validating dependencies to bring these resources online as quickly as possible. We appreciate your patience as we work towards full resolution._

7. 6. Dezember 2025 um 03:35 UTCresolved

   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.

1. 4. Dezember 2025 um 17:12 UTCinvestigating

   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 implement a fix. We apologize for the inconvenience and appreciate your patience while we resolve this issue.

2. 4. Dezember 2025 um 18:48 UTCinvestigating

   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. 4. Dezember 2025 um 19:17 UTCresolved

   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.

1. 24. November 2025 um 03:39 UTCinvestigating

   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 information becomes available.

2. 24. November 2025 um 04:51 UTCmonitoring

   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. 24. November 2025 um 05:38 UTCresolved

   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.

1. 19. November 2025 um 22:05 UTCinvestigating

   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 already powered on services, and those services are able to build new nodes correctly during maintenance updates or in the event of a failover. We're investigating the cause of the issue for possible mitigations that we can apply. We'll continue to update the status of this incident here.

2. 19. November 2025 um 23:49 UTCinvestigating

   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, and those services are able to build new nodes correctly during maintenance updates or in the event of a failover. We're investigating the cause of the issue for possible mitigations that we can apply. We advise not powering off your services if you plan to power them back on. We'll continue to update the status of this incident here.

3. 20. November 2025 um 00:07 UTCresolved

   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.

1. 18. November 2025 um 12:08 UTCinvestigating

   We are currently experiencing connectivity issues [https://aiven.io](https://aiven.io "https://aiven.io") and the Aiven Console [https://console.aiven.io/](https://console.aiven.io/ "https://console.aiven.io/"). This incident is caused by an ongoing outage within the Cloudflare Global Network. We are monitoring the situation closely. Cloudflare Incident Report: [https://www.cloudflarestatus.com/incidents/8gmgl950y3h7](https://www.cloudflarestatus.com/incidents/8gmgl950y3h7 "https://www.cloudflarestatus.com/incidents/8gmgl950y3h7") We apologise for the inconvenience caused by this issue. We will provide a further update as soon as possible.

2. 18. November 2025 um 12:30 UTCinvestigating

   We are currently experiencing connectivity issues [https://aiven.io](https://aiven.io "https://aiven.io") and the Aiven Console [https://console.aiven.io/](https://console.aiven.io/ "https://console.aiven.io/"). Running services are not impacted. This incident is caused by an ongoing outage within the Cloudflare Global Network. We are monitoring the situation closely. Cloudflare Incident Report:[https://www.cloudflarestatus.com/incidents/8gmgl950y3h7](https://www.cloudflarestatus.com/incidents/8gmgl950y3h7 "https://www.cloudflarestatus.com/incidents/8gmgl950y3h7")

3. 18. November 2025 um 14:44 UTCinvestigating

   We are currently awaiting remediation from CloudFlare, who are actively working to resolve the issue on their side. At this time, all running services remain fully operational and are not experiencing any impact. We will provide further updates as soon as more information becomes available.

4. 18. November 2025 um 19:06 UTCresolved

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

1. 6. November 2025 um 04:24 UTCinvestigating

   We are currently aware of an issue that is preventing PostgreSQL nodes from being able to start. We are currently working on a fix for this as a priority. We will continue to provide updates via our status page as they become available.

2. 6. November 2025 um 05:00 UTCmonitoring

   We identified an issue when trying to upgrade the version of postgres-anonymizer which was preventing new PostgreSQL nodes from starting up correctly. We have now mitigated this issue so all new PostgreSQL services will not encounter issues when starting up. We are currently working on recycling the nodes in existing PostgreSQL services to apply this fix. Customers can elect to power cycle the service themselves in order to return back to baseline sooner. If you continue to experience issues, please reach out to Aiven Support.

3. 6. November 2025 um 07:03 UTCmonitoring

   All impacted nodes in PostgreSQL services have been restored and are now operational. As referenced in the previous update, mitigation measures for new nodes continue to be in effect. Our engineering team has identified the root cause of this incident and is currently developing a permanent fix. The issue is specific to PostgreSQL 18; other PostgreSQL versions are not impacted. We will continue to closely monitor system performance to ensure continued platform stability.

4. 6. November 2025 um 07:35 UTCresolved

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

1. 31. Oktober 2025 um 11:35 UTCinvestigating

   **Investigating** - Our team is currently investigating an issue with starting up new services. Customers may be experiencing services stuck in initializing or rebalancing state. We will provide another update as soon as we have more information.

2. 31. Oktober 2025 um 11:59 UTCmonitoring

   **Monitoring** - A fix has been implemented for the issue affecting starting up new nodes. We are currently monitoring the platform to ensure that all systems are stable and the impact is mitigated.

3. 31. Oktober 2025 um 13:36 UTCresolved

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