Wasabi

Affected: AP-Southeast-1 (Singapore)

Failure mode: Hardware, power, cooling or another physical failure. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-10-10 02:27 UTC

   We are currently investigating an issue impacting the AP-SOUTHEAST-1 (Singapore) region. Due to a power event at the site, services in the region are impacted and customers may experience errors or failed requests.

2. monitoring 2026-10-10 02:55 UTC

   Our team has identified the issue and fixed it. At the moment everything is back to normal and we will continue to monitor before we mark this event as resolved.

3. resolved 2026-10-10 04:11 UTC

   Incident resolved

4. postmortem 2026-10-13 14:10 UTC

   On October 10, 2026, between 01:10 and 02:30 UTC, customers may have experienced degraded performance and elevated error rates in the Singapore region due to a power unit failure at the data center. The failure disrupted connectivity to the underlying infrastructure, reducing...

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

Affected: Wasabi Management Console

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

Names an upstream provider: AWS.

1. investigating 2026-10-06 07:08 UTC

   We are currently investigating some customers difficulty to access the Wasabi Console. As alternative try to use your region URL, example: console.us-east-1.wasabisys.com or console.us-east-2.wasabisys.com or console.us-west-1.wasabisys.com etc

2. resolved 2026-10-06 08:51 UTC

   This incident has been resolved

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

Affected: Wasabi Account Control Manager Console

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-01 08:31 UTC

   We are currently investigating an issue with WACM reporting 0% storage utilization for subaccounts instead of the actual value

2. resolved 2026-09-01 10:36 UTC

   Issue affecting WACM storage utilization data has been resolved. Data synchronization was completed and WACM should now present the correct values. Please contact support@wasabi.com if you continue to see any problem related to this incident.

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

Affected: US-East-1 (N. Virginia)

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-25 23:46 UTC

   We are currently investigating issues happening in US-EAST-1 region that are impacting some of the PUT (Upload) api calls.

2. monitoring 2026-08-26 01:09 UTC

   Our team has identified the issue and fixed it. At the moment everything is back to normal and we will continue to monitor before we mark this event as resolved.

3. resolved 2026-08-26 02:37 UTC

   The issue has been resolved. Earlier today, some customers in our US-EAST-1 region may have experienced elevated latency or errors on storage PUT requests due to an internal infrastructure issue on our backend. Our team identified the cause and applied a fix. Service has been...

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

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

1. resolved 2026-08-04 07:30 UTC

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

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

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-07-15 19:00 UTC

   Between 2026-07-15 19:24 UTC and 20:26 UTC, a subset of customers experienced issues accessing the Wasabi Management Console when their requests were geo-routed through the Singapore console endpoint. Some affected customers also reported difficulty accessing bucket information...

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

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

1. resolved 2026-07-04 17:45 UTC

   On 4 July 2026, from 16:09 UTC to 17:37 UTC, customers experienced network error messages when accessing the Wasabi Management Console. Wasabi’s Operations team identified the issue and took action to restore service stability by rerouting traffic load. Wasabi Management Console...

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

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2026-06-29 00:15 UTC

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

2. postmortem 2026-07-02 01:37 UTC

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

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

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

1. resolved 2026-06-25 01:15 UTC

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

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

Affected: US-Central-1 (Texas), EU-Central-1 (Amsterdam), EU-Central-2 (Frankfurt), EU-West-1 (London), Wasabi Management Console

Failure mode: A code release introduced the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-27 06:39 UTC

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

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

   We are continuing to investigate this issue.

3. monitoring 2026-05-27 10:46 UTC

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

4. monitoring 2026-05-27 13:38 UTC

   We are continuing to monitor for any further issues.

5. resolved 2026-05-27 13:39 UTC

   This incident has been resolved.

6. postmortem 2026-06-03 13:31 UTC

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

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

Affected: AP-Northeast-1 (Tokyo)

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

1. investigating 2026-05-21 01:37 UTC

   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. monitoring 2026-05-21 02:03 UTC

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

3. resolved 2026-05-21 03:24 UTC

   Incident resolved.

4. postmortem 2026-05-28 00:56 UTC

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

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

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

