Snapshot 20500
Normalized text
Scripts and page chrome removed; this is what change detection compares.
{
"incidents": [
{
"created_at": "2026-09-16T12:21:27Z",
"id": "01M2N2MD1Y9HQXKWANZETYEWAE",
"impact": "minor",
"incident_updates": [
{
"body": "We have resolved the underlying cause of the new node creation and new nodes are able to be created without issues.\n\nShould any further issues be encountered, please reach out to support via the Aiven console.\n\nWe apologise for the inconvenience caused by this issue, and commit to analysing and improving our platform to avoid future incidents similar to this one.",
"created_at": "2026-09-30T06:35:21Z",
"display_at": "2026-09-30T06:35:21Z",
"id": "01M3RGCQW5W56SZR3Y6T2B8YEZ",
"incident_id": "01M2N2MD1Y9HQXKWANZETYEWAE",
"status": "resolved",
"updated_at": "2026-09-30T06:35:21Z"
},
{
"body": "We have completed our mitigating actions and the creation of new nodes for services on the Aiven platform has returned to normal.\nCustomers can now proceed with any operations that were delayed during this issue, including service creation, scaling, upgrades, maintenance updates and configuration changes. Operations that were left pending should continue automatically.\nOur engineers continue to monitor the platform to confirm the issue is fully resolved.\nWe apologise for the inconvenience caused by this issue. We will provide a further update as our team completes monitoring of this situation.",
"created_at": "2026-09-16T15:04:38Z",
"display_at": "2026-09-16T15:04:38Z",
"id": "01M2NBZ5VV184PA67RQC05YRF9",
"incident_id": "01M2N2MD1Y9HQXKWANZETYEWAE",
"status": "monitoring",
"updated_at": "2026-09-16T15:04:38Z"
},
{
"body": "We are monitoring our mitigating actions to issues with creating new nodes for services on the Aiven platform. \n\nOur engineers have done mitigating steps and we see improvements in the node creation, but we'll continue investigating and monitoring of the issue.\n\nWe apologise for the inconvenience caused by this issue.\n\nWe will provide a further update as our team continues monitoring and triaging this situation.",
"created_at": "2026-09-16T13:58:54Z",
"display_at": "2026-09-16T13:58:54Z",
"id": "01M2N86TERF0ZEM2QWP16XMQ9Q",
"incident_id": "01M2N2MD1Y9HQXKWANZETYEWAE",
"status": "monitoring",
"updated_at": "2026-09-16T13:58:54Z"
},
{
"body": "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.\n\nOur engineers are currently investigating the root cause and working on a fix for the issue.\n\nWe apologise for the inconvenience caused by this issue. We will provide a further update as our team continues on the solution for this situation.",
"created_at": "2026-09-16T12:21:27Z",
"display_at": "2026-09-16T12:21:27Z",
"id": "01M2N2MD1Y4Y9C7J0YK5TKADX2",
"incident_id": "01M2N2MD1Y9HQXKWANZETYEWAE",
"status": "investigating",
"updated_at": "2026-09-16T12:21:27Z"
}
],
"name": "Creation of new service nodes disrupted",
"page_id": "01H0FX8N7BG3M9PMMX0J0HENJF",
"resolved_at": "2026-09-30T06:35:21Z",
"status": "resolved",
"updated_at": "2026-09-30T06:35:21Z"
},
{
"created_at": "2026-09-29T20:14:14Z",
"id": "01M3QCVE5V2R1GSTF3FJ1D8WD9",
"impact": "none",
"incident_updates": [
{
"body": "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.\nWe apologise for the disruption this caused.",
"created_at": "2026-09-30T00:41:32Z",
"display_at": "2026-09-30T00:41:32Z",
"id": "01M3QW4WBEV8CZHGTYFGQQ2D41",
"incident_id": "01M3QCVE5V2R1GSTF3FJ1D8WD9",
"status": "resolved",
"updated_at": "2026-09-30T00:41:32Z"
},
{
"body": "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.\nWe apologise for the disruption this caused.",
"created_at": "2026-09-30T00:30:48Z",
"display_at": "2026-09-30T00:30:48Z",
"id": "01M3QVH7313A86HMMNKTV9Z65M",
"incident_id": "01M3QCVE5V2R1GSTF3FJ1D8WD9",
"status": "monitoring",
"updated_at": "2026-09-30T00:30:48Z"
},
{
"body": "PostgreSQL major version upgrades can be performed again.\n\nA 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.",
"created_at": "2026-09-29T23:50:09Z",
"display_at": "2026-09-29T23:50:09Z",
"id": "01M3QS6SHXXDE2T6XMKWKVHPKC",
"incident_id": "01M3QCVE5V2R1GSTF3FJ1D8WD9",
"status": "identified",
"updated_at": "2026-09-29T23:50:09Z"
},
{
"body": "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.\n\nAffected services are being restored as the mitigation is deployed. We will provide further updates as the rollout progresses. We apologize for the inconvenience.",
"created_at": "2026-09-29T21:59:34Z",
"display_at": "2026-09-29T21:59:34Z",
"id": "01M3QJWA07K2741AE4VJABJCRW",
"incident_id": "01M3QCVE5V2R1GSTF3FJ1D8WD9",
"status": "identified",
"updated_at": "2026-09-29T21:59:34Z"
},
{
"body": "We are currently investigating an issue affecting Aiven for PostgreSQL services, where a major version upgrade can leave the service in an unusable state.\nWe 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].\nOur 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.",
"created_at": "2026-09-29T20:14:14Z",
"display_at": "2026-09-29T20:14:14Z",
"id": "01M3QCVE5VFGS22S7EW3JD9PAA",
"incident_id": "01M3QCVE5V2R1GSTF3FJ1D8WD9",
"status": "investigating",
"updated_at": "2026-09-29T20:14:14Z"
}
],
"name": "Issue with PostgreSQL major version upgrade",
"page_id": "01H0FX8N7BG3M9PMMX0J0HENJF",
"resolved_at": "2026-09-30T00:41:32Z",
"status": "resolved",
"updated_at": "2026-09-30T00:41:32Z"
},
{
"created_at": "2026-09-22T00:55:01Z",
"id": "01M339QT1T1ADNG71E2V5XHZ69",
"impact": "major",
"incident_updates": [
{
"body": "This incident is now resolved.\n\nEarlier 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.\n\nA corrected certificate has been in place across all API nodes since 02:05 UTC, and we have seen no further errors during our monitoring period. We are following up with a permanent fix to prevent this from recurring.\n\nWe apologize for the disruption. If you are still seeing problems, please contact Aiven support at [[email protected]](mailto:[email protected])",
"created_at": "2026-09-22T08:05:24Z",
"display_at": "2026-09-22T08:05:24Z",
"id": "01M342BVD0XFEP75S95E8E51PN",
"incident_id": "01M339QT1T1ADNG71E2V5XHZ69",
"status": "resolved",
"updated_at": "2026-09-22T08:05:24Z"
},
{
"body": "This incident is now resolved.\nBetween 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 integrations.\n\nThe issue was corrected and we have seen no further errors during our monitoring period. We are following up with additional changes to prevent this from recurring.\n\nWe apologise for the disruption. If you are still seeing problems, please contact Aiven support.",
"created_at": "2026-09-22T05:54:13Z",
"display_at": "2026-09-22T05:54:13Z",
"id": "01M33TVMVE7SW47REFH6K54E40",
"incident_id": "01M339QT1T1ADNG71E2V5XHZ69",
"status": "monitoring",
"updated_at": "2026-09-22T05:54:13Z"
},
{
"body": "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.\nWe will confirm here once it is complete. Thank you for your patience.",
"created_at": "2026-09-22T03:36:56Z",
"display_at": "2026-09-22T03:36:56Z",
"id": "01M33K0918XSHX3514WY378WCW",
"incident_id": "01M339QT1T1ADNG71E2V5XHZ69",
"status": "identified",
"updated_at": "2026-09-22T03:36:56Z"
},
{
"body": "We have identified the cause of this issue and a fix is now being rolled out across our API nodes in stages.\nThe 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 creating, modifying or querying services via the Console, CLI, Terraform provider or direct API calls. Retrying will often succeed.\nWe will confirm here once the rollout is complete. Thank you for your patience.",
"created_at": "2026-09-22T02:28:55Z",
"display_at": "2026-09-22T02:28:55Z",
"id": "01M33F3R4NYQM1ZBXT9EJ9HP65",
"incident_id": "01M339QT1T1ADNG71E2V5XHZ69",
"status": "identified",
"updated_at": "2026-09-22T02:28:55Z"
},
{
"body": "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 the Console, and failures when creating, modifying or querying services.\nOur engineering team is investigating and work to restore service is underway.\nWe will provide a further update within 30 minutes, or sooner if there is news to share. We apologise for the disruption.",
"created_at": "2026-09-22T00:55:01Z",
"display_at": "2026-09-22T00:55:01Z",
"id": "01M339QT1TTQHBX9KG81FJNZKG",
"incident_id": "01M339QT1T1ADNG71E2V5XHZ69",
"status": "investigating",
"updated_at": "2026-09-22T00:55:01Z"
}
],
"name": "Aiven Console and API are down",
"page_id": "01H0FX8N7BG3M9PMMX0J0HENJF",
"resolved_at": "2026-09-22T08:05:24Z",
"status": "resolved",
"updated_at": "2026-09-22T08:05:24Z"
},
{
"created_at": "2026-09-21T04:57:37Z",
"id": "01M31579NRV40M6S2ZEJAENKNE",
"impact": "major",
"incident_updates": [
{
"body": "This incident has been resolved. Aiven Console login and support ticket creation through the portal are fully functional again. \n\nWe continued to monitor performance and have seen no further issues. If you encounter any problems, please email [[email protected]](mailto:[email protected]).",
"created_at": "2026-09-21T08:25:14Z",
"display_at": "2026-09-21T08:25:14Z",
"id": "01M31H3FAX2FXQ2N3JE86QT32G",
"incident_id": "01M31579NRV40M6S2ZEJAENKNE",
"status": "resolved",
"updated_at": "2026-09-21T08:25:14Z"
},
{
"body": "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 [[email protected]](mailto:[email protected])",
"created_at": "2026-09-21T06:01:10Z",
"display_at": "2026-09-21T06:01:10Z",
"id": "01M318VNG3NH6FXXYHYWDNZQ1T",
"incident_id": "01M31579NRV40M6S2ZEJAENKNE",
"status": "monitoring",
"updated_at": "2026-09-21T06:01:10Z"
},
{
"body": "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.\n\nIf you require assistance with an urgent issue unrelated to the Aiven Console being down, please send an email to [[email protected]](mailto:[email protected]). Our support team will process your request directly.",
"created_at": "2026-09-21T05:27:57Z",
"display_at": "2026-09-21T05:27:57Z",
"id": "01M316YVECFJPVX11KJDD08GBM",
"incident_id": "01M31579NRV40M6S2ZEJAENKNE",
"status": "investigating",
"updated_at": "2026-09-21T05:27:57Z"
},
{
"body": "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.",
"created_at": "2026-09-21T04:57:37Z",
"display_at": "2026-09-21T04:57:37Z",
"id": "01M31579NR28RD7CNFYARXAAZJ",
"incident_id": "01M31579NRV40M6S2ZEJAENKNE",
"status": "investigating",
"updated_at": "2026-09-21T04:57:37Z"
}
],
"name": "Aiven Console is down",
"page_id": "01H0FX8N7BG3M9PMMX0J0HENJF",
"resolved_at": "2026-09-21T08:25:14Z",
"status": "resolved",
"updated_at": "2026-09-21T08:25:14Z"
},
{
"created_at": "2026-08-08T21:28:11Z",
"id": "01KZHMDFBHSR672AG5KT38N7KA",
"impact": "minor",
"incident_updates": [
{
"body": "New VM creation has returned to normal across all cloud providers, including DigitalOcean.\n\n* VM provisioning is operating normally across all regions.\n* The upstream DigitalOcean incident has been resolved.\n* We are continuing to monitor the infrastructure to ensure stable provisioning.\n\nThe incident is now resolved. Thank you for your patience.",
"created_at": "2026-08-09T06:28:49Z",
"display_at": "2026-08-09T06:28:49Z",
"id": "01KZJKBCT26CRTVEBE3ADBYPKQ",
"incident_id": "01KZHMDFBHSR672AG5KT38N7KA",
"status": "resolved",
"updated_at": "2026-08-09T06:28:49Z"
},
{
"body": "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.\n\n**Current status**\n\n• **All clouds except DigitalOcean:** New VM creations are slowly returning to normal pace. We are continuing to monitor to confirm provisioning times remain stable.\n\n• **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.\n\nOur engineering team is actively monitoring provisioning performance across all clouds and continues to track the DigitalOcean provider's recovery. Thank you for your patience.",
"created_at": "2026-08-08T21:50:27Z",
"display_at": "2026-08-08T21:50:27Z",
"id": "01KZHNP7SZMC9RJPVQQ1ZVPT82",
"incident_id": "01KZHMDFBHSR672AG5KT38N7KA",
"status": "investigating",
"updated_at": "2026-08-08T21:50:27Z"
},
{
"body": "We are currently experiencing delays in the creation of new virtual machines, which may affect the provisioning of new services and nodes.\nAn 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.\n\n**Impact**:\n**DigitalOcean**: New VM creation is currently unavailable in all DO regions.\n**All other clouds**: New VM creation may be delayed longer than usual.\n\nExisting 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).\n\nOur 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.",
"created_at": "2026-08-08T21:28:11Z",
"display_at": "2026-08-08T21:28:11Z",
"id": "01KZHMDFBHDYTAYEXF9R3XSMHF",
"incident_id": "01KZHMDFBHSR672AG5KT38N7KA",
"status": "investigating",
"updated_at": "2026-08-08T21:28:11Z"
}
],
"name": "Delayed VM Creation",
"page_id": "01H0FX8N7BG3M9PMMX0J0HENJF",
"resolved_at": "2026-08-09T06:28:49Z",
"status": "resolved",
"updated_at": "2026-08-09T06:28:49Z"
},
{
"created_at": "2026-07-29T14:29:15Z",
"id": "01KYQ4F5YRVX37CD90CPZMBZZJ",
"impact": "major",
"incident_updates": [
{
"body": "Our team has successfully applied the appropriate mitigation to all impacted nodes, and the fix has been deployed to prevent future occurrences.",
"created_at": "2026-07-29T17:07:13Z",
"display_at": "2026-07-29T17:07:13Z",
"id": "01KYQDGDPRTSA4TZWD9M303Z37",
"incident_id": "01KYQ4F5YRVX37CD90CPZMBZZJ",
"status": "resolved",
"updated_at": "2026-07-29T17:07:13Z"
},
{
"body": "Issue has been identified and fixes are being applied. Thank you for your patience.",
"created_at": "2026-07-29T15:17:27Z",
"display_at": "2026-07-29T15:17:27Z",
"id": "01KYQ77ENRARPPQ96QZE8CKAQA",
"incident_id": "01KYQ4F5YRVX37CD90CPZMBZZJ",
"status": "identified",
"updated_at": "2026-07-29T15:17:27Z"
},
{
"body": "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.",
"created_at": "2026-07-29T14:29:15Z",
"display_at": "2026-07-29T14:29:15Z",
"id": "01KYQ4F5YRFPR2J4PB19QNMQ1C",
"incident_id": "01KYQ4F5YRVX37CD90CPZMBZZJ",
"status": "investigating",
"updated_at": "2026-07-29T14:29:15Z"
}
],
"name": "Aiven Dynamic Disk Sizing (DDS) failures",
"page_id": "01H0FX8N7BG3M9PMMX0J0HENJF",
"resolved_at": "2026-07-29T17:07:13Z",
"status": "resolved",
"updated_at": "2026-07-29T17:07:13Z"
},
{
"created_at": "2026-07-02T23:24:59Z",
"id": "01KWJJCQPX0DKH6PTVHB6Z6YFE",
"impact": "major",
"incident_updates": [
{
"body": "We have resolved the underlying cause of this issue.\n\nShould any further issues be encountered, please reach out to support via the Aiven console.\n\nWe apologise for the inconvenience caused by this issue, and commit to analysing and improving our platform to avoid future incidents similar to this one.",
"created_at": "2026-07-03T05:28:30Z",
"display_at": "2026-07-03T05:28:30Z",
"id": "01KWK76BFVH4ABG60M60175H97",
"incident_id": "01KWJJCQPX0DKH6PTVHB6Z6YFE",
"status": "resolved",
"updated_at": "2026-07-03T05:28:30Z"
},
{
"body": "```\nWe have implemented a mitigation for the infrastructure issue affecting node lifecycle management, and we are now seeing service operations return to normal.\n\nWe 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.\n```\n\n ",
"created_at": "2026-07-03T04:56:00Z",
"display_at": "2026-07-03T04:56:00Z",
"id": "01KWK5AV65T90HB8AMHVKP2J4M",
"incident_id": "01KWJJCQPX0DKH6PTVHB6Z6YFE",
"status": "monitoring",
"updated_at": "2026-07-03T04:56:00Z"
},
{
"body": "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.\n\nAs 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.\n\nImpacted operations across all providers include:\n- Creating new services\n- Powering services up\n- Scheduled maintenance updates\n- Service scaling and plan upgrades\n\nNote: 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.",
"created_at": "2026-07-03T02:20:43Z",
"display_at": "2026-07-03T02:20:43Z",
"id": "01KWJWEGN5F85CAS8VT63HMYZV",
"incident_id": "01KWJJCQPX0DKH6PTVHB6Z6YFE",
"status": "investigating",
"updated_at": "2026-07-03T02:20:43Z"
},
{
"body": "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.\n\nImpacted operations (on DigitalOcean only) include:\n\n• Creating new services\n\n• Deleting existing services\n\n• Powering services up or down\n\n• Scheduled maintenance updates\n\n• Service scaling and plan upgrades\n\n\nNote: 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.",
"created_at": "2026-07-02T23:24:59Z",
"display_at": "2026-07-02T23:24:59Z",
"id": "01KWJJCQPXRTGC6Y9H5AMKMTEZ",
"incident_id": "01KWJJCQPX0DKH6PTVHB6Z6YFE",
"status": "investigating",
"updated_at": "2026-07-02T23:24:59Z"
}
],
"name": "Delayed Service Operations Affecting All Cloud Providers (MySQL Unaffected)",
"page_id": "01H0FX8N7BG3M9PMMX0J0HENJF",
"resolved_at": "2026-07-03T05:28:30Z",
"status": "resolved",
"updated_at": "2026-07-03T05:28:30Z"
},
{
"created_at": "2026-06-25T10:16:16Z",
"id": "01KVZ4FH5QGZM4VJ85GSQJ90XP",
"impact": "none",
"incident_updates": [
{
"body": "The issue has been resolved. Terraform \u0026 Kubernetes operator users should no longer experience `400` errors when using `aiven_pg_database`. We apologize for any inconvenience caused.",
"created_at": "2026-06-25T13:14:31Z",
"display_at": "2026-06-25T13:14:31Z",
"id": "01KVZENWTGEZWYM5TRXSMMNJR3",
"incident_id": "01KVZ4FH5QGZM4VJ85GSQJ90XP",
"status": "resolved",
"updated_at": "2026-06-25T13:14:31Z"
},
{
"body": "A fix has been applied and the issue is expected to be resolved. \n\nWe are continuing to monitor closely as we work to restore full system operation.\n\nWe apologise for the inconvenience caused by this issue. ",
"created_at": "2026-06-25T12:27:51Z",
"display_at": "2026-06-25T12:27:51Z",
"id": "01KVZC0F4KVVX8CBTJY7XA1KJ6",
"incident_id": "01KVZ4FH5QGZM4VJ85GSQJ90XP",
"status": "monitoring",
"updated_at": "2026-06-25T12:27:51Z"
},
{
"body": "We are currently investigating an issue affecting Terraform \u0026 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.",
"created_at": "2026-06-25T10:16:16Z",
"display_at": "2026-06-25T10:16:16Z",
"id": "01KVZ4FH5QPM7AC04YPHTJCWTD",
"incident_id": "01KVZ4FH5QGZM4VJ85GSQJ90XP",
"status": "identified",
"updated_at": "2026-06-25T10:16:16Z"
}
],
"name": "Terraform \u0026 Kubernetes operators - List Databases API Error (400)",
"page_id": "01H0FX8N7BG3M9PMMX0J0HENJF",
"resolved_at": "2026-06-25T13:14:31Z",
"status": "resolved",
"updated_at": "2026-06-25T13:14:31Z"
},
{
"created_at": "2026-06-23T14:18:37Z",
"id": "01KVTDHTR4D812RGYHY8BQ1XC5",
"impact": "none",
"incident_updates": [
{
"body": "The issues affecting KRaft migrations during Kafka 3\\.8 to 3\\.9 upgrades have been resolved.\n\nFixes have been deployed, migrations have been re-enabled, and services have remained stable during monitoring. \n\nIf you are experiencing any issues, please contact support.",
"created_at": "2026-06-25T11:38:25Z",
"display_at": "2026-06-25T11:38:25Z",
"id": "01KVZ95Y7HPRY5T483719XWZ80",
"incident_id": "01KVTDHTR4D812RGYHY8BQ1XC5",
"status": "resolved",
"updated_at": "2026-06-25T11:38:25Z"
},
{
"body": "We have deployed fixes for the issues affecting KRaft migrations during Kafka 3.8 to 3.9 upgrades, and migrations have been re-enabled. \n\nWe are continuing to monitor the situation to ensure services remain stable. \n\nIf you are experiencing any issues, please contact support.",
"created_at": "2026-06-25T08:06:04Z",
"display_at": "2026-06-25T08:06:04Z",
"id": "01KVYX145G7BQ970JN1WKFB5C6",
"incident_id": "01KVTDHTR4D812RGYHY8BQ1XC5",
"status": "monitoring",
"updated_at": "2026-06-25T08:06:04Z"
},
{
"body": "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.\nIf you are experiencing any issues, please contact support.",
"created_at": "2026-06-24T15:01:27Z",
"display_at": "2026-06-24T15:01:27Z",
"id": "01KVX2D05PYFD5471AWPSRCSF7",
"incident_id": "01KVTDHTR4D812RGYHY8BQ1XC5",
"status": "identified",
"updated_at": "2026-06-24T15:01:27Z"
},
{
"body": "We have identified two separate problems:\n\n• An issue in migration code\n\n• An [upstream bug](https://github.com/apache/kafka/pull/19854)\n\nWe are working on the fix for the migration issue and back-porting the fix for the upstream bug.\n\nIf you have any issues, please contact support.",
"created_at": "2026-06-23T15:10:54Z",
"display_at": "2026-06-23T15:10:54Z",
"id": "01KVTGHJAJA5ATCFEB86K7DZEV",
"incident_id": "01KVTDHTR4D812RGYHY8BQ1XC5",
"status": "identified",
"updated_at": "2026-06-23T16:05:18Z"
},
{
"body": "We have paused Kafka 3.8 -\u003e3.9 upgrades as we are investigating an issue with KRaft migration during the upgrade.\n\nAiven is actively monitoring affected services and applying mitigations where required.\n\nImpact: 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. \n\nNext update: We will provide an update once more information is available.",
"created_at": "2026-06-23T14:18:37Z",
"display_at": "2026-06-23T14:18:37Z",
"id": "01KVTDHTR4FBMMF5S5AB99MXXZ",
"incident_id": "01KVTDHTR4D812RGYHY8BQ1XC5",
"status": "investigating",
"updated_at": "2026-06-23T14:18:37Z"
}
],
"name": "Kafka upgrade to 3.9 paused",
"page_id": "01H0FX8N7BG3M9PMMX0J0HENJF",
"resolved_at": "2026-06-25T11:38:25Z",
"status": "resolved",
"updated_at": "2026-06-25T11:38:25Z"
},
{
"created_at": "2026-06-11T15:25:40Z",
"id": "01KTVMKZBYSE5P60SA0CHF505F",
"impact": "none",
"incident_updates": [
{
"body": "The issue has been resolved. All affected functionality is operating normally.",
"created_at": "2026-06-16T11:05:49Z",
"display_at": "2026-06-16T11:05:49Z",
"id": "01KV81QS9NY0ZZ30A2GAMTYE42",
"incident_id": "01KTVMKZBYSE5P60SA0CHF505F",
"status": "resolved",
"updated_at": "2026-06-16T11:05:49Z"
},
{
"body": "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.\n\nWe will re-enable Kafka upgrades to version 3.9 once we confirm the issue is fully resolved.",
"created_at": "2026-06-15T14:01:05Z",
"display_at": "2026-06-15T14:01:05Z",
"id": "01KV5SBZCFYRG0Z8HXWZKZ15YS",
"incident_id": "01KTVMKZBYSE5P60SA0CHF505F",
"status": "monitoring",
"updated_at": "2026-06-15T14:01:05Z"
},
{
"body": "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.\n\n**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.",
"created_at": "2026-06-11T15:25:40Z",
"display_at": "2026-06-11T15:25:40Z",
"id": "01KTVMKZBY31CCKTMEYM1QRY7W",
"incident_id": "01KTVMKZBYSE5P60SA0CHF505F",
"status": "investigating",
"updated_at": "2026-06-11T15:25:40Z"
}
],
"name": "Kafka upgrades to 3.9 are paused",
"page_id": "01H0FX8N7BG3M9PMMX0J0HENJF",
"resolved_at": "2026-06-16T11:05:49Z",
"status": "resolved",
"updated_at": "2026-06-16T11:05:49Z"
},
{
"created_at": "2026-06-09T15:10:00Z",
"id": "01KTPEXVETZE2SJAYVXFVT25EJ",
"impact": "major",
"incident_updates": [
{
"body": "The monitoring period has passed without further evidence of the issue occurring. Incident has been declared resolved.",
"created_at": "2026-06-09T16:57:26Z",
"display_at": "2026-06-09T16:57:26Z",
"id": "01KTPN2JGJD7HBBBH28FD995BA",
"incident_id": "01KTPEXVETZE2SJAYVXFVT25EJ",
"status": "resolved",
"updated_at": "2026-06-09T16:57:26Z"
},
{
"body": "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.",
"created_at": "2026-06-09T16:36:20Z",
"display_at": "2026-06-09T16:36:20Z",
"id": "01KTPKVY2NRJDAN3DPK2KFC9HJ",
"incident_id": "01KTPEXVETZE2SJAYVXFVT25EJ",
"status": "monitoring",
"updated_at": "2026-06-09T16:36:20Z"
},
{
"body": "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.",
"created_at": "2026-06-09T16:18:24Z",
"display_at": "2026-06-09T16:18:24Z",
"id": "01KTPJV37SCHQY1XBYHFC1GWKG",
"incident_id": "01KTPEXVETZE2SJAYVXFVT25EJ",
"status": "monitoring",
"updated_at": "2026-06-09T16:18:24Z"
},
{
"body": "Our team has identified a potential root cause and is working to fix the issue on the affected services.",
"created_at": "2026-06-09T15:57:46Z",
"display_at": "2026-06-09T15:57:46Z",
"id": "01KTPHNAE1GHKK17BSP03DBBM6",
"incident_id": "01KTPEXVETZE2SJAYVXFVT25EJ",
"status": "identified",
"updated_at": "2026-06-09T15:57:46Z"
},
{
"body": "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.",
"created_at": "2026-06-09T15:10:00Z",
"display_at": "2026-06-09T15:10:00Z",
"id": "01KTPEXVETRY46H1P0627BNRK5",
"incident_id": "01KTPEXVETZE2SJAYVXFVT25EJ",
"status": "investigating",
"updated_at": "2026-06-09T15:10:00Z"
}
],
"name": "Backup and restore failures affecting some Aiven for PostgreSQL services",
"page_id": "01H0FX8N7BG3M9PMMX0J0HENJF",
"resolved_at": "2026-06-09T16:57:26Z",
"status": "resolved",
"updated_at": "2026-06-09T16:57:26Z"
},
{
"created_at": "2026-05-25T02:29:06Z",
"id": "01KSEFDTE7Y3MPKV5CPMJ5V6PH",
"impact": "major",
"incident_updates": [
{
"body": "We have resolved the underlying cause of the issue affection service operations in our Azure regions.\n\nShould any further issues be encountered, please reach out to support via the Aiven console.\n\nWe apologise for the inconvenience caused by this issue, and commit to analysing and improving our platform to avoid future incidents similar to this one.",
"created_at": "2026-05-25T03:54:07Z",
"display_at": "2026-05-25T03:54:07Z",
"id": "01KSEM9GC4FTFXAASP9PMCMAVC",
"incident_id": "01KSEFDTE7Y3MPKV5CPMJ5V6PH",
"status": "resolved",
"updated_at": "2026-05-25T03:54:07Z"
},
{
"body": "```\nWe 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.\n```\n\n ",
"created_at": "2026-05-25T03:48:26Z",
"display_at": "2026-05-25T03:48:26Z",
"id": "01KSEKZ3C9EED8MYYKVEQA3RDV",
"incident_id": "01KSEFDTE7Y3MPKV5CPMJ5V6PH",
"status": "identified",
"updated_at": "2026-05-25T03:48:26Z"
},
{
"body": "We are experiencing an issue affecting service operations across Azure regions.\n\nWhile 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.\n\nWe will continue to update here on the progress of this issue.",
"created_at": "2026-05-25T02:29:06Z",
"display_at": "2026-05-25T02:29:06Z",
"id": "01KSEFDTE7J7GKS86TJKK1CZQQ",
"incident_id": "01KSEFDTE7Y3MPKV5CPMJ5V6PH",
"status": "investigating",
"updated_at": "2026-05-25T02:29:06Z"
}
],
"name": "Service operations affected in Azure",
"page_id": "01H0FX8N7BG3M9PMMX0J0HENJF",
"resolved_at": "2026-05-25T03:54:07Z",
"status": "resolved",
"updated_at": "2026-05-25T03:54:07Z"
},
{
"created_at": "2026-05-20T01:15:06Z",
"id": "01KS1F6QG7BAYZHAYBAW4MWXQT",
"impact": "minor",
"incident_updates": [
{
"body": "This issue is now resolved.\n\nShould any further issues be encountered, please reach out to support via the Aiven console.\n\nWe apologise for the inconvenience caused by this issue.",
"created_at": "2026-05-20T02:38:53Z",
"display_at": "2026-05-20T02:38:53Z",
"id": "01KS1M04TFKVW8AWNG8FA39RSC",
"incident_id": "01KS1F6QG7BAYZHAYBAW4MWXQT",
"status": "resolved",
"updated_at": "2026-05-20T02:38:53Z"
},
{
"body": "```\nWe 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.\n```\n\n ",
"created_at": "2026-05-20T01:15:06Z",
"display_at": "2026-05-20T01:15:06Z",
"id": "01KS1F6QG7KHDJVJ0CJ4C3YJ20",
"incident_id": "01KS1F6QG7BAYZHAYBAW4MWXQT",
"status": "investigating",
"updated_at": "2026-05-20T01:15:06Z"
}
],
"name": "Issue affecting services in DigitalOcean NYC3 region",
"page_id": "01H0FX8N7BG3M9PMMX0J0HENJF",
"resolved_at": "2026-05-20T02:38:53Z",
"status": "resolved",
"updated_at": "2026-05-20T02:38:53Z"
},
{
"created_at": "2026-05-14T06:55:15Z",
"id": "01KRJM983YEN7TRH1Q09CNWFKE",
"impact": "none",
"incident_updates": [
{
"body": "We have resolved the underlying cause of the kafka service disruption.\n\nShould any further issues be encountered, please reach out to support via the Aiven console.\n\nWe apologise for the inconvenience caused by this issue, and commit to analysing and improving our platform to avoid future incidents similar to this one.",
"created_at": "2026-05-15T23:13:23Z",
"display_at": "2026-05-15T23:13:23Z",
"id": "01KRPYMZQQ2ARKNEA295XJATMM",
"incident_id": "01KRJM983YEN7TRH1Q09CNWFKE",
"status": "resolved",
"updated_at": "2026-05-15T23:13:23Z"
},
{
"body": "Our team has seen the impacted services recover, and we are now closely monitoring for any remaining impact.",
"created_at": "2026-05-14T15:13:59Z",
"display_at": "2026-05-14T15:13:59Z",
"id": "01KRKGTF3ZE0P4613J7YYF1EDQ",
"incident_id": "01KRJM983YEN7TRH1Q09CNWFKE",
"status": "monitoring",
"updated_at": "2026-05-14T15:13:59Z"
},
{
"body": "```\nWe 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.\n```",
"created_at": "2026-05-14T10:49:14Z",
"display_at": "2026-05-14T10:49:14Z",
"id": "01KRK1NPKPXNEJRQSZ33HNMJB5",
"incident_id": "01KRJM983YEN7TRH1Q09CNWFKE",
"status": "monitoring",
"updated_at": "2026-05-14T10:49:14Z"
},
{
"body": "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.",
"created_at": "2026-05-14T07:36:04Z",
"display_at": "2026-05-14T07:36:04Z",
"id": "01KRJPKZRS9P9BAVZK1QNFW3C6",
"incident_id": "01KRJM983YEN7TRH1Q09CNWFKE",
"status": "identified",
"updated_at": "2026-05-14T07:36:04Z"
},
{
"body": "```\nWe 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.\n```",
"created_at": "2026-05-14T06:55:15Z",
"display_at": "2026-05-14T06:55:15Z",
"id": "01KRJM983YB9R42EMTPDBB2GS8",
"incident_id": "01KRJM983YEN7TRH1Q09CNWFKE",
"status": "investigating",
"updated_at": "2026-05-14T06:55:15Z"
}
],
"name": "Multiple Aiven for Apache Kafka services experiencing disruption",
"page_id": "01H0FX8N7BG3M9PMMX0J0HENJF",
"resolved_at": "2026-05-15T23:13:23Z",
"status": "resolved",
"updated_at": "2026-05-15T23:13:23Z"
},
{
"created_at": "2026-03-01T23:12:45Z",
"id": "01KJNTSXKSNJJ8NWRKFWW9XT3K",
"impact": "major",
"incident_updates": [
{
"body": "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. \n\nWe 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. \n\nAs 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. \n\nWe recommend customers continue to monitor the official AWS Health Status Page for updates.\nhttps://health.aws.amazon.com/health/status",
"created_at": "2026-04-02T11:23:09Z",
"display_at": "2026-04-02T11:23:09Z",
"id": "01KN6YXKWZTDVQZN100YPKCA1K",
"incident_id": "01KJNTSXKSNJJ8NWRKFWW9XT3K",
"status": "resolved",
"updated_at": "2026-04-02T11:23:09Z"
},
{
"body": "Amazon Web Services (AWS) currently has an outage that is impacting deployments of services in the ME-CENTRAL-1 and ME-SOUTH-1 regions.\n\nWe 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.\n\nFor more information please see the AWS status page: https://health.aws.amazon.com/health/status",
"created_at": "2026-03-03T03:01:31Z",
"display_at": "2026-03-03T03:01:31Z",
"id": "01KJRT9GS17K9YP48QJ26J76R2",
"incident_id": "01KJNTSXKSNJJ8NWRKFWW9XT3K",
"status": "monitoring",
"updated_at": "2026-04-01T14:31:13Z"
},
{
"body": "\nAmazon Web Services (AWS) currently has an outage that is impacting deployments of services in the ME-CENTRAL-1 Region.\n\nWe 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.\n\nFor 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\")",
"created_at": "2026-03-02T15:38:41Z",
"display_at": "2026-03-02T15:38:41Z",
"id": "01KJQK76Z2417KKJ437YY79QQ3",
"incident_id": "01KJNTSXKSNJJ8NWRKFWW9XT3K",
"status": "monitoring",
"updated_at": "2026-03-02T15:39:24Z"
},
{
"body": "Amazon Web Services (AWS) currently has an outage that is impacting deployments of services in the ME-CENTRAL-1 Region. \n\nAiven provides the capability to let users move their workloads off this region, and we would recommend that users do so. \n\nFor more information please see the AWS status page: https://health.aws.amazon.com/health/status",
"created_at": "2026-03-02T08:16:06Z",
"display_at": "2026-03-02T08:16:06Z",
"id": "01KJPSWTDEPFD91JZ9P4K16CB3",
"incident_id": "01KJNTSXKSNJJ8NWRKFWW9XT3K",
"status": "monitoring",
"updated_at": "2026-03-02T08:16:06Z"
},
{
"body": "Amazon Web Services (AWS) currently has an outage that is impacting deployments of services in the ME-CENTRAL-1 Region (mec1-az2) specifically. \n\nAiven provides the capability to let users move their workloads off this region, and we would recommend that users do so. \n\nFor more information please see the AWS status page: https://health.aws.amazon.com/health/status",
"created_at": "2026-03-01T23:12:45Z",
"display_at": "2026-03-01T23:12:45Z",
"id": "01KJNTSXKSD4MHC6A7VWMBYAPM",
"incident_id": "01KJNTSXKSNJJ8NWRKFWW9XT3K",
"status": "monitoring",
"updated_at": "2026-03-01T23:12:45Z"
}
],
"name": "Amazon Web Services (AWS) ME-CENTRAL-1 and ME-SOUTH-1 region status",
"page_id": "01H0FX8N7BG3M9PMMX0J0HENJF",
"resolved_at": "2026-04-02T11:23:09Z",
"status": "resolved",
"updated_at": "2026-04-02T11:23:09Z"
},
{
"created_at": "2025-12-12T11:33:23Z",
"id": "01KC95CJ7TGWFPTC4C2KAJ04KV",
"impact": "none",
"incident_updates": [
{
"body": "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.",
"created_at": "2025-12-17T13:58:34Z",
"display_at": "2025-12-17T13:58:34Z",
"id": "01KCP9P0P1SW6TDV3E3DCWCHZS",
"incident_id": "01KC95CJ7TGWFPTC4C2KAJ04KV",
"status": "resolved",
"updated_at": "2025-12-17T13:58:34Z"
},
{
"body": "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.",
"created_at": "2025-12-12T21:20:58Z",
"display_at": "2025-12-12T21:20:58Z",
"id": "01KCA70ENKFTE2ZJ424Z06B6WE",
"incident_id": "01KC95CJ7TGWFPTC4C2KAJ04KV",
"status": "identified",
"updated_at": "2025-12-12T21:20:58Z"
},
{
"body": "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.",
"created_at": "2025-12-12T11:33:23Z",
"display_at": "2025-12-12T11:33:23Z",
"id": "01KC95CJ7TFJRWTY89YHZFGDXR",
"incident_id": "01KC95CJ7TGWFPTC4C2KAJ04KV",
"status": "investigating",
"updated_at": "2025-12-12T11:33:23Z"
}
],
"name": "Delays in Service Provisioning on UpCloud",
"page_id": "01H0FX8N7BG3M9PMMX0J0HENJF",
"resolved_at": "2025-12-17T13:58:34Z",
"status": "resolved",
"updated_at": "2026-03-12T18:31:00Z"
},
{
"created_at": "2025-12-08T03:48:30Z",
"id": "01KBY16EX4A9C7GBK0MKAVMMQC",
"impact": "major",
"incident_updates": [
{
"body": "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.",
"created_at": "2025-12-08T20:41:10Z",
"display_at": "2025-12-08T20:41:10Z",
"id": "01KBZV4Q491XTJZ2WNJ40T6HXV",
"incident_id": "01KBY16EX4A9C7GBK0MKAVMMQC",
"status": "resolved",
"updated_at": "2025-12-08T20:41:47Z"
},
{
"body": "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.\n\nWe are continuing to closely monitor the environment to ensure stability of the platform.",
"created_at": "2025-12-08T17:25:56Z",
"display_at": "2025-12-08T17:25:56Z",
"id": "01KBZFZ7XDET13WX12GRDJBEV4",
"incident_id": "01KBY16EX4A9C7GBK0MKAVMMQC",
"status": "monitoring",
"updated_at": "2025-12-08T17:25:56Z"
},
{
"body": "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. \n\nOur engineers have identified the issue and are now working on potential mitigations.",
"created_at": "2025-12-08T16:05:00Z",
"display_at": "2025-12-08T16:05:00Z",
"id": "01KBZBB1JR4P1661V2A4BKGZV5",
"incident_id": "01KBY16EX4A9C7GBK0MKAVMMQC",
"status": "investigating",
"updated_at": "2025-12-08T16:05:00Z"
},
{
"body": "We are investigating a delay for new nodes coming online. \n\nOur engineers are actively working on a resolution. \n\nWe apologize for any inconvenience this may cause. \n\nWe will provide another update as soon as more information is available.",
"created_at": "2025-12-08T03:48:30Z",
"display_at": "2025-12-08T03:48:30Z",
"id": "01KBY16EX400ZGQ29BSB421AT3",
"incident_id": "01KBY16EX4A9C7GBK0MKAVMMQC",
"status": "investigating",
"updated_at": "2025-12-08T03:48:30Z"
}
],
"name": "Delay for new nodes coming online",
"page_id": "01H0FX8N7BG3M9PMMX0J0HENJF",
"resolved_at": "2025-12-08T20:41:10Z",
"status": "resolved",
"updated_at": "2026-03-12T18:31:00Z"
},
{
"created_at": "2025-12-05T07:19:24Z",
"id": "01KBPP2FM307P2H9N3ZEEQ4J59",
"impact": "none",
"incident_updates": [
{
"body": "We have confirmed that all the Aiven services running on the Microsoft Azure region are operational. \n\nIf you face any further issues please contact Aiven support. ",
"created_at": "2025-12-06T03:35:09Z",
"display_at": "2025-12-06T03:35:09Z",
"id": "01KBRVMJE0Z8ASF7SBGX0A9D7J",
"incident_id": "01KBPP2FM307P2H9N3ZEEQ4J59",
"status": "resolved",
"updated_at": "2025-12-06T03:35:09Z"
},
{
"body": "We continue monitoring the updates provide by Microsoft Azure, the current status is: \n\n**_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._\n\n_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._",
"created_at": "2025-12-06T03:10:12Z",
"display_at": "2025-12-06T03:10:12Z",
"id": "01KBRT6WJ5CWKXGA904GFGTTDS",
"incident_id": "01KBPP2FM307P2H9N3ZEEQ4J59",
"status": "monitoring",
"updated_at": "2025-12-06T03:10:12Z"
},
{
"body": "We have received official confirmation from Microsoft Azure regarding the connectivity and availability issues we observed earlier.\n\nMicrosoft 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.\n\nCurrent 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.",
"created_at": "2025-12-05T20:25:20Z",
"display_at": "2025-12-05T20:25:20Z",
"id": "01KBR31J00EX964CHH2425X813",
"incident_id": "01KBPP2FM307P2H9N3ZEEQ4J59",
"status": "investigating",
"updated_at": "2025-12-05T20:25:20Z"
},
{
"body": "We have received official confirmation from Microsoft Azure regarding the connectivity and availability issues we observed earlier.\n\nMicrosoft 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.\n\nCurrent 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.",
"created_at": "2025-12-05T19:00:08Z",
"display_at": "2025-12-05T19:00:08Z",
"id": "01KBQY5JKC3PNCRHY1NDBD1GF7",
"incident_id": "01KBPP2FM307P2H9N3ZEEQ4J59",
"status": "investigating",
"updated_at": "2025-12-05T19:00:08Z"
},
{
"body": "We have received official confirmation from Microsoft Azure regarding the connectivity and availability issues we observed earlier.\n\nMicrosoft 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.\n\nCurrent 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.",
"created_at": "2025-12-05T16:53:39Z",
"display_at": "2025-12-05T16:53:39Z",
"id": "01KBQPXYNY9XS9P38RWYCTCHD0",
"incident_id": "01KBPP2FM307P2H9N3ZEEQ4J59",
"status": "investigating",
"updated_at": "2025-12-05T16:53:39Z"
},
{
"body": "We have received official confirmation from Microsoft Azure regarding the connectivity and availability issues we observed earlier.\n\nMicrosoft 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.\n\nCurrent 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.",
"created_at": "2025-12-05T13:58:23Z",
"display_at": "2025-12-05T13:58:23Z",
"id": "01KBQCX1N0JN5EVQ71650B6HDS",
"incident_id": "01KBPP2FM307P2H9N3ZEEQ4J59",
"status": "investigating",
"updated_at": "2025-12-05T13:58:23Z"
},
{
"body": "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.\n\nAlthough 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.\n\nWe apologise for the inconvenience caused by this issue.",
"created_at": "2025-12-05T07:19:24Z",
"display_at": "2025-12-05T07:19:24Z",
"id": "01KBPP2FM3S73PQGPENQAET51F",
"incident_id": "01KBPP2FM307P2H9N3ZEEQ4J59",
"status": "investigating",
"updated_at": "2025-12-05T07:19:24Z"
}
],
"name": "Investigating connectivity issues in Azure Norway West region",
"page_id": "01H0FX8N7BG3M9PMMX0J0HENJF",
"resolved_at": "2025-12-06T03:35:09Z",
"status": "resolved",
"updated_at": "2026-03-12T18:31:00Z"
},
{
"created_at": "2025-12-04T17:12:15Z",
"id": "01KBN5KA3TTTF3MAWSRXEXBCCX",
"impact": "none",
"incident_updates": [
{
"body": "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.",
"created_at": "2025-12-04T19:17:24Z",
"display_at": "2025-12-04T19:17:24Z",
"id": "01KBNCRECNABDXBPP7N0KPQPX3",
"incident_id": "01KBN5KA3TTTF3MAWSRXEXBCCX",
"status": "resolved",
"updated_at": "2025-12-04T19:17:24Z"
},
{
"body": "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.",
"created_at": "2025-12-04T18:48:32Z",
"display_at": "2025-12-04T18:48:32Z",
"id": "01KBNB3JZNC2E9ZAWZGYRSSAN7",
"incident_id": "01KBN5KA3TTTF3MAWSRXEXBCCX",
"status": "investigating",
"updated_at": "2025-12-04T18:48:32Z"
},
{
"body": "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.\n\nWe apologize for the inconvenience and appreciate your patience while we resolve this issue.",
"created_at": "2025-12-04T17:12:15Z",
"display_at": "2025-12-04T17:12:15Z",
"id": "01KBN5KA3T4YFPZWG7XRCAJ5EP",
"incident_id": "01KBN5KA3TTTF3MAWSRXEXBCCX",
"status": "investigating",
"updated_at": "2025-12-04T17:12:15Z"
}
],
"name": "Metrics API Outage",
"page_id": "01H0FX8N7BG3M9PMMX0J0HENJF",
"resolved_at": "2025-12-04T19:17:24Z",
"status": "resolved",
"updated_at": "2026-03-12T18:31:00Z"
},
{
"created_at": "2025-11-24T03:39:21Z",
"id": "01KASZ3MPKMYCEDM9WXPX1ZKDD",
"impact": "none",
"incident_updates": [
{
"body": "We have confirmed that the incident has been resolved, and all the PG replicas are operating normally.\n\nWe apologise for the inconvenience caused by this issue.",
"created_at": "2025-11-24T05:38:38Z",
"display_at": "2025-11-24T05:38:38Z",
"id": "01KAT5Y2H0GYPNFTKSREEAMX4B",
"incident_id": "01KASZ3MPKMYCEDM9WXPX1ZKDD",
"status": "resolved",
"updated_at": "2025-11-24T05:38:38Z"
},
{
"body": "The root cause for the issue was identified (some credentials were disabled as part of a previous incident). \n\nAfter enabling the credentials back there is no PG replicas reporting the issue.\n\nIf you find any problem with your PG replicas please contact Aiven support.",
"created_at": "2025-11-24T04:51:01Z",
"display_at": "2025-11-24T04:51:01Z",
"id": "01KAT36W9DV9RHN4QKJ2B2VZXC",
"incident_id": "01KASZ3MPKMYCEDM9WXPX1ZKDD",
"status": "monitoring",
"updated_at": "2025-11-24T04:51:01Z"
},
{
"body": "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.\n\nWe will provide status updates for this incident as more information becomes available.",
"created_at": "2025-11-24T03:39:21Z",
"display_at": "2025-11-24T03:39:21Z",
"id": "01KASZ3MPKF92FD9P4VC8N558B",
"incident_id": "01KASZ3MPKMYCEDM9WXPX1ZKDD",
"status": "investigating",
"updated_at": "2025-11-24T03:39:21Z"
}
],
"name": "Availability affected for some PG read replica nodes.",
"page_id": "01H0FX8N7BG3M9PMMX0J0HENJF",
"resolved_at": "2025-11-24T05:38:38Z",
"status": "resolved",
"updated_at": "2026-03-12T18:31:00Z"
},
{
"created_at": "2025-11-19T22:05:11Z",
"id": "01KAF2CX93VCVN3MBBPJ4ND0VN",
"impact": "major",
"incident_updates": [
{
"body": "We have identified a mitigation to resolve the issues causing PostgreSQL services not being able to be powered on after being powered off. \n\nWe are continuing to monitor closely to ensure no further problems.\n\nWe apologise for the inconvenience caused by this issue. ",
"created_at": "2025-11-20T00:07:14Z",
"display_at": "2025-11-20T00:07:14Z",
"id": "01KAF9CCC4DPB8J1HFB0F3AGFQ",
"incident_id": "01KAF2CX93VCVN3MBBPJ4ND0VN",
"status": "resolved",
"updated_at": "2025-11-20T00:07:14Z"
},
{
"body": "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.\n\nThis 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.\n\nWe'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. \n\nWe'll continue to update the status of this incident here.",
"created_at": "2025-11-19T23:49:26Z",
"display_at": "2025-11-19T23:49:26Z",
"id": "01KAF8BSNH8QXT9XN1QEWYRKAH",
"incident_id": "01KAF2CX93VCVN3MBBPJ4ND0VN",
"status": "investigating",
"updated_at": "2025-11-19T23:49:26Z"
},
{
"body": "We're currently experiencing an issue powering on PostgreSQL services.\n\nThis 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.\n\nThis 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.\n\nWe're investigating the cause of the issue for possible mitigations that we can apply.\n\nWe'll continue to update the status of this incident here.",
"created_at": "2025-11-19T22:05:11Z",
"display_at": "2025-11-19T22:05:11Z",
"id": "01KAF2CX93WH0MVBY2YBJRZ0BY",
"incident_id": "01KAF2CX93VCVN3MBBPJ4ND0VN",
"status": "investigating",
"updated_at": "2025-11-19T22:05:11Z"
}
],
"name": "Issue preventing power on of PostgreSQL services",
"page_id": "01H0FX8N7BG3M9PMMX0J0HENJF",
"resolved_at": "2025-11-20T00:07:14Z",
"status": "resolved",
"updated_at": "2026-03-12T18:31:00Z"
},
{
"created_at": "2025-11-18T12:08:38Z",
"id": "01KABDVVSC79P1Z54WVXFVTWM0",
"impact": "none",
"incident_updates": [
{
"body": "Cloudflare has resolved the issues on their side and our platform has returned to normal operation. No impact was observed on any running services.\n\nShould any further issues be encountered, please reach out to support via the Aiven console.",
"created_at": "2025-11-18T19:06:12Z",
"display_at": "2025-11-18T19:06:12Z",
"id": "01KAC5REPRQEMXW52P75EM4EYH",
"incident_id": "01KABDVVSC79P1Z54WVXFVTWM0",
"status": "resolved",
"updated_at": "2025-11-18T19:06:12Z"
},
{
"body": "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.",
"created_at": "2025-11-18T14:44:56Z",
"display_at": "2025-11-18T14:44:56Z",
"id": "01KABPT220TJ9AY0Q5GK26FQ8A",
"incident_id": "01KABDVVSC79P1Z54WVXFVTWM0",
"status": "investigating",
"updated_at": "2025-11-18T14:44:56Z"
},
{
"body": "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/\").\nRunning services are not impacted.\nThis incident is caused by an ongoing outage within the Cloudflare Global Network. We are monitoring the situation closely.\nCloudflare Incident Report:[https://www.cloudflarestatus.com/incidents/8gmgl950y3h7](https://www.cloudflarestatus.com/incidents/8gmgl950y3h7 \"https://www.cloudflarestatus.com/incidents/8gmgl950y3h7\")",
"created_at": "2025-11-18T12:30:32Z",
"display_at": "2025-11-18T12:30:32Z",
"id": "01KABF3Z0HH3NA2GFVQHVFJDWC",
"incident_id": "01KABDVVSC79P1Z54WVXFVTWM0",
"status": "investigating",
"updated_at": "2025-11-18T12:30:32Z"
},
{
"body": "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/\").\nThis incident is caused by an ongoing outage within the Cloudflare Global Network. We are monitoring the situation closely.\nCloudflare Incident Report: [https://www.cloudflarestatus.com/incidents/8gmgl950y3h7](https://www.cloudflarestatus.com/incidents/8gmgl950y3h7 \"https://www.cloudflarestatus.com/incidents/8gmgl950y3h7\")\n\nWe apologise for the inconvenience caused by this issue. We will provide a further update as soon as possible.",
"created_at": "2025-11-18T12:08:38Z",
"display_at": "2025-11-18T12:08:38Z",
"id": "01KABDVVSCK6PY7Y8EVV84TYYD",
"incident_id": "01KABDVVSC79P1Z54WVXFVTWM0",
"status": "investigating",
"updated_at": "2025-11-18T12:08:38Z"
}
],
"name": "Aiven Console and aiven.io down",
"page_id": "01H0FX8N7BG3M9PMMX0J0HENJF",
"resolved_at": "2025-11-18T19:06:12Z",
"status": "resolved",
"updated_at": "2026-03-12T18:31:00Z"
},
{
"created_at": "2025-11-06T04:24:09Z",
"id": "01K9BPGQNV74ZQPQ145MFM7V5R",
"impact": "major",
"incident_updates": [
{
"body": "The root cause of this incident has been fixed. All impacted PostgreSQL 18 nodes are operating normally. \n\nWe 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.",
"created_at": "2025-11-06T07:35:58Z",
"display_at": "2025-11-06T07:35:58Z",
"id": "01K9C1FZA1A2JTTD2BDYBRJVSQ",
"incident_id": "01K9BPGQNV74ZQPQ145MFM7V5R",
"status": "resolved",
"updated_at": "2025-11-06T07:35:58Z"
},
{
"body": "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. \n\nOur 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. \n\nWe will continue to closely monitor system performance to ensure continued platform stability.",
"created_at": "2025-11-06T07:03:04Z",
"display_at": "2025-11-06T07:03:03Z",
"id": "01K9BZKQ0Z3K0S8QPJED6B7MKG",
"incident_id": "01K9BPGQNV74ZQPQ145MFM7V5R",
"status": "monitoring",
"updated_at": "2025-11-06T07:03:04Z"
},
{
"body": "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. \n\nWe 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.\n\nIf you continue to experience issues, please reach out to Aiven Support.",
"created_at": "2025-11-06T05:00:05Z",
"display_at": "2025-11-06T05:00:05Z",
"id": "01K9BRJH51JPK5R75T0S83Y0D3",
"incident_id": "01K9BPGQNV74ZQPQ145MFM7V5R",
"status": "monitoring",
"updated_at": "2025-11-06T05:00:05Z"
},
{
"body": "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.",
"created_at": "2025-11-06T04:24:09Z",
"display_at": "2025-11-06T04:24:09Z",
"id": "01K9BPGQNV5QMZNZWHXM2D2QF6",
"incident_id": "01K9BPGQNV74ZQPQ145MFM7V5R",
"status": "investigating",
"updated_at": "2025-11-06T04:24:09Z"
}
],
"name": "PostgreSQL nodes unable to start",
"page_id": "01H0FX8N7BG3M9PMMX0J0HENJF",
"resolved_at": "2025-11-06T07:35:58Z",
"status": "resolved",
"updated_at": "2026-03-12T18:31:00Z"
},
{
"created_at": "2025-10-31T11:32:28Z",
"id": "01K8X0MPH4GQEJX7G9DA3DMQJW",
"impact": "major",
"incident_updates": [
{
"body": "**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.",
"created_at": "2025-10-31T13:36:24Z",
"display_at": "2025-10-31T13:36:24Z",
"id": "01K8X7QMTVF3ED6V3HZKVNHKFF",
"incident_id": "01K8X0MPH4GQEJX7G9DA3DMQJW",
"status": "resolved",
"updated_at": "2025-10-31T13:36:24Z"
},
{
"body": "**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.",
"created_at": "2025-10-31T11:59:11Z",
"display_at": "2025-10-31T11:59:11Z",
"id": "01K8X25KXYG6CGR53MW6DE5PRF",
"incident_id": "01K8X0MPH4GQEJX7G9DA3DMQJW",
"status": "monitoring",
"updated_at": "2025-10-31T11:59:11Z"
},
{
"body": "**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.",
"created_at": "2025-10-31T11:35:20Z",
"display_at": "2025-10-31T11:35:20Z",
"id": "01K8X0SYM1CPE959K7Y3FJ1J1R",
"incident_id": "01K8X0MPH4GQEJX7G9DA3DMQJW",
"status": "investigating",
"updated_at": "2025-10-31T11:35:20Z"
},
{
"body": "**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.",
"created_at": "2025-10-31T11:32:28Z",
"display_at": "2025-10-31T11:32:28Z",
"id": "01K8X0MPH4MKNMNB2J2ETSXDXD",
"incident_id": "01K8X0MPH4GQEJX7G9DA3DMQJW",
"status": "investigating",
"updated_at": "2025-10-31T11:32:28Z"
}
],
"name": "Multiple service types cannot start",
"page_id": "01H0FX8N7BG3M9PMMX0J0HENJF",
"resolved_at": "2025-10-31T13:36:24Z",
"status": "resolved",
"updated_at": "2026-03-12T18:31:00Z"
},
{
"created_at": "2025-10-29T17:04:42Z",
"id": "01K8REVKATE4MRBMZQ4WHZYAWD",
"impact": "major",
"incident_updates": [
{
"body": "RESOLVED: 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.",
"created_at": "2025-10-29T21:18:40Z",
"display_at": "2025-10-29T21:18:40Z",
"id": "01K8RXCMGAQW1X0X5Q2R2NDK81",
"incident_id": "01K8REVKATE4MRBMZQ4WHZYAWD",
"status": "resolved",
"updated_at": "2025-10-29T21:18:40Z"
},
{
"body": "We have identified an issue where services in BYOC environments are struggling to spin up new nodes. Our engineering team have identified a fix and currently working on applying the same. Please open a support ticket with us if you have BYOC service that is currently stuck in rebalancing or creating new nodes.",
"created_at": "2025-10-29T18:05:59Z",
"display_at": "2025-10-29T18:05:59Z",
"id": "01K8RJBSXVT1VN0VZP991VKZSF",
"incident_id": "01K8REVKATE4MRBMZQ4WHZYAWD",
"status": "monitoring",
"updated_at": "2025-10-29T18:06:13Z"
},
{
"body": "We have identified an issue where services in BYOC environments are struggling to spin up new nodes. Our engineering team is currently working on the mitigation for the issue. Please open a support ticket with us if you have BYOC service that is currently stuck in rebalancing or creating new nodes.",
"created_at": "2025-10-29T17:04:42Z",
"display_at": "2025-10-29T17:04:42Z",
"id": "01K8REVKATATSZACYFBJ7CANHE",
"incident_id": "01K8REVKATE4MRBMZQ4WHZYAWD",
"status": "identified",
"updated_at": "2025-10-29T17:05:15Z"
}
],
"name": "Nodes struggling to spin in BYOC environments",
"page_id": "01H0FX8N7BG3M9PMMX0J0HENJF",
"resolved_at": "2025-10-29T21:18:40Z",
"status": "resolved",
"updated_at": "2026-03-12T18:31:00Z"
}
],
"page": {
"id": "01H0FX8N7BG3M9PMMX0J0HENJF",
"name": "Aiven",
"updated_at": "2026-09-30T06:35:21Z",
"url": "https://status.aiven.io/"
}
}