Aiven 中断历史

1. 2026年10月20日 UTC 06:43investigating

   我们正在调查正在发生的谷歌云VPN事件,它影响到了欧洲西部2和非洲-南部1个区域。 这影响到各节点之间的网络连通性,并可能影响在受影响地区提供集成的艾文服务及其绩效。 我们的小组正在调查影响并监测受影响的服务。 一旦获得更多信息,我们将提供进一步的最新资料.

2. 2026年10月20日 UTC 06:51investigating

   我们正在调查谷歌云联网事件 Google Cloud工程师证实Virtual Private Cloud(VPC)网络存在影响虚拟机之间通信的问题,包括内部IP地址上的通信,IPv6等网络路径. ``` 目前据报道,该事件影响到了以下地区: 非洲:非洲-南方1 欧洲:欧-中,欧-北 1,欧-北 2,欧-西南 1,欧-西 1,欧-西 2,欧-西3,欧-西4,欧-西6,欧-西8,欧-西9,欧-西10,欧-西12 ``` 这个问题正在影响节点之间的网络连接,并可能影响在受影响地区提供分组的艾文服务及其绩效。 我们的小组正在调查影响并监测受影响的服务。 一旦获得更多信息,我们将提供进一步的最新资料.

3. 2026年10月20日 UTC 08:44investigating

   最新资料指出,西欧2和西欧2-b区是受影响的地点。 事件涉及Virtual Private Cloud(VPC)的网络问题,可中断虚拟机之间的通信. 这可能影响到节点之间的连通性以及受影响地点的集群Aiven服务。 我们的小组继续调查对受影响服务的影响并监测其健康。 一旦获得更多信息,我们将分享进一步的最新情况.

4. 2026年10月20日 UTC 11:10investigating

   最新资料将 " Europe-West2 " 和 " Europe-West2-b " 区确定为受影响的地点。 该事件涉及Virtual Private Cloud(VPC)的网络问题,干扰了受影响地段虚拟机之间的通信,这影响了集群Aiven服务的提供——目前Apache Kafka的Aiven和OpenSearch的Aiven. 我们继续监测我们的服务,以查明任何剩余的受影响服务,我们正在等待从谷歌方面恢复连接,并等待受影响的节点返回。 一旦获得更多信息,我们将分享进一步的最新情况.

5. 2026年10月20日 UTC 14:10investigating

   我们继续回应影响欧洲西部地区的谷歌云事件。 基本的Google Cloud问题——欧洲-西-B区的停电被Google缓解了,大部分工作量的恢复从15:10 EEST开始. 在恢复过程中,在受灾地区运行的服务可能得不到或退化。 我们看到服务正在恢复,并正在优先恢复现有工作量。 客户可能尚不能产生新的工作量。 我们正在积极恢复受影响的服务,包括回收受影响的卡夫卡节点,并通过需要额外步骤的OpenSearch和PostgreSQL服务开展工作。 我们正在密切监测局势,并将继续下去,直到所有受影响的服务健康为止.

6. 2026年10月20日 UTC 18:10monitoring

   已知受"Google Cloud"事件影响的所有PG和Kafka服务在欧洲-西2被回收. 我们正在恢复和修复已知的Opensearch服务。 我们正在继续监测该地区的所有服务,以确认它们依然健康。 若您在西欧地区仍有问题,请联系Aiven Support.

7. 2026年10月20日 UTC 18:55monitoring

   所有已知受"Google Cloud"事件影响的艾文服务在欧洲-西2被恢复. 在Google缓解了欧洲-West2-b区的停电后,我们恢复了阿帕奇·卡夫卡(Apache Kafka),OpenSearch(OpenSearch)和PostgreSQL(PostgreSQL)服务受影响的艾文(Aiven)通过收复节点或取而代之. 我们正在继续监测该地区的所有服务,以确认它们依然健康。 若您在西欧地区仍有问题,请联系Aiven Support.

8. 2026年10月20日 UTC 19:30resolved

   这一事件已经得到解决。 Google Cloud的欧洲-West2-b区停电, 灾区的节点被恢复后重新启动. 部分影响Apache Kafka的Aiven,OpenSearch的Aiven,PostgreSQL的Aiven和Valkey服务的Aiven在恢复正常运行前需要额外的恢复步骤或节点替换. 所有受影响的服务现已恢复。 我们为干扰道歉.