1. resolved 2026-05-08 10:00 UTC

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

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

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

Names an upstream provider: AWS.

1. resolved 2026-04-25 07:30 UTC

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

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

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

1. resolved 2026-03-24 19:30 UTC

   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 support@wasabi.com.

2. postmortem 2026-04-27 23:38 UTC

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

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

Affected: US-West-1 (Oregon)

Failure mode: Hardware, power, cooling or another physical failure. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-02-06 08:45 UTC

   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. identified 2026-02-06 10:12 UTC

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

3. monitoring 2026-02-06 11:31 UTC

   All services are operational and are currently under monitoring.

4. resolved 2026-02-06 12:28 UTC

   This incident has been resolved.

5. postmortem 2026-02-23 14:23 UTC

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

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

Affected: Wasabi Management Console

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

1. investigating 2025-11-20 02:35 UTC

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

2. investigating 2025-11-20 02:42 UTC

   We are continuing to investigate this issue.

3. monitoring 2025-11-20 03:07 UTC

   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. resolved 2025-11-20 04:06 UTC

   Management Console Access is restored to Operational Status

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

Affected: Wasabi Custom Cloud Console

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

1. investigating 2025-10-23 14:13 UTC

   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. identified 2025-10-23 14:17 UTC

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

3. monitoring 2025-10-23 14:21 UTC

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

4. resolved 2025-10-23 15:00 UTC

   The login issue with Custom Cloud Console has been resolved.

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

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

1. resolved 2025-09-19 11:00 UTC

   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 support@wasabi.com.

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

Affected: Wasabi Account Control Manager Console

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-08-18 16:12 UTC

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

2. monitoring 2025-08-18 20:08 UTC

   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. monitoring 2025-08-19 12:31 UTC

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

4. monitoring 2025-08-19 12:37 UTC

   We are continuing to monitor for any further issues.

5. monitoring 2025-08-19 12:39 UTC

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

6. resolved 2025-08-20 15:52 UTC

   The WACM Utilization Data updates issue has been resolved. Please contact support@wasabi.com if you continue to see any problem related to this incident.

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

Affected: EU-West-3 (London)

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-07-25 19:31 UTC

   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. identified 2025-07-25 20:21 UTC

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

3. monitoring 2025-07-25 21:26 UTC

   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. resolved 2025-07-25 22:32 UTC

   This incident has been resolved.

5. postmortem 2025-08-27 14:55 UTC

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

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

Affected: EU-Central-1 (Amsterdam)

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

1. investigating 2025-07-16 08:47 UTC

   We are currently experiencing system errors in our EU-CENTRAL-1 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. monitoring 2025-07-16 09:19 UTC

   We have identified and resolved the issue. All affected resources are back in service. We are currently monitoring the status. If you see any error, please reach out to support@wasabi.com for assistance.

3. resolved 2025-07-16 10:51 UTC

   This incident has been resolved.

4. postmortem 2025-07-30 12:07 UTC

   On 16 July 2025 from 07:35 UTC to approximately 9:14 UTC, Wasabi's eu-central-1 \(Amsterdam\) region began to see degraded performance for some customers as multiple internal storage services went offline, resulting in elevated HTTP 5XX error responses for GET requests to their...

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

Affected: EU-Central-2 (Frankfurt)

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

1. investigating 2025-07-08 12:28 UTC

   We are currently experiencing system errors in our EU-CENTRAL-2 (Frankfurt) 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. identified 2025-07-08 13:10 UTC

   Our Operations Team is working to restore services in the region. Customers may continue to experience HTTP 5XX error responses when interacting with their Wasabi bucket(s) at this time.

3. identified 2025-07-08 14:26 UTC

   We are continuing to work on restoring service in the region. Some customers may continue to experience HTTP 5XX error responses when interacting with their Wasabi bucket(s) at this time.

4. monitoring 2025-07-08 17:10 UTC

   Our EU-CENTRAL-2 region is now fully operational, and we will continue to monitor the service. For any questions or concerns, please reach out to our Support Team at support@wasabi.com

5. resolved 2025-07-08 18:50 UTC

   This incident has been resolved.

