Cronologia delle interruzioni di Wasabi

1. 1 settembre 2026 alle ore 08:31 UTCinvestigating

   Stiamo attualmente indagando su un problema con WACM che riporta l'utilizzo dello storage 0% per i sottoconti invece del valore reale

2. 1 settembre 2026 alle ore 10:36 UTCresolved

   Il problema riguardante i dati di utilizzo dello storage WACM è stato risolto. La sincronizzazione dei dati è stata completata e WACM dovrebbe ora presentare i valori corretti. Si prega di contattare [email protected] se si continua a vedere qualsiasi problema relativo a questo incidente.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 25 agosto 2026 alle ore 23:46 UTCinvestigating

   Attualmente stiamo indagando su problemi che avvengono nella regione US-EAST-1 che stanno influenzando alcune delle chiamate PUT (Upload) api.

2. 26 agosto 2026 alle ore 01:09 UTCmonitoring

   Il nostro team ha identificato il problema e risolto. Al momento tutto è tornato alla normalità e continueremo a monitorare prima di segnare questo evento come risolto.

3. 26 agosto 2026 alle ore 02:37 UTCresolved

   Il problema è stato risolto. Ancora oggi, alcuni clienti della nostra regione US-EAST-1 possono avere sperimentato latenza elevata o errori sulle richieste di storage PUT a causa di un problema di infrastruttura interna sul nostro backend. Il nostro team ha identificato la causa e ha applicato una correzione. Il servizio è stato completamente restaurato. Ci scusiamo per qualsiasi inconveniente.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 4 agosto 2026 alle ore 14:21 UTCresolved

   Il 4 agosto 2026 dalle 07:36 UTC alle 08:03 UTC, i servizi Wasabi S3 nella nostra regione di Francoforte (eu-central-2) non sono stati disponibili a causa di un recente aggiornamento software per la nostra infrastruttura frontend. Il Team Operazioni di Wasabi è stato avvisato dai nostri sistemi di monitoraggio automatizzati per un calo del traffico di ingestione e ha iniziato a indagare. L'aggiornamento è stato rotolato indietro e i servizi sono stati completamente restaurati nella regione entro 08:03 UTC.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 15 luglio 2026 alle ore 20:50 UTCresolved

   Tra il 2026-07-15 19:24 UTC e il 20:26 UTC, un sottoinsieme di clienti sperimentato problemi di accesso alla console di gestione Wasabi quando le loro richieste sono state geo-rotolate attraverso il endpoint della console di Singapore. Alcuni clienti interessati hanno anche riferito difficoltà ad accedere alle informazioni del secchio attraverso la Console. L'incidente è avvenuto durante l'implementazione di una nuova configurazione di distribuzione dei contenuti per l'endpoint della console di Singapore. A seguito dell'implementazione, un certo traffico ha percorso i nuovi problemi di connettività del percorso. Una volta che il problema è stato identificato, Wasabi ha rirottato le modifiche DNS, ripristinando il routing precedente. Servizio recuperato come cambiamenti DNS propagati a livello globale. In seguito a questo incidente, Wasabi sta esaminando il processo di implementazione e validazione per le modifiche di routing delle console regionali per migliorare i test di pre-deployment, ridurre l'impatto del cliente durante i futuri rollout e rafforzare il monitoraggio del traffico regionale dopo l'implementazione.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 9 luglio 2026 alle ore 20:11 UTCresolved

   Il 4 luglio 2026, da 16:09 UTC a 17:37 UTC, i clienti hanno sperimentato messaggi di errore di rete quando si accede alla console di gestione Wasabi. Il team di Wasabi Operations ha identificato il problema e ha preso l'azione per ripristinare la stabilità del servizio, reindirizzando il carico del traffico. La funzionalità di Wasabi Management Console è stata completamente restaurata da 17:37 UTC. Per qualsiasi domanda, contattare [email protected].

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 30 giugno 2026 alle ore 02:54 UTCresolved

   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. 2 luglio 2026 alle ore 01:37 UTCpostmortem

   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. 29 giugno 2026 alle ore 03:47 UTCresolved

   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. 27 maggio 2026 alle ore 06:39 UTCinvestigating

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

2. 27 maggio 2026 alle ore 09:12 UTCinvestigating

   We are continuing to investigate this issue.

3. 27 maggio 2026 alle ore 10:46 UTCmonitoring

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

