https://approjects-vendor-status-watch.static.hf.space/v/wasabi.htmlIncidents from Wasabi's public status page, polled daily.Wed, 16 Sep 2026 12:28:20 +0000https://stspg.io/ryz3ch101t4gwasabi:2026-09-14T00:00:00.000ZMon, 14 Sep 2026 00:00:00 +0000Scheduled maintenance is currently in progress. We will provide updates as necessary.https://stspg.io/s43vn824x4gpwasabi:2026-09-01T08:31:14.463ZTue, 01 Sep 2026 08:31:14 +0000Issue 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.https://stspg.io/x81mcwlz7w9pwasabi:2026-08-31T00:00:00.000ZMon, 31 Aug 2026 00:00:00 +0000Scheduled maintenance is currently in progress. We will provide updates as necessary.https://stspg.io/cwdf5n8gqhklwasabi:2026-08-25T23:46:01.931ZTue, 25 Aug 2026 23:46:01 +0000The 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 fully restored. We apologize for any inconvenience.https://stspg.io/m3gr3tc8h8xvwasabi:2026-08-04T07:30:00.000ZTue, 04 Aug 2026 07:30:00 +0000On 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.https://stspg.io/k1133pp377m0wasabi:2026-07-15T19:00:00.000ZWed, 15 Jul 2026 19:00:00 +0000Between 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 through the Console. The incident occurred during the rollout of a new content delivery configuration for the Singapore console endpoint. Following deployment, some traffic routed through the new path experienced connectivity issues. Once the issue was identified, Wasabi rolled back the DNS changes, restoring the previous routing. Service recovered as DNS changes propagated globally. Following this incident, Wasabi is reviewing the deployment and validation process for regional console routing changes to improve phttps://stspg.io/jsr1w71b5315wasabi:2026-07-04T17:45:12.000ZSat, 04 Jul 2026 17:45:12 +0000On 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 functionality was fully restored by 17:37 UTC.  For any questions, please reach out to support@wasabi.com.https://stspg.io/7c2x20qg35d8wasabi:2026-06-28T14:00:00.000ZSun, 28 Jun 2026 14:00:00 +0000Between 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 storahttps://stspg.io/s6k7nb5vl092wasabi:2026-06-24T15:00:00.000ZWed, 24 Jun 2026 15:00:00 +0000Between 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.https://stspg.io/gyr6p37qwv6zwasabi:2026-05-27T06:39:04.335ZWed, 27 May 2026 06:39:04 +0000Between 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 dhttps://stspg.io/mjj18y4xz4zqwasabi:2026-05-21T01:37:42.000ZThu, 21 May 2026 01:37:42 +0000Between 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 furthhttps://stspg.io/n0blwnsnc229wasabi:2026-05-08T10:00:00.000ZFri, 08 May 2026 10:00:00 +0000On 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.https://stspg.io/t2sfrg231d58wasabi:2026-04-25T07:30:00.000ZSat, 25 Apr 2026 07:30:00 +0000On 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 support@wasabi.com.https://stspg.io/tgcxvdtvr2m0wasabi:2026-03-24T19:30:00.000ZTue, 24 Mar 2026 19:30:00 +0000Between 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.https://stspg.io/dr4rxcf0b1ywwasabi:2026-02-06T08:45:03.200ZFri, 06 Feb 2026 08:45:03 +0000On 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 rehttps://stspg.io/4cng95bz5hnwwasabi:2025-11-20T02:35:44.020ZThu, 20 Nov 2025 02:35:44 +0000Management Console Access is restored to Operational Statushttps://stspg.io/bsypxjdncnsjwasabi:2025-10-23T14:13:58.000ZThu, 23 Oct 2025 14:13:58 +0000The login issue with Custom Cloud Console has been resolved.https://stspg.io/dr16yhrz8wpswasabi:2025-09-19T11:00:00.000ZFri, 19 Sep 2025 11:00:00 +0000From 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.https://stspg.io/qtl1c1jy1txswasabi:2025-08-18T16:12:37.951ZMon, 18 Aug 2025 16:12:37 +0000The WACM Utilization Data updates issue has been resolved. Please contact support@wasabi.com if you continue to see any problem related to this incident.