Wasabi 中断历史

1. 2026年10月10日 UTC 02:27investigating

   我们目前正在调查影响AP-SOUTHEAST-1(新加坡)区域的问题。 由于现场发生电力事件,该区域的服务受到影响,客户可能遇到错误或请求失败.

2. 2026年10月10日 UTC 02:55monitoring

   我们的小组已经查明并解决了这个问题。 在一切恢复正常的时候,我们将继续监测,然后我们才能将这一事件定为已经解决的事件.

3. 2026年10月10日 UTC 04:11resolved

   事件得到解决

4. 2026年10月13日 UTC 14:10postmortem

   2026年10月10日,在协调世界时01:10至02:30之间,由于数据中心的动力单元故障,顾客在新加坡地区可能遭遇了性能下降和出错率上升. 故障中断了与基本基础设施的连接,降低了交通水平并中断了API业务。 数据中心团队更换了已失效的单元并恢复了UTC大约02:23的功率. 我们的团队随后与数据中心供应商合作,在协调世界时02:30将受影响的设备重新上线,之后服务恢复并恢复了正常水平. 我们监测了恢复情况,以证实行动已恢复正常。 如有任何问题,请联系[[email protected]](电邮:[email protected]).

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

1. 2026年10月6日 UTC 07:08investigating

   我们正在调查一些客户 难以进入瓦萨比控制台。 作为选择尝试使用您的区域 URL, 例如 : 控制台.us-east-1.wasabisys.com 或者说 控制台.us-east-2.wasabisys.com 或者说 控制台.us-west-1.wasabisys.com 类

2. 2026年10月6日 UTC 08:51resolved

   这件事已经解决了

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

1. 2026年9月1日 UTC 08:31investigating

   我们正在调查一个问题,WaCM报告子账户的存储利用率为0%,而不是实际价值

2. 2026年9月1日 UTC 10:36resolved

   影响WACM存储利用数据的问题已经解决. 数据同步已经完成,现在WACM应提出正确的数值. 请联系支援@wasabi.com 如果您继续看到与此事件相关的任何问题.

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

1. 2026年8月25日 UTC 23:46investigating

   我们正在调查美国-EAST-1地区正在发生的影响一些PUT(Api)电话的问题.

2. 2026年8月26日 UTC 01:09monitoring

   我们的小组已经查明并解决了这个问题。 在一切恢复正常的时候,我们将继续监测,然后我们才能将这一事件定为已经解决的事件.

3. 2026年8月26日 UTC 02:37resolved

   这个问题已经得到解决。 今天早些时候,由于我们的后端存在内部基础设施问题,我们美国-EAST-1区域的一些客户在PUT存储请求中可能遭遇了更高的延迟或出错. 我们的团队确定了原因 并应用了固定。 服务已完全恢复。 我们为任何不便而道歉.

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

1. 2026年8月4日 UTC 14:21resolved

   On 4 August 2026 from 07:36 UTC to 08:03 UTC, Wasabi S3 services in our Frankfurt (eu-central-2) region were unavailable due to a recent software update to our frontend infrastructure. Wasabi’s Operations Team was alerted by our automated monitoring systems to a drop on our ingestion traffic and started investigating. The updated was rolled back and services were fully restored on the region by 08:03 UTC.

1. 2026年7月15日 UTC 20:50resolved

   在2026-07-15 19:24 UTC和20:26 UTC之间,一子客户在通过新加坡控制台端点进行地理路由时遇到进入Wasabi管理控制台的问题. 一些受影响客户还报告说,难以通过控制台获取桶信息。 事件发生在新加坡控制台端点新内容提供配置推出期间. 在部署后,一些经过新道路的交通遇到了连接问题。 问题确定后,瓦萨比回滚了DNS的改变,恢复了之前的路线. 随着在全球传播DNS变化,服务恢复。 事件发生后,瓦萨比正在审查区域控制台线路变更的部署和验证过程,以改进部署前测试,减少今后推出期间对客户的影响,并加强部署后对区域交通的监测.

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