6. postmortem 2025-07-15 10:31 UTC

   On 08 July 2025 from 12:10 UTC to approximately 16:36 UTC, Wasabi S3 services in our Frankfurt \(eu-central-2\) region were unavailable due to a partial power issue in our datacenter. Wasabi’s Operations Team was alerted by our automated alert system that multiple racks were...

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

Affected: US-East-1 (N. Virginia), US-East-2 (N. Virginia)

Failure mode: Hardware, power, cooling or another physical failure. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2025-06-26 18:01 UTC

   We are currently investigating system errors in our US-EAST-1 and US-EAST-2 regions. 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. monitoring 2025-06-26 19:24 UTC

   We have identified and resolved the issue. All affected resources are back in service. We are currently monitoring the status. If you see any error, please reach out to support@wasabi.com for assistance.

3. resolved 2025-06-26 20:14 UTC

   This incident has been resolved. Please reach out to support@wasabi.com for any further assistance.

4. postmortem 2025-07-03 13:13 UTC

   On 26 June 2025 from 18:30 UTC to 19:12 UTC, we experienced system errors in our us-east-1 and us-east-2 regions due to an unplanned data center thermal event. Starting at 18:30 UTC, our Operations team was notified of a spike in thermal temperature within several servers within...

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

Affected: AP-Southeast-2 (Sydney)

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2025-06-18 23:45 UTC

   Our Team had identified issues with network connectivity for AP-Southeast-2 (Sydney) for a few minutes ago (9:10 .. 09:30 am approximately) and it is already mitigated. We will keep updating once we have more information.

2. monitoring 2025-06-19 00:44 UTC

   We continue to monitor AP-Southeast-2 (Sydney) access and it is stable, no further issues.

3. resolved 2025-06-19 03:28 UTC

   The networking access to Sydney region continue normal and we are resolving this incident.

4. postmortem 2025-06-25 14:03 UTC

   On 18 June 2025 at 23:10 UTC, Wasabi’s Sydney vault was impacted by Network issue at one of our network provider for 20 minutes, causing client requests to result in timeout when trying to reach to Wasabi endpoint in Sydney...

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

Affected: Wasabi Account Control API, Wasabi Account Control Manager Console

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

1. investigating 2025-05-29 03:03 UTC

   We are currently investigating System errors when users try to use WACM/Wasabi Account Control API to create subaccounts resulting in Internal Error result.

2. investigating 2025-05-29 03:13 UTC

   We are continuing to investigate this issue.

3. identified 2025-05-29 03:31 UTC

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

4. monitoring 2025-05-29 03:48 UTC

   We identified the cause and fixed the issue. The WACM and WAC API are back to normal and no errors should occur now. We will continue monitoring the System status.

5. resolved 2025-05-29 04:38 UTC

   The WACM/WAC API service is back to normal and we are marking the event as resolved. Once the analysis is completed by our internal team, we will update the status page with the Post Mortem information.

6. postmortem 2025-06-02 14:12 UTC

   On 28 May 2025 at 19:00 UTC, our Engineering and Operations Teams began investigating subaccount creation failures occurring within our WACM/WAC API services. These failures resulted in an HTTP 5XX response error when clients requested the creation of a subaccount utilizing the...

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

Affected: US-East-2 (N. Virginia)

Failure mode: Traffic surge or denial-of-service attack. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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

   We are currently experiencing system errors in our US-EAST-2 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. identified 2025-05-24 12:46 UTC

   The issue has been identified, and we are making appropriate changes to the system.

3. monitoring 2025-05-24 13:10 UTC

   We have made changes, traffic is operating normally, and we are monitoring the systems.

4. resolved 2025-05-24 16:29 UTC

   This incident has been resolved. Please contact support@wasabi.com if you continue to see errors related to this incident.

5. postmortem 2025-06-03 03:44 UTC

   On 23 May 2025 at 23:00 UTC, Wasabi’s us-east-2 \(Manassas\) vault began seeing a large increase in S3 API traffic, causing regional resources to become strained with excessive internal connections. This excessive, sustained increase in traffic to the region was outside of...

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

Affected: AP-Northeast-1 (Tokyo)

