История сбоев Wasabi

1. 10 октября 2026 г. в 02:27 UTCinvestigating

   В настоящее время мы расследуем вопрос, затрагивающий регион AP-SOUTHEAST-1 (Сингапур). Из-за энергетического события на сайте услуги в регионе подвергаются воздействию, и клиенты могут испытывать ошибки или неисправные запросы.

2. 10 октября 2026 г. в 02:55 UTCmonitoring

   Наша команда определила проблему и исправила ее. На данный момент все возвращается в нормальное русло, и мы продолжим следить, прежде чем отметим это событие как решенное.

3. 10 октября 2026 г. в 04:11 UTCresolved

   Инцидент разрешен

4. 13 октября 2026 г. в 14:10 UTCpostmortem

   10 октября 2026 года, между 01:10 и 02:30 UTC, клиенты, возможно, испытали ухудшение производительности и повышенные показатели ошибок в регионе Сингапура из-за отказа блока питания в центре обработки данных. Сбой нарушил подключение к базовой инфраструктуре, снизил уровень трафика и прервал операции API. Команда центра обработки данных заменила неисправный блок и восстановила мощность примерно в 02:23 UTC. Затем наша команда работала с поставщиком центров обработки данных, чтобы вернуть пострадавшее оборудование в Интернет в 02:30 UTC, после чего услуги восстановились, а трафик вернулся к нормальному уровню. Мы наблюдали за восстановлением, чтобы подтвердить, что операции вернулись в норму. По любым вопросам обращайтесь по адресу [[email protected]] (mailto:[email protected]).

Автоматический перевод официального обновления инцидента.

1. 6 октября 2026 г. в 07:08 UTCinvestigating

   В настоящее время мы изучаем некоторые проблемы с доступом к консоли Wasabi. В качестве альтернативы попробуйте использовать URL вашего региона, например: console.us-east-1.wasabisys.com или console.us-east-2.wasabisys.com или console.us-west-1.wasabisys.com и т.д

2. 6 октября 2026 г. в 08:51 UTCresolved

   Этот инцидент был урегулирован

Автоматический перевод официального обновления инцидента.

1. 1 сентября 2026 г. в 08:31 UTCinvestigating

   В настоящее время мы расследуем проблему с WACM, сообщающим об использовании 0% для хранения субсчетов вместо фактической стоимости

2. 1 сентября 2026 г. в 10:36 UTCresolved

   Проблема, затрагивающая данные использования WACM-хранилищ, решена. Была завершена синхронизация данных, и теперь WACM должен представить правильные значения. Пожалуйста, свяжитесь с [email protected], если вы продолжаете видеть какие-либо проблемы, связанные с этим инцидентом.

Автоматический перевод официального обновления инцидента.

1. 25 августа 2026 г. в 23:46 UTCinvestigating

   В настоящее время мы расследуем проблемы, происходящие в регионе US-EAST-1, которые влияют на некоторые из вызовов PUT.

2. 26 августа 2026 г. в 01:09 UTCmonitoring

   Наша команда определила проблему и исправила ее. На данный момент все возвращается в нормальное русло, и мы продолжим следить, прежде чем отметим это событие как решенное.

3. 26 августа 2026 г. в 02:37 UTCresolved

   Вопрос решен. Ранее сегодня некоторые клиенты в нашем регионе US-EAST-1, возможно, испытали повышенную задержку или ошибки при запросах на хранение PUT из-за проблемы внутренней инфраструктуры на нашем бэкэнде. Наша команда определила причину и применила исправление. Служба полностью восстановлена. Приносим извинения за любые неудобства.

Автоматический перевод официального обновления инцидента.

1. 4 августа 2026 г. в 14:21 UTCresolved

   4 августа 2026 года с 07:36 UTC до 08:03 UTC услуги Wasabi S3 в нашем регионе Франкфурт (eu-central-2) были недоступны из-за недавнего обновления программного обеспечения для нашей интерфейсной инфраструктуры. Операционная группа Васаби была предупреждена нашими автоматизированными системами мониторинга о снижении трафика и начала расследование. Обновленная версия была отброшена, а сервисы были полностью восстановлены в регионе к 08:03 UTC.

Автоматический перевод официального обновления инцидента.

1. 15 июля 2026 г. в 20:50 UTCresolved

   Между 2026-07-15 19:24 UTC и 20:26 UTC подмножество клиентов испытывало проблемы с доступом к консоли управления Wasabi, когда их запросы были гео-маршрутизированы через конечную точку консоли Сингапура. Некоторые пострадавшие клиенты также сообщили о трудностях с доступом к информации через Консоль. Инцидент произошел во время развертывания новой конфигурации доставки контента для конечной точки консоли в Сингапуре. После развертывания часть трафика, направляемого по новому пути, столкнулась с проблемами подключения. Как только проблема была выявлена, Васаби откатил изменения DNS, восстановив предыдущую маршрутизацию. Сервис восстановился после глобального распространения изменений DNS. После этого инцидента Wasabi пересматривает процесс развертывания и валидации для региональных изменений маршрутизации консоли, чтобы улучшить тестирование перед развертыванием, уменьшить влияние клиентов во время будущих развертываний и усилить мониторинг регионального трафика после развертывания.

Автоматический перевод официального обновления инцидента.

1. 9 июля 2026 г. в 20:11 UTCresolved

   4 июля 2026 года, с 16:09 UTC до 17:37 UTC, клиенты испытывали сообщения об ошибках сети при доступе к консоли управления Wasabi. Команда Wasabi Operations определила проблему и приняла меры для восстановления стабильности обслуживания путем перенаправления нагрузки на трафик. Функционал Wasabi Management Console был полностью восстановлен к 17:37 UTC. По любым вопросам обращайтесь по адресу [email protected].

Автоматический перевод официального обновления инцидента.

1. 30 июня 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 июля 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 июня 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 мая 2026 г. в 06:39 UTCinvestigating

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

2. 27 мая 2026 г. в 09:12 UTCinvestigating

   We are continuing to investigate this issue.

3. 27 мая 2026 г. в 10:46 UTCmonitoring

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

4. 27 мая 2026 г. в 13:38 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 27 мая 2026 г. в 13:39 UTCresolved

   This incident has been resolved.

6. 3 июня 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 мая 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 мая 2026 г. в 02:03 UTCmonitoring

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

3. 21 мая 2026 г. в 03:24 UTCresolved

   Incident resolved.

4. 28 мая 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 мая 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 апреля 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 марта 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 апреля 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 февраля 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 февраля 2026 г. в 10:12 UTCidentified

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

3. 6 февраля 2026 г. в 11:31 UTCmonitoring

   All services are operational and are currently under monitoring.

4. 6 февраля 2026 г. в 12:28 UTCresolved

   This incident has been resolved.

5. 23 февраля 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 ноября 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 ноября 2025 г. в 02:42 UTCinvestigating

   We are continuing to investigate this issue.

3. 20 ноября 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 ноября 2025 г. в 04:06 UTCresolved

   Management Console Access is restored to Operational Status

1. 23 октября 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 октября 2025 г. в 14:17 UTCidentified

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

3. 23 октября 2025 г. в 14:21 UTCmonitoring

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

4. 23 октября 2025 г. в 14:22 UTCresolved

   The login issue with Custom Cloud Console has been resolved.

1. 22 сентября 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 августа 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 августа 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 августа 2025 г. в 12:37 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 19 августа 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 августа 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 июля 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 июля 2025 г. в 20:21 UTCidentified

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

3. 25 июля 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 июля 2025 г. в 22:32 UTCresolved

   This incident has been resolved.

5. 27 августа 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.