1. 2026年7月9日 UTC 20:11resolved

   2026年7月4日,从协调世界时16:09到协调世界时17:37,客户在访问瓦萨比管理控制台时体验到网络错误信息. 瓦萨比的作战小组查明了这个问题,并采取行动通过改道交通负荷来恢复服务稳定性. Wasabi Management Console功能在协调世界时17:37完全恢复. 如有任何问题,请联系@wasabi.com.

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

1. 2026年6月30日 UTC 02:54resolved

   Between 00:10 UTC and 18:00 UTC on June 29, some customers may have experienced increased latency and elevated HTTP 5XX error responses when performing API operations against buckets in the AP-NORTHEAST-2 (Osaka) region. The issue has been resolved. It was caused by a backend storage infrastructure issue that affected request processing performance. Our engineering team identified the cause, implemented corrective actions, and fully restored normal service.

2. 2026年7月2日 UTC 01:37postmortem

   Between 00:10 UTC and 18:00 UTC on June 29, some customers may have experienced increased latency and elevated HTTP 5XX error responses when performing API operations against buckets in AP-NORTHEAST-2. The issue was related to an infrastructure configuration introduced during expansion activities completed in June 2026. At the time of deployment, the environment operated within expected parameters and no customer impact was observed. Under subsequent production workload, the configuration resulted in degraded routing for a portion of storage traffic, leading to increased request latency and intermittent write timeouts for a subset of customer workloads. Once the issue was identified and correlated to the underlying configuration, the affected configuration was corrected and impacted storage services were restarted, restoring normal operation. Following the incident, Wasabi completed the following actions: * Corrected the infrastructure configuration responsible for the traffic routing issue. * Restored affected storage services and verified normal system performance. * Validated storage operation across the affected infrastructure before returning the environment to normal service. In order to avoid similar events in the future, Wasabi has implemented additional validation procedures during infrastructure deployment and configuration activities. These enhancements are intended to verify infrastructure configuration prior to production use and further strengthen deployment quality controls.

1. 2026年6月29日 UTC 03:47resolved

   Between 01:10 UTC and 02:15 UTC on June 25th, some customers may have experienced elevated HTTP 5XX error responses when accessing buckets in the AP-NORTHEAST-1 region. The issue has been resolved. It was caused by a transient issue affecting Wasabi backend components, which was automatically detected by our monitoring systems and promptly remediated by our engineering team.

1. 2026年5月27日 UTC 06:39investigating

   We are currently investigating intermittent Network Errors when creating or accessing buckets via Wasabi Console in some regions.

2. 2026年5月27日 UTC 09:12investigating

   We are continuing to investigate this issue.

3. 2026年5月27日 UTC 10:46monitoring

   The issue was identified and a fix implement by our team. We are currently monitoring our systems.

4. 2026年5月27日 UTC 13:38monitoring

   We are continuing to monitor for any further issues.

5. 2026年5月27日 UTC 13:39resolved

   This incident has been resolved.

6. 2026年6月3日 UTC 13:31postmortem

   Between 2026-05-26 13:40 UTC and 2026-05-27 09:20 UTC, some customers experienced intermittent difficulties accessing buckets through the Wasabi Console in the us-central-1, eu-central-1, eu-central-2, and eu-west-1 regions. The incident was caused by a deployment inconsistency introduced during a backend system update. As a result, a subset of backend services was running a different software version than expected, leading to intermittent failures when customers accessed bucket information through the Console. Following identification of the issue, Wasabi strengthened its deployment validation process to ensure software version consistency across production environments before feature activation. Additional release verification controls have been implemented to better align tested and deployed software, and we are evaluating improvements to version reporting and monitoring to increase deployment visibility and help identify potential discrepancies earlier.

1. 2026年5月21日 UTC 01:37investigating

   We are currently investigating System errors. Some customers experiencing HTTP 5XX error responses when interacting with their Wasabi buckets in AP-NORTHEAST-1 region.