Failure mode: Hardware, power, cooling or another physical failure. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-05-21 09:47 UTC

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

2. identified 2025-05-21 10:42 UTC

   The issue has been identified and we are working towards to a solution.

3. monitoring 2025-05-21 11:13 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2025-05-21 13:07 UTC

   This incident has been resolved, please contact support@wasabi.com with any outstanding questions.

5. postmortem 2025-05-30 13:21 UTC

   On 21 May 2025 at 02:45 UTC, Wasabi’s Tokyo vault was impacted by system errors, causing client requests to result in 5xx errors for any API calls to their S3 buckets. This issue was due to an internal failure in the Tokyo Region where the backend server had a hardware fault,...

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

Affected: Wasabi.com

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

1. investigating 2025-05-14 16:47 UTC

   The Try Free Sign-up form on wasabi.com is currently returning Server Error responses upon submission. We are investigating this issue and will update the page here when we have more information.

2. monitoring 2025-05-14 17:31 UTC

   We have identified the issue with the sign-up form submission, and have rolled back changes to restore functionality. This issue should be resolved for all users now, please reach out to support@wasabi.com with any remaining questions.

3. resolved 2025-05-14 19:04 UTC

   This issue has been resolved.

4. postmortem 2025-05-14 21:31 UTC

   From approximately 13:45 to 17:15 UTC, customers using the Free Trial Form Sign Up on Wasabi.com may have been met with a “Server Error” when submitting their request. Due to an error within one of our website modules, a portion of the service was impacted, which prevented the...

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

Affected: US-Central-1 (Texas), US-East-1 (N. Virginia), US-East-2 (N. Virginia), US-West-1 (Oregon), CA-Central-1 (Toronto), EU-Central-1 (Amsterdam), EU-Central-2 (Frankfurt), EU-West-1 (London), EU-West-2 (Paris), EU-West-3 (London), EU-South-1 (Milan), AP-Northeast-1 (Tokyo), AP-Northeast-2 (Osaka), AP-Southeast-1 (Singapore), AP-Southeast-2 (Sydney), Wasabi Account Control API, Wasabi Account Control Manager Console, Wasabi Management Console, Wasabi.com

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

1. investigating 2025-05-07 13:09 UTC

   We are investigating Storage Quota Exceeded error messages for RCS accounts, our teams are working to resolve this issue.

2. identified 2025-05-07 13:34 UTC

   We have isolated this issue and are working to ensure all impacted accounts are adjusted appropriately.

3. monitoring 2025-05-07 15:31 UTC

   A fix has been implemented and we expect that there will be no more new instances of this issue for any Wasabi accounts. If you continue to experience any issues with your Wasabi account, please reach out to our Support Team at support@wasabi.com NOTE: This entry updated to...

4. resolved 2025-05-08 01:32 UTC

   The issue affecting some RCS and PayGo accounts with an incorrect 'StorageQuotaExceeded' error message has been resolved. Please reach out to support@wasabi.com if you require further assistance. NOTE: This entry has been updated to reflect that the incident affected not only...

5. postmortem 2025-05-09 21:36 UTC

   From 2025-05-07 03:00 UTC to 2025-05-07 16:00 UTC, a subset of customers experienced data upload issues due to an incorrect storage quota exceeded flag applied to their subaccounts. Specifically, some subaccounts configured with no quota value on their account were incorrectly...

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

Failure mode: Network, DNS, routing or connectivity failure. Root cause: Network or DNS. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2025-04-08 20:00 UTC

   On 08 April 2025 from 20:05 UTC to approximately 20:16 UTC, Wasabi services in our London (eu-west-3) region was unavailable due to an internal routing issue which impacted the region's ability to process incoming customer requests. At 20:05 UTC, our Operations Team was notified...

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

Affected: AP-Northeast-2 (Osaka)

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

1. investigating 2025-04-08 14:41 UTC

   We are currently investigating system errors in our AP-NORTHEAST-2 region. Our team is working to isolate the issue and provide a resolution.

2. monitoring 2025-04-08 14:45 UTC

   We have identified and resolved the issue. All affected resources are back in service. We are currently monitoring the status. If you see any error, please reach out to support@wasabi.com for assistance.