自动翻译自官方事件更新。

1. 2026年10月18日 UTC 10:54investigating

   在**vultr-ewr**云区的节点的建立和替换正遇到问题,出现可能比正常需要更长的时间。 已经运行的服务不受影响. 我们的工程组正在积极进行这项工作,一旦我们得到更多信息,我们将提供另一个最新情况.

2. 2026年10月19日 UTC 04:06resolved

   我们已经解决了在**vultr-ewr**云区域建立和替换节点的根本问题。 如果遇到进一步的问题,请通过艾文控制台伸出援手。 我们对该问题造成的不便表示歉意,并承诺分析和改进我们的平台,以避免今后发生类似这种情况的事件.

自动翻译自官方事件更新。

1. 2026年10月16日 UTC 08:40investigating

   目前,我们正面临为几乎所有服务类型启动新的服务节点的问题。 运行的节点不受影响 。 我们的工程组正在积极研究一个解决方案,一旦我们掌握更多信息,我们将提供另一个最新情况.

2. 2026年10月16日 UTC 09:56monitoring

   一项措施已经执行,我们正在监测结果。 新的服务节点可以再次启动,运行的节点在任何时刻都没有受到影响. 一旦我们确认这一问题已完全解决,我们将提供进一步的最新情况.

3. 2026年10月16日 UTC 13:31resolved

   这一事件已经得到解决。 新的服务节点能够正常地重新开始,运行的节点在事件期间的任何时候都没有受到影响. 我们对此可能造成的不便表示歉意.

自动翻译自官方事件更新。

1. 2026年10月12日 UTC 00:04investigating

   我们有问题 在google Asia-东南1区域 我们无法旋转节点。 这是由于我们正在研究的一个上游云提供方问题。 我们正在调查,并将在今后30分钟内更新进一步的细节.

2. 2026年10月12日 UTC 03:09investigating

   我们正在调查一个防止在东南一带建立节点的问题。 这个问题只影响到一些用户。 工程在GCP的支持下积极投入. 30分钟后更新.

3. 2026年10月16日 UTC 05:04identified

   我们查明了防止在东南一带建立节点问题的根源。 我们的团队正与GCP合作执行一个定律. 一旦获得更多信息,我们将提供另一个最新情况.

4. 2026年10月16日 UTC 14:38resolved

   我们已经解决了Google Asia-Southest1地区这一问题的根本原因。 如果遇到进一步的问题,请通过艾文控制台伸出援手。 我们对该问题造成的不便表示歉意.

自动翻译自官方事件更新。

1. 2026年9月29日 UTC 20:14investigating

   我们目前正在调查一个影响Aiven PostgreSQL服务的问题,其中重大版本升级可以使服务处于无法使用状态. 我们建议客户此时不要启动PostgreSQL主要版本升级. 如果您已经启动一个主要版本升级, 且您的服务没有响应, 请联系支援团队@ aiven.io 。 我们的工程队正积极努力查明根源并恢复受影响的服务。 一旦获得更多信息,我们将提供进一步的最新资料。 我们为不方便而道歉.

2. 2026年9月29日 UTC 21:59identified

   我们对影响Aiven上PostgreSQL服务的主要版本升级的问题有了缓解。 请继续避免引发目前的重大版本升级. 随着缓解措施的部署,正在恢复受影响的服务。 我们将随着推出的进展提供进一步的最新情况。 我们为不方便而道歉.

3. 2026年9月29日 UTC 23:50identified

   PostgreSQL主要版本升级可以再次进行. 少数因早先升级失败而受到影响的服务目前正在修复。 如果需要任何行动,我们会直接与客户联系, 一旦修复完成,我们会在这里发布另一个更新.

4. 2026年9月30日 UTC 00:30monitoring

   受这个问题影响的所有客户服务都已恢复,你无需采取进一步行动。 现在可以进行PostgreSQL主要版本的升级。 我们对此造成的破坏表示歉意.

5. 2026年9月30日 UTC 00:41resolved

   受这个问题影响的所有客户服务都已恢复,你无需采取进一步行动。 现在可以进行PostgreSQL主要版本的升级。 我们对此造成的破坏表示歉意.