2. 2026年5月21日 UTC 02:03monitoring

   The issue was identified and team performed the actions to resolve it. We are currently monitoring our systems.

3. 2026年5月21日 UTC 03:24resolved

   Incident resolved.

4. 2026年5月28日 UTC 00:56postmortem

   Between 2026-05-20 17:57 UTC and 2026-05-21 01:44 UTC, a subset of customers operating in the AP-NORTHEAST-1 region experienced intermittent HTTP 5xx errors impacting object storage operations. The issue was triggered by failures on a portion of the underlying storage hosts, resulting in temporary service instability within the region. The host failures occurred under elevated internal system activity associated with platform health-management operations and concurrent storage reclamation workflows. Service impact was intermittent throughout the event window. Wasabi has implemented additional operational safeguards and recovery workflows to accelerate remediation of impacted internal nodes. These enhancements improve recovery efficiency across high-availability infrastructure and further reduce the risk and duration of future service-impacting events.

1. 2026年5月13日 UTC 20:48resolved

   On May 8, 2026, at approximately 10:00 UTC, a set of accounts was incorrectly flagged as having exceeded their Storage Quota. These were reset manually by 12:57 UTC, restoring backend/API upload functionality. Some customers may have experienced errors when attempting customers attempted GDB/S3 uploads during the incident window and experienced actual upload blocking behavior. Additionally, some customers experienced WACM or Custom Cloud Console application errors during this time. On May 9, 2026, a fix was deployed to address the issue and prevent future occurances.

1. 2026年4月27日 UTC 18:06resolved

   On 25 April 2026, from 07:27 UTC to 12:50 UTC, customers experienced network errors and timeout messages when accessing the Wasabi Management Console via the US-East-1 endpoint. Wasabi’s Operations team identified the issue and took action to restore service stability by rerouting traffic load. Wasabi Management Console functionality in US-East-1 was fully restored by 12:50 UTC. For any questions, please reach out to [email protected].

1. 2026年3月30日 UTC 15:28resolved

   From 3/24 19:30 UTC to 3/25 10:15 UTC customers may have experienced elevated HTTP 5XX error responses when interacting with their Wasabi bucket(s) is AP-NORTHEAST-1 region. This issue has been resolved. For any questions please reach out to [email protected].

2. 2026年4月27日 UTC 23:38postmortem

   Between 24 March 2026 at 19:30 UTC and 25 March 2026 at 10:15 UTC, Wasabi S3 read operations in the Tokyo region \(ap-northeast-1\) were impacted for a small subset of customers and buckets. The impact was caused by a software deployment that unintentionally impacted one of our storage pools, resulting in the inability to access data stored on that pool. No other storage pools in the Tokyo region were affected. Once this was detected the pool was enabled again and data access restored. Procedural changes were added and active monitoring was already added to avoid this specific type of incident in the future.

1. 2026年2月6日 UTC 08:45investigating

   A power issue at the US-WEST-1 datacenter has been identified which is in the process of being restored.  We will update this page as we have more information.

2. 2026年2月6日 UTC 10:12identified

   The issue has been identified and a fix is being implemented.

3. 2026年2月6日 UTC 11:31monitoring

   All services are operational and are currently under monitoring.

4. 2026年2月6日 UTC 12:28resolved

   This incident has been resolved.

5. 2026年2月23日 UTC 14:23postmortem

   On 6 February 2026 from 06:30 UTC to approximately 10:02 UTC, Wasabi S3 services in our Hillsboro \(us-west-1\) region were unavailable due to a partial power issue within our datacenter facility. Wasabi’s Operations Team was alerted by our automated monitoring systems that multiple racks were experiencing power disruptions, which impacted customer access and operations during this time. The disruption originated within infrastructure hosted at Flexential’s Portland–Hillsboro 2 \(PDX02\) data center, where the failure of an upstream electrical distribution circuit breaker resulted in a loss of power to cabinets supporting affected systems. Flexential performed controlled restoration procedures and subsequently replaced the failed breaker under emergency change control. Following power restoration and comprehensive system validation checks by Wasabi’s Operations Team, services were progressively restored and us-west-1 region were fully operational.