3. resolved 2025-04-08 15:23 UTC

   This incident has been resolved.

4. postmortem 2025-04-11 15:05 UTC

   On 08 April 2025 from 14:13 UTC to approximately 14:39 UTC, Wasabi services in our Osaka \(ap-northeast-2\) region was unavailable due to an internal routing issue which impacted the region's ability to process incoming customer requests. At 14:13 UTC, our Operations Team was...

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

Affected: EU-Central-1 (Amsterdam)

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

1. investigating 2025-04-04 10:01 UTC

   We are currently investigating system errors in our EU-CENTRAL-1 region. Our team is working to isolate the issue and provide a resolution.

2. investigating 2025-04-04 10:05 UTC

   We are continuing to investigate this issue.

3. monitoring 2025-04-04 12:34 UTC

   We have identified and resolved the issue. All affected resources are back in service. We are currently monitoring the status. If you see any error, please reach out to support@wasabi.com for assistance.

4. resolved 2025-04-04 13:59 UTC

   This incident has been resolved.

5. postmortem 2025-04-21 15:01 UTC

   On 04 April 2025 from 06:20 UTC to 12:20 UTC, we experienced system errors in our eu-central-1 \(Amsterdam\) region. This issue affected the S3 service and impacted customer’s ability to read and write to/from their Wasabi buckets within the region. Starting at 05:11 UTC, our...

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

Affected: US-Central-1 (Texas), US-East-1 (N. Virginia), US-East-2 (N. Virginia), US-West-1 (Oregon), EU-Central-1 (Amsterdam), EU-Central-2 (Frankfurt), EU-West-2 (Paris), AP-Northeast-1 (Tokyo), AP-Northeast-2 (Osaka), Wasabi Management Console

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. resolved 2025-03-27 22:09 UTC

   Between 10:09PM to 10:14PM UTC, we experienced errors with connecting to the Wasabi Web Console, STS, and IAM services. It was a temporary issue, auto-resolved and Operations Team validated it. There is no longer any further impact, and all services are now running without issue.

2. postmortem 2025-04-03 21:10 UTC

   On 27 March 2025 from 10:09 UTC to approximately 10:14 UTC, Wasabi services in our Ashburn \(us-east-1\), Manassas \(us-east-2\), Hillsboro \(us-west-1\), Plano \(us-central-1\), Amsterdam \(eu-central-1\), Tokyo \(ap-northeast-1\), Osaka \(ap-northeast-2\), London...

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

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. resolved 2025-03-17 14:30 UTC

   Between 10:40 to 10:50 UTC, we experienced errors with connecting to the Wasabi Web Console, STS, and IAM services. Our Operations Team has taken corrective action and there is no longer any further impact, and all services are now running without issue.

2. postmortem 2025-03-31 04:02 UTC

   On 17 March 2025 from 10:34 UTC to approximately 10:50 UTC, Wasabi services in our Ashburn \(us-east-1\), Manassas \(us-east-2\), Hillsboro \(us-west-1\), Plano \(us-central-1\), Amsterdam \(eu-central-1\), Tokyo \(ap-northeast-1\), Osaka \(ap-northeast-2\), London...

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

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

1. resolved 2025-02-19 09:00 UTC

   From 09:00 to 11:00 UTC on 19 February 2025, visitors experienced HTTP 5XX errors when attempting to view our Wasabi.com website. These errors were caused by an update to the site, which resulted in multiple modules not loading properly. Once the issue was identified, the...

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

Affected: Wasabi Account Control Manager Console

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

1. investigating 2025-02-05 05:35 UTC

   We are currently investigating an issue to access the Wasabi Account Control Manager Console page. Our customers might experience 404 and 502 errors when accessing the Wasabi Account Control Manager Console.

2. identified 2025-02-05 06:07 UTC

   Our teams had identified the issue and are working on the fix.

3. monitoring 2025-02-05 06:09 UTC

   The action to fix for the issue (errors 404 and 502) to access the Wasabi Account Control Manager Console was completed and the service has returned to normal. We are currently monitoring it.

