Historial de interrupciones de Wasabi

1. September 1, 2026 at 8:31 AM UTCinvestigating

   Actualmente estamos investigando un problema con WACM reportando 0% uso de almacenamiento para subcuentas en lugar del valor real

2. September 1, 2026 at 10:36 AM UTCresolved

   Se ha resuelto la cuestión que afecta a los datos de utilización del almacenamiento de WACM. Se completó la sincronización de datos y la WACM debería presentar ahora los valores correctos. Póngase en contacto con [email protected] si continúa viendo algún problema relacionado con este incidente.

Traducido automáticamente desde la actualización oficial del incidente.

1. August 25, 2026 at 11:46 PM UTCinvestigating

   Actualmente estamos investigando temas que están ocurriendo en la región US-EAST-1 que están impactando algunas de las llamadas PUT (Upload).

2. August 26, 2026 at 1:09 AM UTCmonitoring

   Nuestro equipo ha identificado el problema y lo ha arreglado. De momento todo vuelve a la normalidad y seguiremos monitoreando antes de marcar este evento como resuelto.

3. August 26, 2026 at 2:37 AM UTCresolved

   La cuestión se ha resuelto. A principios de hoy, algunos clientes de nuestra región US-EAST-1 pueden haber experimentado una elevada latencia o errores en las solicitudes de almacenamiento PUT debido a un problema de infraestructura interna en nuestro backend. Nuestro equipo identificó la causa y aplicó una solución. El servicio ha sido totalmente restaurado. Nos disculpamos por cualquier inconveniente.

Traducido automáticamente desde la actualización oficial del incidente.

1. August 4, 2026 at 2:21 PM UTCresolved

   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. July 15, 2026 at 8:50 PM UTCresolved

   Entre 2026-07-15 19:24 UTC y 20:26 UTC, un subconjunto de clientes experimentó problemas accediendo a la Consola de Gestión de Wasabi cuando sus solicitudes fueron geo-rutadas a través de la consola de Singapur. Algunos clientes afectados también reportaron dificultad para acceder a información de cubo a través de la consola. El incidente ocurrió durante la puesta en marcha de una nueva configuración de entrega de contenidos para el endpoint de la consola de Singapur. Tras el despliegue, algunos tráficos atravesaron el nuevo camino experimentaron problemas de conectividad. Una vez que se identificó el problema, Wasabi hizo retroceder los cambios del DNS, restaurando la ruta anterior. El servicio se recuperó a medida que los cambios DNS se propagaron a nivel mundial. Tras este incidente, Wasabi está revisando el proceso de despliegue y validación de los cambios de enrutamiento de consolas regionales para mejorar las pruebas previas al despliegue, reducir el impacto de los clientes durante las futuras incursiones y fortalecer la vigilancia del tráfico regional después del despliegue.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 9, 2026 at 8:11 PM UTCresolved

   On 4 July 2026, from 16:09 UTC to 17:37 UTC, customers experienced network error messages when accessing the Wasabi Management Console. El equipo de Operaciones de Wasabi identificó el problema y tomó medidas para restaurar la estabilidad de los servicios mediante la redireccion de carga de tráfico. La funcionalidad Wasabi Management Console fue completamente restaurada por 17:37 UTC. Para cualquier pregunta, por favor contacte a [email protected].

Traducido automáticamente desde la actualización oficial del incidente.

1. June 30, 2026 at 2:54 AM 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. July 2, 2026 at 1:37 AM 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. June 29, 2026 at 3:47 AM 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. May 27, 2026 at 6:39 AM UTCinvestigating

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

2. May 27, 2026 at 9:12 AM UTCinvestigating

   We are continuing to investigate this issue.

3. May 27, 2026 at 10:46 AM UTCmonitoring

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

4. May 27, 2026 at 1:38 PM UTCmonitoring

   We are continuing to monitor for any further issues.

5. May 27, 2026 at 1:39 PM UTCresolved

   This incident has been resolved.

6. June 3, 2026 at 1:31 PM 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. May 21, 2026 at 1:37 AM 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. May 21, 2026 at 2:03 AM UTCmonitoring

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

3. May 21, 2026 at 3:24 AM UTCresolved

   Incident resolved.

4. May 28, 2026 at 12:56 AM 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. May 13, 2026 at 8:48 PM 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. April 27, 2026 at 6:06 PM 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. March 30, 2026 at 3:28 PM 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. April 27, 2026 at 11:38 PM 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. February 6, 2026 at 8:45 AM 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. February 6, 2026 at 10:12 AM UTCidentified

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

3. February 6, 2026 at 11:31 AM UTCmonitoring

   All services are operational and are currently under monitoring.

4. February 6, 2026 at 12:28 PM UTCresolved

   This incident has been resolved.

5. February 23, 2026 at 2:23 PM 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. November 20, 2025 at 2:35 AM UTCinvestigating

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

2. November 20, 2025 at 2:42 AM UTCinvestigating

   We are continuing to investigate this issue.

3. November 20, 2025 at 3:07 AM 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. November 20, 2025 at 4:06 AM UTCresolved

   Management Console Access is restored to Operational Status

1. October 23, 2025 at 2:13 PM 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. October 23, 2025 at 2:17 PM UTCidentified

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

3. October 23, 2025 at 2:21 PM UTCmonitoring

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

4. October 23, 2025 at 2:22 PM UTCresolved

   The login issue with Custom Cloud Console has been resolved.

1. September 22, 2025 at 6:16 PM 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. August 18, 2025 at 4:12 PM 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. August 18, 2025 at 8:08 PM 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. August 19, 2025 at 12:37 PM UTCmonitoring

   We are continuing to monitor for any further issues.

4. August 19, 2025 at 12:39 PM 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. August 20, 2025 at 3:52 PM 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. July 25, 2025 at 7:31 PM 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. July 25, 2025 at 8:21 PM UTCidentified

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

3. July 25, 2025 at 9:26 PM 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. July 25, 2025 at 10:32 PM UTCresolved

   This incident has been resolved.

5. August 27, 2025 at 2:55 PM 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. July 16, 2025 at 8:47 AM 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. July 16, 2025 at 9:19 AM 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. July 16, 2025 at 10:51 AM UTCresolved

   This incident has been resolved.

4. July 30, 2025 at 12:07 PM 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. July 8, 2025 at 12:28 PM 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. July 8, 2025 at 1:10 PM 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. July 8, 2025 at 2:26 PM 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. July 8, 2025 at 5:10 PM 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. July 8, 2025 at 6:50 PM UTCresolved

   This incident has been resolved.

6. July 15, 2025 at 10:31 AM 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.