1. 2025年11月20日 UTC 02:35investigating

   We are investigating issues regarding Wasabi Console access. Some customers were facing timeout or webpage taking a long time to load.

2. 2025年11月20日 UTC 02:42investigating

   We are continuing to investigate this issue.

3. 2025年11月20日 UTC 03:07monitoring

   Our team had identified the issue and the Wasabi Management Console access is back to normal. We will continue to monitoring the System status.

4. 2025年11月20日 UTC 04:06resolved

   Management Console Access is restored to Operational Status

1. 2025年10月23日 UTC 14:13investigating

   Customers attempting to log in to their Custom Cloud Console may receive a login error. We will update this page as we have more information.

2. 2025年10月23日 UTC 14:17identified

   The login issue with Custom Cloud Console has been identified and fixed.

3. 2025年10月23日 UTC 14:21monitoring

   Custom Cloud Console is now fully operational and being monitored by our Operations team.

4. 2025年10月23日 UTC 14:22resolved

   The login issue with Custom Cloud Console has been resolved.

1. 2025年9月22日 UTC 18:16resolved

   From 6:52AM to 7:04AM EST customers may have experienced elevated HTTP 5XX error responses when interacting with their Wasabi bucket(s). This issue has been resolved. For any questions please reach out to [email protected].

1. 2025年8月18日 UTC 16:12identified

   As a result of a recent database update, Wasabi’s data synchronization is currently delayed. The system is being managed and monitored to ensure that the data synchronization finishes properly and is up-to-date. Please report any problems you encounter with the display of Account Utilization data in WACM to [email protected].

2. 2025年8月18日 UTC 20:08monitoring

   The data synchronization job is currently running and is being monitored to ensure that the synchronization finishes properly and is up-to-date within the next 12 - 24 hours. We will update the status page as we get more information.

3. 2025年8月19日 UTC 12:37monitoring

   We are continuing to monitor for any further issues.

4. 2025年8月19日 UTC 12:39monitoring

   Issues affecting the response time for WACM have been resolved. Data synchronization is in progress and utilization data should be complete this morning.

5. 2025年8月20日 UTC 15:52resolved

   The WACM Utilization Data updates issue has been resolved. Please contact [email protected] if you continue to see any problem related to this incident.

1. 2025年7月25日 UTC 19:31investigating

   We are currently experiencing system errors in our EU-WEST-3 region. Customers may experience elevated HTTP 5XX error responses when interacting with their Wasabi bucket(s). We will update this page as we have more information.

2. 2025年7月25日 UTC 20:21identified

   We have identified the problem and our team is currently working to correct it.

3. 2025年7月25日 UTC 21:26monitoring

   The issue has been corrected by our Operations Team and the EU-WEST-3 region is now fully operational. We will continue to monitor the region

4. 2025年7月25日 UTC 22:32resolved

   This incident has been resolved.

5. 2025年8月27日 UTC 14:55postmortem

   On 25 July 2025 from 19:06 UTC to approximately 21:14 UTC, Wasabi's eu-west-3 \(London\) region experienced a service incident which resulted in elevated HTTP 5XX errors being returned for many request types to the region. The cause for the incident was an internal service failure, which prevented multiple services within the region from being able to successfully communicate across platforms. Due to this failure, our internal proxy service was unable to efficiently direct requests within the region, resulting in a degradation of the service and causing client requests to fail. Wasabi's Engineering and Operations teams worked to systematically restart impacted service hosts beginning at 19:20 UTC through 19:28 UTC. Once the hosts were back online, internal routing issues due to faulty configuration files required the team to manually correct the configurations and apply those to service hosts. By 21:24 UTC, all hosts and services were operating properly, and the region was operational.