4. resolved 2025-02-05 06:55 UTC

   This incident has been resolved.

5. postmortem 2025-02-10 22:37 UTC

   On 05 February 2025 from 05:06 AM UTC to approximately 06:04 AM UTC, Wasabi Account Control Manager Console \(WACM\) was unavailable, resulting in errors 404 or 502 when trying to access the WACM URL. The issue was caused by internal component restart with a scenario of DB lock...

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

Affected: EU-South-1 (Milan)

Failure mode: A zone, region or data center became unavailable. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-01-10 16:30 UTC

   We are currently investigating issues in our EU-SOUTH-1 (Milan) region.

2. monitoring 2025-01-10 16:51 UTC

   We have identified and corrected the issue, and our EU-SOUTH-1 (Milan) region is now back to a fully operational state. We will continue to monitor the region.

3. resolved 2025-01-10 18:03 UTC

   This incident has been resolved.

4. postmortem 2025-01-15 20:01 UTC

   On 10 January 2024 from 15:57 UTC to 16:45 UTC, we experienced an issue where clients received 4XX level errors while accessing the S3 buckets in the eu-south-1 \(Milan\) region. During an internal configuration change, a software bug caused the invalidation of TLS certificates...

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

Affected: Wasabi Account Control Manager Console

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

1. investigating 2025-01-06 06:30 UTC

   We are currently investigating issues with accessing the WACM Console. Users may experience HTTP 404 or 502 error responses.

2. resolved 2025-01-06 08:00 UTC

   This incident has been resolved.

3. postmortem 2025-01-08 21:31 UTC

   On 06 January 2025 from 05:54 UTC to 08:02 UTC, Wasabi Account Control Manager Console \(WACM\) was unavailable, resulting in HTTP 4XX or 5XX errors when trying to access the WACM URL. The issue was caused by a failure in restarting internal services responsible for maintaining...

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

Affected: Wasabi Account Control API, Wasabi Account Control Manager Console

Failure mode: A schema or data migration caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2024-12-24 20:43 UTC

   As a result of a recent database update, Wasabi’s Invoice generation was paused and reactivated on December 23, 2024. The system is being managed and monitored to ensure that the data continues to be properly reported through the remainder of the month (and thus the year-end)....

2. resolved 2025-01-03 14:20 UTC

   All systems have been performing as expected throughout the Holiday period and have shown no issues. Returning the system to normal operational status.

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

Affected: US-East-1 (N. Virginia), US-East-2 (N. Virginia)

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

Names an upstream provider: AWS.

1. investigating 2024-12-07 16:14 UTC

   We are currently investigating an increase in 500 level HTTP responses on customer traffic to the us-east-1 and us-east-2 regions.

2. investigating 2024-12-07 17:14 UTC

   We are continuing to investigate the system errors in the us-east-1 and us-east-2 regions. We will update this page as we have more information.

3. identified 2024-12-07 18:25 UTC

   We have identified a power issue at the data center which is in the process of being restored. We will update this page as we have more information.

4. identified 2024-12-07 19:24 UTC

   We are continuing the process of restoring power and bringing systems back up. We will update this page as we have more information.

5. identified 2024-12-07 19:59 UTC

   Power has been fully restored to the us-east-2 region. We are continuing the process of restoration to the us-east-1 region and will update this page as we have more information.

6. identified 2024-12-07 21:29 UTC

   Power has been fully restored to the us-east-1 region and we are continuing to work on bringing all systems back online. We will update this page as we have more information.

7. monitoring 2024-12-07 22:17 UTC

   All systems are now back online and fully operational. We are continuing to monitor the regions and will update this page as we have more information.

8. resolved 2024-12-08 00:28 UTC

   Services in both regions have been restored. Please reach out to support@wasabi.com if you see any issues related to this incident.

9. postmortem 2024-12-16 16:47 UTC

   On 7 December 2024 from 15:22 UTC to 21:30 UTC, Wasabi experienced a loss of power event in our US-EAST-1 and US-EAST-2 data centers. At 15:22, our Operations Team noticed that infrastructure within the US-EAST-1 and US-EAST-2 regions failed to respond to standard smoke tests...

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