自动翻译自官方事件更新。

1. 2026年9月22日 UTC 00:55investigating

   我们知道一个影响艾文API的问题. Aiven Console, Aiven CLI, Terraform 供应商和任何自定义的脚本或集成器都通过这个相同的API运行,因此顾客可能会在其中任何一个都看到出错. 您可能经历无法加载或签名到控制台,以及创建、修改或查询服务时出现故障。 我们的工程组正在调查 恢复服务的工作正在进行 我们将在30分钟内提供进一步的最新资料,如果有消息要分享,则更早提供。 我们为干扰道歉.

2. 2026年9月22日 UTC 02:28identified

   我们查明了这一问题的原因,目前正在我们API各节点分阶段推出一个解决办法。 Aiven Console和API已经重新为一些客户工作了. 在推出完成之前,您仍然可能看到间歇性登录失败,或者在通过Console,CLI,Terraform提供者或直接API呼叫创建,修改或查询服务时出现错误. 重试往往会成功. 待推出完成后我们会确认 谢谢你的耐心.

3. 2026年9月22日 UTC 03:36identified

   我们API的节点 仍然在启动 大多数客户现在应该找到Aiven Console,API,CLI和Terraform供应商正常工作,我们期望随着推出的完成,任何剩余的错误都会被清除. 完成后我们会在这里确认 谢谢你的耐心.

4. 2026年9月22日 UTC 05:54monitoring

   这一事件现已得到解决。 9月22日 UTC凌晨0点10分到02点05分左右,一个影响我们公共API端点的问题给使用Aiven Console,Aiven API,CLI,Terraform供应商和其他基于API的集成的客户造成了登录失败和出错. 这个问题已经得到纠正,我们监测期间没有看到进一步的错误。 我们正在采取进一步的改革措施,以防止这种情况再次发生。 我们为干扰道歉。 如果您还遇到问题,请联系艾文支援.

5. 2026年9月22日 UTC 08:05resolved

   这一事件现已得到解决。 今天早些时候,一个影响我们公共API端点的证书问题给使用Aiven Console,Aiven API,CLI,Terraform供应商和其他基于API的集成的客户造成了登录失败和出错. 自协调世界时02:05起,所有API节点都设置了经更正的证书,我们在监测期间没有看到进一步的错误。 我们正在采取长期措施,防止这种情况再次发生。 我们为中断道歉。 如果您还看到问题,请联系 Aiven 支援 [[email protected]] (mailto:[email protected])

自动翻译自官方事件更新。

1. 2026年9月21日 UTC 04:57investigating

   我们正在调查用户无法登录到Aiven控制台的报告。 我们将尽快分享进一步的最新情况.

2. 2026年9月21日 UTC 05:27investigating

   我们还在调查一个影响艾文控制台的问题 目前客户无法直接通过门户网站创建或提交新的支持票. 如果您在与Aiven Console倒台无关的紧急问题上需要援助,请发电子邮件至[[email protected]] (mailto:[email protected]). 我们的支援小组将直接处理你的请求.

3. 2026年9月21日 UTC 06:01monitoring

   已经为Aiven Console安装了固定装置并恢复了门户功能。 我们目前正在监测执行情况。 如果您遇到任何问题,请发电子邮件[[email protected]] (mailto:[email protected])

4. 2026年9月21日 UTC 08:25resolved

   这一事件已经得到解决。 Aiven Console登录及通过门户网站支持出票创建再次全面运行. 我们继续监测执行情况,没有看到进一步的问题。 如果您遇到任何问题,请发电子邮件[[email protected]] (mailto:[email protected]).

自动翻译自官方事件更新。

1. 2026年9月16日 UTC 12:21investigating

   我们正在调查在艾文平台上为服务建立新的节点的问题。 效果是新节点的创建时间更慢. 任何新建节点的事件都会受到影响,例如故障、切换、升级和维护更新。 我们的工程师目前正在调查问题的根源,并努力解决这个问题。 我们对该问题造成的不便表示歉意。 随着我们小组继续讨论解决这一局势的办法,我们将提供进一步的最新情况.