4. 27 maggio 2026 alle ore 13:38 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 27 maggio 2026 alle ore 13:39 UTCresolved

   This incident has been resolved.

6. 3 giugno 2026 alle ore 13:31 UTCpostmortem

   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. 21 maggio 2026 alle ore 01:37 UTCinvestigating

   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. 21 maggio 2026 alle ore 02:03 UTCmonitoring

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

3. 21 maggio 2026 alle ore 03:24 UTCresolved

   Incident resolved.

4. 28 maggio 2026 alle ore 00:56 UTCpostmortem

   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. 13 maggio 2026 alle ore 20:48 UTCresolved

   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. 27 aprile 2026 alle ore 18:06 UTCresolved

   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. 30 marzo 2026 alle ore 15:28 UTCresolved

   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. 27 aprile 2026 alle ore 23:38 UTCpostmortem

   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. 6 febbraio 2026 alle ore 08:45 UTCinvestigating

   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. 6 febbraio 2026 alle ore 10:12 UTCidentified

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

3. 6 febbraio 2026 alle ore 11:31 UTCmonitoring

   All services are operational and are currently under monitoring.

4. 6 febbraio 2026 alle ore 12:28 UTCresolved

   This incident has been resolved.

5. 23 febbraio 2026 alle ore 14:23 UTCpostmortem

   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. 20 novembre 2025 alle ore 02:35 UTCinvestigating

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

2. 20 novembre 2025 alle ore 02:42 UTCinvestigating

   We are continuing to investigate this issue.

3. 20 novembre 2025 alle ore 03:07 UTCmonitoring

   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. 20 novembre 2025 alle ore 04:06 UTCresolved

   Management Console Access is restored to Operational Status

1. 23 ottobre 2025 alle ore 14:13 UTCinvestigating

   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. 23 ottobre 2025 alle ore 14:17 UTCidentified

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

3. 23 ottobre 2025 alle ore 14:21 UTCmonitoring

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

4. 23 ottobre 2025 alle ore 14:22 UTCresolved

   The login issue with Custom Cloud Console has been resolved.

1. 22 settembre 2025 alle ore 18:16 UTCresolved

   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. 18 agosto 2025 alle ore 16:12 UTCidentified

   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. 18 agosto 2025 alle ore 20:08 UTCmonitoring

   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. 19 agosto 2025 alle ore 12:37 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 19 agosto 2025 alle ore 12:39 UTCmonitoring

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

5. 20 agosto 2025 alle ore 15:52 UTCresolved

   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. 25 luglio 2025 alle ore 19:31 UTCinvestigating

   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. 25 luglio 2025 alle ore 20:21 UTCidentified

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

3. 25 luglio 2025 alle ore 21:26 UTCmonitoring

   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. 25 luglio 2025 alle ore 22:32 UTCresolved

   This incident has been resolved.

5. 27 agosto 2025 alle ore 14:55 UTCpostmortem

   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.

1. 16 luglio 2025 alle ore 08:47 UTCinvestigating

   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. 16 luglio 2025 alle ore 09:19 UTCmonitoring

   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 [email protected] for assistance.

3. 16 luglio 2025 alle ore 10:51 UTCresolved

   This incident has been resolved.

4. 30 luglio 2025 alle ore 12:07 UTCpostmortem

   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 bucket\(s\). The cause for this degradation was an internal service restart, which failed to initialize all dependent services during the restart process. Due to this internal service failure, the internal connection to some storage subsystems was lost. Wasabi's Operations team was able to restart the failed initialization on all impacted servers to restore the S3 service to a fully operational state. By 9:14 UTC, all services in the eu-central-1 region were running properly.

1. 8 luglio 2025 alle ore 12:28 UTCinvestigating

   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. 8 luglio 2025 alle ore 13:10 UTCidentified

   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. 8 luglio 2025 alle ore 14:26 UTCidentified

   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. 8 luglio 2025 alle ore 17:10 UTCmonitoring

   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 [email protected]

5. 8 luglio 2025 alle ore 18:50 UTCresolved

   This incident has been resolved.

6. 15 luglio 2025 alle ore 10:31 UTCpostmortem

   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 experiencing power issues, however not all racks within the datacenter were impacted due to the power issue not impacting all circuits within the building. While our Operations Team was working to bring up all server hardware and running system checks and diagnostics, a second power issue at 16:18 UTC caused all impacted racks to go offline a second time. By 16:36 UTC, our Operations Team was able to successfully bring up all impacted racks to a fully operational state.