Affected: US-East-1 (N. Virginia), US-East-2 (N. Virginia), EU-Central-1 (Amsterdam), EU-Central-2 (Frankfurt)

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-12-05 21:11 UTC

   We are currently investigating an increase in "Account Connection Limited" responses from the S3 system on a number of Wasabi Storage Regions. We will update this page as we have more information.

2. monitoring 2024-12-05 22:39 UTC

   We have isolated the issue "Account Connection Limited" errors and engineering has made changes to restore the service. We will update this page with any further information.

3. resolved 2024-12-05 23:49 UTC

   After monitoring, we have confirmed the issue is resolved and there is no further impact on our services.

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

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2024-12-02 19:30 UTC

   From 19:30 UTC 12/2/24 to 15:11 UTC 12/3/24 customers may have experienced elevated HTTP 5XX error responses and slow response times to buckets in our eu-central-2 (Frankfurt) region. Retries to the region were successful and the region is now fully operational.

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

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2024-12-01 23:41 UTC

   We experienced an issue that interrupted services for a brief period at 23:41 UTC on December 1, 2024. The system config was adjusted and service resumed at approximately 23:51 UTC.

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

Affected: US-Central-1 (Texas), US-East-1 (N. Virginia), US-East-2 (N. Virginia), US-West-1 (Oregon), CA-Central-1 (Toronto), EU-Central-1 (Amsterdam), EU-Central-2 (Frankfurt), EU-West-1 (London), EU-West-2 (Paris), EU-West-3 (London), EU-South-1 (Milan), AP-Northeast-1 (Tokyo), AP-Northeast-2 (Osaka), AP-Southeast-1 (Singapore), AP-Southeast-2 (Sydney), Wasabi Account Control API, Wasabi Account Control Manager Console, Wasabi Management Console

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2024-11-30 00:20 UTC

   We are currently investigating reported network errors across all regions. Access to both Console and S3 services may return errors. We will update this page as we have more information.

2. investigating 2024-11-30 03:08 UTC

   We continue to investigate the issue. Some traffic continues to receive errors.

3. monitoring 2024-11-30 03:43 UTC

   We have isolated the issue and resolution is underway. We expect all regions except us-east-1 to be successful. There is still some level of error responses being seen in Ashburn and we continue to work on that. We will continue to monitor all regions and update their status as...

4. monitoring 2024-11-30 04:45 UTC

   The system has been restored to fully operational in all regions. We will populate the Postmortem section of this incident with more complete details as soon as possible.

5. resolved 2024-11-30 04:46 UTC

   This incident has been resolved.

6. postmortem 2024-12-04 14:08 UTC

   On 30 November 2024 from 2024-11-30 00:17 UTC to approximately 2024-11-30 03:00 UTC, Wasabi experienced an issue where client connection attempts to Wasabi Cloud Storage and the Web Console were impacted across all storage regions, resulting in all API calls to be returned as...

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

Affected: EU-West-2 (Paris)

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

1. investigating 2024-11-17 00:06 UTC

   We are currently investigating degraded performance in the EU-West-2 (Paris) region

2. investigating 2024-11-17 00:48 UTC

   Our Operations team continues to work with the network traffic team to isolate the problem, we will update this page with more information soon

3. monitoring 2024-11-17 01:21 UTC

   We have identified the issue and are making changes to address the traffic. We are continuing to monitor the system as well

4. resolved 2024-11-17 02:14 UTC

   This incident is now resolved.

5. postmortem 2024-12-06 11:32 UTC

   On Sunday 17 November at approximately 00:14 UTC, an incident occurred in the eu-central-2 \(Paris\) region, resulting in elevated HTTP 5XX error responses and slow response times to buckets impacting some customers. During an upgrade to the region, an error caused the service...

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

Affected: Wasabi Management Console

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

1. investigating 2024-11-15 13:21 UTC

   We are currently investigating intermittent issues affecting Wasabi Managment Console login.

2. monitoring 2024-11-15 16:04 UTC

   We have identified and resolved the issue. The access to our Management Console is back to normal and operational again. We will continue to monitor our services.