2. 2026年9月16日 UTC 13:58monitoring

   我们正在通过在艾文平台上创建新的服务节点来监测我们的减轻影响行动。 我们的工程师已经做了缓解步骤,我们看到了节点创建方面的改进,但我们将继续调查和监督这个问题. 我们对该问题造成的不便表示歉意。 随着我们的小组继续监测和划分这一局势,我们将提供进一步的最新情况.

3. 2026年9月16日 UTC 15:04monitoring

   我们完成了减缓行动,在艾文平台设立新的服务节点的工作已恢复正常。 客户现在可以进行这个问题期间延误的任何业务,包括服务创建、规模化、升级、维护更新和配置变化。 有待处理的业务应自动继续进行。 我们的工程师们继续监测这个平台,以确认这个问题已经完全解决。 我们对该问题造成的不便表示歉意。 在我们的小组完成对这种情况的监测时,我们将提供进一步的最新情况.

4. 2026年9月30日 UTC 06:35resolved

   我们已经解决了新节点产生的根本原因,并且能够不带问题地创建出新的节点。 如果遇到进一步的问题,请通过艾文控制台伸出援手。 我们对该问题造成的不便表示歉意,并承诺分析和改进我们的平台,以避免今后发生类似这种情况的事件.

自动翻译自官方事件更新。

1. 2026年8月8日 UTC 21:28investigating

   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. 2026年8月8日 UTC 21:50investigating

   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. 2026年8月9日 UTC 06:28resolved

   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. 2026年7月29日 UTC 14:29investigating

   我们正在调查一个影响动态磁盘大小(DDS)的问题,在其中,调整操作可能失败于一小部分新创建的节点。 目前正在采取缓解措施.

2. 2026年7月29日 UTC 15:17identified

   已查明问题,并正在采取补救措施。 谢谢你的耐心.

3. 2026年7月29日 UTC 17:07resolved

   我们的小组成功地对所有受影响的节点采取了适当的缓解措施,并部署了固定装置来防止今后发生.

自动翻译自官方事件更新。

1. 2026年7月2日 UTC 23:24investigating

   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. 2026年7月3日 UTC 02:20investigating

   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. 2026年7月3日 UTC 04:56monitoring

   ``` 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. 2026年7月3日 UTC 05:28resolved

   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. 2026年6月25日 UTC 10:16identified

   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. 2026年6月25日 UTC 12:27monitoring

   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. 2026年6月25日 UTC 13:14resolved

   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. 2026年6月23日 UTC 14:18investigating

   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. 2026年6月23日 UTC 15:10identified

   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. 2026年6月24日 UTC 15:01identified

   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. 2026年6月25日 UTC 08:06monitoring

   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. 2026年6月25日 UTC 11:38resolved

   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. 2026年6月11日 UTC 15:25investigating

   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. 2026年6月15日 UTC 14:01monitoring

   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. 2026年6月16日 UTC 11:05resolved

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

1. 2026年6月9日 UTC 15:10investigating

   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. 2026年6月9日 UTC 15:57identified

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

3. 2026年6月9日 UTC 16:18monitoring

   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. 2026年6月9日 UTC 16:36monitoring

   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. 2026年6月9日 UTC 16:57resolved

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

1. 2026年5月25日 UTC 02:29investigating

   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. 2026年5月25日 UTC 03:48identified

   ``` 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. 2026年5月25日 UTC 03:54resolved

   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. 2026年5月20日 UTC 01:15investigating

   ``` 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. 2026年5月20日 UTC 02:38resolved

   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. 2026年5月14日 UTC 06:55investigating

   ``` 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. 2026年5月14日 UTC 07:36identified

   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. 2026年5月14日 UTC 10:49monitoring

   ``` 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. 2026年5月14日 UTC 15:13monitoring

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

5. 2026年5月15日 UTC 23:13resolved

   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. 2026年3月1日 UTC 23:12monitoring

   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. 2026年3月2日 UTC 08:16monitoring

   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. 2026年3月2日 UTC 15:38monitoring

   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. 2026年3月3日 UTC 03:01monitoring

   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. 2026年4月2日 UTC 11:23resolved

   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. 2025年12月12日 UTC 11:33investigating

   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. 2025年12月12日 UTC 21:20identified

   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. 2025年12月17日 UTC 13:58resolved

   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.