Historique des pannes de Wasabi

1. 10 octobre 2026 à 02:27 UTCinvestigating

   Nous enquêtons actuellement sur un problème touchant la région AP-SOUTHEAST-1 (Singapour). En raison d'un événement de puissance sur le site, les services dans la région sont touchés et les clients peuvent faire face à des erreurs ou des demandes défaillantes.

2. 10 octobre 2026 à 02:55 UTCmonitoring

   Notre équipe a identifié le problème et l'a corrigé. Pour le moment, tout est revenu à la normale et nous continuerons à surveiller avant de marquer cet événement comme résolu.

3. 10 octobre 2026 à 04:11 UTCresolved

   Incident résolu

4. 13 octobre 2026 à 14:10 UTCpostmortem

   Le 10 octobre 2026, entre 01:10 et 02:30 UTC, les clients ont peut-être connu des performances dégradées et des taux d'erreur élevés dans la région de Singapour en raison d'une panne d'unité électrique au centre de données. Cette défaillance a perturbé la connectivité à l'infrastructure sous-jacente, réduisant le trafic et interrompant les opérations de l'API. L'équipe du centre de données a remplacé l'unité défaillante et a rétabli la puissance à environ 02:23 UTC. Notre équipe a ensuite travaillé avec le fournisseur de centre de données pour ramener l'équipement affecté en ligne à 02:30 UTC, après quoi les services se sont rétablis et le trafic est revenu à des niveaux normaux. Nous avons surveillé le rétablissement pour confirmer que les opérations étaient revenues à la normale. Pour toute question, veuillez contacter [[email protected]](mailto:[email protected]).

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 6 octobre 2026 à 07:08 UTCinvestigating

   Nous enquêtons actuellement sur la difficulté d'accès de certains clients à la console Wasabi. Comme alternative essayer d'utiliser votre URL de région, exemple: console.us-east-1.wasabisys.com ou console.us-east-2.wasabisys.com ou console.us-west-1.wasabisys.com etc

2. 6 octobre 2026 à 08:51 UTCresolved

   Cet incident a été résolu

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 1 septembre 2026 à 08:31 UTCinvestigating

   Nous enquêtons actuellement sur un problème avec WACM déclarant 0% utilisation de stockage pour les sous-comptes au lieu de la valeur réelle

2. 1 septembre 2026 à 10:36 UTCresolved

   La question touchant les données d'utilisation du stockage de la MCA a été résolue. La synchronisation des données a été achevée et WACM devrait maintenant présenter les valeurs correctes. Veuillez contacter [email protected] si vous continuez à voir tout problème lié à cet incident.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 25 août 2026 à 23:46 UTCinvestigating

   Nous enquêtons actuellement sur des problèmes qui se produisent dans la région US-EAST-1 et qui touchent certains des appels PUT (Upload) api.

2. 26 août 2026 à 01:09 UTCmonitoring

   Notre équipe a identifié le problème et l'a corrigé. Pour le moment, tout est revenu à la normale et nous continuerons à surveiller avant de marquer cet événement comme résolu.

3. 26 août 2026 à 02:37 UTCresolved

   La question a été réglée. Plus tôt aujourd'hui, certains clients de notre région US-EAST-1 ont peut-être connu une latence élevée ou des erreurs sur les demandes de PUT de stockage en raison d'un problème d'infrastructure interne sur notre moteur. Notre équipe a identifié la cause et a appliqué une solution. Le service a été entièrement restauré. Nous nous excusons pour tout désagrément.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 4 août 2026 à 14:21 UTCresolved

   Le 4 août 2026 de 07:36 UTC à 08:03 UTC, les services Wasabi S3 dans notre région de Francfort (eu-central-2) n'étaient pas disponibles en raison d'une récente mise à jour logicielle de notre infrastructure frontend. L'équipe des opérations de Wasabi a été alertée par nos systèmes automatisés de surveillance d'une baisse de notre trafic d'ingestion et a commencé à enquêter. La mise à jour a été reportée et les services ont été entièrement restaurés dans la région à 08:03 UTC.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 15 juillet 2026 à 20:50 UTCresolved

   Entre 2026-07-15 19:24 UTC et 20:26 UTC, un sous-ensemble de clients ont éprouvé des problèmes d'accès à la console de gestion de Wasabi lorsque leurs demandes ont été géocheminées par le terminal de la console de Singapour. Certains clients touchés ont également signalé des difficultés à accéder à l'information sur les seau par l'intermédiaire de la console. L'incident s'est produit lors du déploiement d'une nouvelle configuration de livraison de contenu pour le terminal de la console de Singapour. Après le déploiement, certains trafics ont transité par le nouveau chemin connu problèmes de connectivité. Une fois le problème identifié, Wasabi a repoussé les changements du DNS, rétablissant ainsi le routage précédent. Service récupéré à mesure que les changements DNS se propagent à l'échelle mondiale. À la suite de cet incident, Wasabi examine le processus de déploiement et de validation des changements d'acheminement des consoles régionales afin d'améliorer les essais préalables au déploiement, de réduire l'impact des clients lors des déploiements futurs et de renforcer la surveillance du trafic régional après le déploiement.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 9 juillet 2026 à 20:11 UTCresolved

   Le 4 juillet 2026, de 16:09 UTC à 17:37 UTC, les clients ont ressenti des messages d'erreur réseau lors de l'accès à la console de gestion Wasabi. L'équipe des opérations de Wasabi a identifié le problème et a pris des mesures pour rétablir la stabilité du service en réorientant la charge de trafic. Wasabi Management Console fonctionnalité a été entièrement restauré par 17:37 UTC. Pour toute question, veuillez contacter [email protected].

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 30 juin 2026 à 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 juillet 2026 à 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 juin 2026 à 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 mai 2026 à 06:39 UTCinvestigating

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

2. 27 mai 2026 à 09:12 UTCinvestigating

   We are continuing to investigate this issue.

3. 27 mai 2026 à 10:46 UTCmonitoring

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

4. 27 mai 2026 à 13:38 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 27 mai 2026 à 13:39 UTCresolved

   This incident has been resolved.

6. 3 juin 2026 à 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 mai 2026 à 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 mai 2026 à 02:03 UTCmonitoring

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

3. 21 mai 2026 à 03:24 UTCresolved

   Incident resolved.

4. 28 mai 2026 à 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 mai 2026 à 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 avril 2026 à 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 mars 2026 à 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 avril 2026 à 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 février 2026 à 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 février 2026 à 10:12 UTCidentified

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

3. 6 février 2026 à 11:31 UTCmonitoring

   All services are operational and are currently under monitoring.

4. 6 février 2026 à 12:28 UTCresolved

   This incident has been resolved.

5. 23 février 2026 à 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 à 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 à 02:42 UTCinvestigating

   We are continuing to investigate this issue.

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

   Management Console Access is restored to Operational Status

1. 23 octobre 2025 à 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 octobre 2025 à 14:17 UTCidentified

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

3. 23 octobre 2025 à 14:21 UTCmonitoring

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

4. 23 octobre 2025 à 14:22 UTCresolved

   The login issue with Custom Cloud Console has been resolved.

1. 22 septembre 2025 à 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 août 2025 à 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 août 2025 à 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 août 2025 à 12:37 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 19 août 2025 à 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 août 2025 à 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 juillet 2025 à 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 juillet 2025 à 20:21 UTCidentified

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

3. 25 juillet 2025 à 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 juillet 2025 à 22:32 UTCresolved

   This incident has been resolved.

5. 27 août 2025 à 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.