3. resolved 2024-11-15 17:16 UTC

   This issue was resolved by 1:55PM UTC.

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

Affected: EU-Central-1 (Amsterdam)

Failure mode: Hardware, power, cooling or another physical failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2024-10-31 21:44 UTC

   We have reports of power issues in our EU-CENTRAL-1 region and some users may be experiencing errors when interfacing with their Wasabi buckets hosted there. We will update our status page with more information as it becomes available.

2. investigating 2024-10-31 22:21 UTC

   A facility power distribution issue is impacting several services in the eu-central-1 region. Direct Connect links are impacted as well as a subset of buckets. We continue to work with the facility to restore service.

3. identified 2024-10-31 23:15 UTC

   We have identified the issue and impacted resources. Team continue to work to restore service.

4. monitoring 2024-11-01 05:17 UTC

   The power distribution issue has been resolved and all affected resources are back in service. We are currently monitoring the status. If you see any error, please reach out to support@wasabi.com for assistance.

5. resolved 2024-11-01 06:49 UTC

   The incident has been resolved. Please reach out to support@wasabi.com if you see any issues related to this incident.

6. postmortem 2024-11-08 01:24 UTC

   From 2024-10-31 at 21:10 UTC to 2024-11-01 at 04:00 UTC, we experienced issues with a subset of customer Buckets that were unavailable due to an unexpected power distribution issue while a planned power maintenance window was in progress at the EU-Central-1 region. The...

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

Affected: Wasabi Account Control Manager Console

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

1. investigating 2024-10-30 20:14 UTC

   We are currently investigating this issue and expect to have these views restored shortly.

2. investigating 2024-10-31 00:34 UTC

   While some of the views have been restored, we continue to work to resolve the issue. This page will be updated as more progress is made.

3. identified 2024-10-31 00:44 UTC

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

4. resolved 2024-10-31 09:55 UTC

   This incident has been resolved.

5. postmortem 2024-11-07 15:24 UTC

   From 2024-10-31 00:42 UTC to 2024-10-31 10:03 UTC, we experienced an issue where Control Accounts, Sub-Accounts and Invoice data in WACM was not loading properly when attempted to be viewed by the client. Upon investigation by our Engineering Team, it was found that the nodes...

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

Affected: US-West-1 (Oregon)

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2024-09-25 13:51 UTC

   We are currently investigating system errors occurring in our US-WEST-1 region.

2. investigating 2024-09-25 13:52 UTC

   We are continuing to investigate this issue.

3. identified 2024-09-25 13:56 UTC

   Our Operations Team has identified the issue and is working to correct the system errors.

4. monitoring 2024-09-25 14:04 UTC

   Our Operations Team has corrected the issue, and the US-WEST-1 region is back in an operational state. We will continue to monitor the region.

5. investigating 2024-09-25 15:20 UTC

   We are continuing to investigate this issue.

6. resolved 2024-09-25 15:22 UTC

   This incident is now resolved. Please reach out to support@wasabi.com if you continue to see any errors related to this incident.

7. postmortem 2024-09-27 18:04 UTC

   From 2024-09-25 13:49 UTC to 2024-09-25 13:54 UTC, an incident occurred in the Hillsboro region, resulting in performance degradation for customers and impacting their ability to make S3 API calls against buckets in the region. During an upgrade to the region, the Operations...

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

Affected: CA-Central-1 (Toronto)

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-09-18 18:09 UTC

   We are currently experiencing system errors in our CA-CENTRAL-1 region.

2. monitoring 2024-09-18 18:17 UTC

   Our Operations Team identified and corrected the cause of the system errors. Performance to the region is restored and we will continue to monitor the region.

3. resolved 2024-09-18 18:50 UTC

   This incident is now resolved. Please reach out to support@wasabi.com if you continue to see any errors related to this incident.

4. postmortem 2024-09-27 18:03 UTC

   From 2024-09-18 17:55 UTC to 2024-09-18 18:08 UTC, we experienced an issue where client connection attempts to Wasabi Cloud Storage were impacted during an upgrade to our services in the CA-CENTRAL-1 region. The activity had no expectations to create any service impact and began...

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