Wasabi 장애 기록

1. 2026년 10월 10일 오전 2:27 UTCinvestigating

   현재 AP-SOUTHEAST-1(싱가포르) 지역에 영향을 미치는 이슈를 조사하고 있습니다. 현장의 전력 이벤트로 인해 지역의 서비스가 영향을 받고 고객이 오류 또는 실패한 요청을 경험할 수 있습니다.

2. 2026년 10월 10일 오전 2:55 UTCmonitoring

   우리의 팀은 문제점을 확인하고 그것을 고쳤습니다. 순간 모든 것은 정상으로 돌아가고 우리는 우리가 이 사건을 해결하기 전에 감시하는 것을 계속할 것입니다.

3. 2026년 10월 10일 오전 4:11 UTCresolved

   잘못된 해결

4. 2026년 10월 13일 오후 2:10 UTCpostmortem

   10 월 10, 2026, 사이 01:10 그리고 02:30 UTC, 고객은 데이터 센터의 전력 단위 실패로 인해 싱가포르 지역의 성능과 높은 오류율을 경험할 수 있습니다. 실패는 하향 인프라에 연결, 트래픽 수준을 감소 및 API 운영 중단. 데이터 센터 팀은 실패 단위를 대체하고 약 02 : 23 UTC에서 복원 된 전력을 대체했습니다. 우리 팀은 데이터 센터 공급자와 협력하여 02:30 UTC에서 영향을받은 장비를 다시 온라인으로 가져와 정상적인 수준으로 회수 및 트래픽을 반환했습니다. 정상적인 작업을 확인하기 위해 복구를 모니터링했습니다. 질문이 있으시면 [[email protected]](mailto:[email protected])로 문의하십시오.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 10월 6일 오전 7:08 UTCinvestigating

   현재 Wasabi 콘솔에 액세스 할 수있는 일부 고객 어려움을 조사하고 있습니다. 대안으로 지역 URL을 사용하려고, 예: 콘솔.us-east-1.wasabisys.com 또는 콘솔.us-east-2.wasabisys.com 또는 카테고리 기타

2. 2026년 10월 6일 오전 8:51 UTCresolved

   이 사건은 해결되었습니다

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 9월 1일 오전 8:31 UTCinvestigating

   우리는 현재 실제 값 대신에 하위 계정에 대한 0% 저장 활용을 보고 WACM과 문제가 있습니다

2. 2026년 9월 1일 오전 10:36 UTCresolved

   WACM 저장 활용 데이터에 영향을 미치는 문제점은 해결되었습니다. Data 동기화가 완료되었고 WACM은 이제 올바른 값을 제시해야 합니다. [email protected]으로 문의하시기 바랍니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 8월 25일 오후 11:46 UTCinvestigating

   우리는 현재 PUT (Upload) api 통화의 일부에 영향을 미치는 US-EAST-1 지역에서 일어나는 문제들을 조사하고 있습니다.

2. 2026년 8월 26일 오전 1:09 UTCmonitoring

   우리의 팀은 문제점을 확인하고 그것을 고쳤습니다. 순간 모든 것은 정상으로 돌아가고 우리는 우리가 이 사건을 해결하기 전에 감시하는 것을 계속할 것입니다.

3. 2026년 8월 26일 오전 2:37 UTCresolved

   문제는 해결되었습니다. 오늘, 우리의 US-EAST-1 지역에 있는 몇몇 고객은 우리의 백엔드에 내부 인프라 문제점 때문에 저장 PUT 요구에 높은 대기권 또는 과실을 경험할지도 모릅니다. 우리의 팀은 원인을 확인하고 수정을 적용했다. 서비스는 완전히 복원되었습니다. 우리는 어떤 불편든지를 위해 apologize.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 8월 4일 오후 2:21 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. 2026년 7월 15일 오후 8:50 UTCresolved

   2026-07-15 19:24 UTC 및 20:26 UTC 사이, 고객의 하위 세트는 싱가포르 콘솔 엔드포인트를 통해 지리적으로 둘러싸인 Wasabi 관리 콘솔에 액세스하는 문제가 경험. 일부 영향을받는 고객은 콘솔을 통해 버킷 정보를 접근하는 어려움을보고했습니다. 이 사건은 싱가포르 콘솔 엔드포인트에 대한 새로운 콘텐츠 전달 구성의 롤아웃 중에 발생했습니다. 배포 후, 새로운 경로 경험있는 연결 문제를 통해 약간의 트래픽 경로. 문제가 확인되면 Wasabi는 DNS 변경 사항을 다시 압연하고 이전 여정을 복원합니다. 서비스는 전 세계적으로 DNS 변경으로 복구됩니다. 이 사건에 따라 Wasabi는 지역 콘솔 라우팅의 배포 및 검증 프로세스를 검토하여 사전 배포 테스트를 개선하고 향후 롤아웃 중에 고객 영향을 줄이고 배포 후 지역 트래픽의 모니터링을 강화합니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 9일 오후 8:11 UTCresolved

   에 4 7월 2026, 에서 16:09 UTC 에 17:37 UTC, 고객 경험 네트워크 오류 메시지 와사비 관리 콘솔에 액세스 할 때. Wasabi의 Operations 팀은 문제점을 확인하고 트래픽 부하를 rerouting하여 서비스 안정성을 복원하기 위해 조치를 취했습니다. Wasabi Management Console 기능은 17:37 UTC에 의해 완전히 복원되었습니다. 이메일: [email protected].

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 6월 30일 오전 2: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. 2026년 7월 2일 오전 1: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. 2026년 6월 29일 오전 3: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. 2026년 5월 27일 오전 6:39 UTCinvestigating

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

2. 2026년 5월 27일 오전 9:12 UTCinvestigating

   We are continuing to investigate this issue.

3. 2026년 5월 27일 오전 10:46 UTCmonitoring

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

4. 2026년 5월 27일 오후 1:38 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 2026년 5월 27일 오후 1:39 UTCresolved

   This incident has been resolved.

6. 2026년 6월 3일 오후 1: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. 2026년 5월 21일 오전 1: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. 2026년 5월 21일 오전 2:03 UTCmonitoring

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

3. 2026년 5월 21일 오전 3:24 UTCresolved

   Incident resolved.

4. 2026년 5월 28일 오전 12: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. 2026년 5월 13일 오후 8: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. 2026년 4월 27일 오후 6: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. 2026년 3월 30일 오후 3: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. 2026년 4월 27일 오후 11: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. 2026년 2월 6일 오전 8: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. 2026년 2월 6일 오전 10:12 UTCidentified

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

3. 2026년 2월 6일 오전 11:31 UTCmonitoring

   All services are operational and are currently under monitoring.

4. 2026년 2월 6일 오후 12:28 UTCresolved

   This incident has been resolved.

5. 2026년 2월 23일 오후 2: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. 2025년 11월 20일 오전 2:35 UTCinvestigating

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

2. 2025년 11월 20일 오전 2:42 UTCinvestigating

   We are continuing to investigate this issue.

3. 2025년 11월 20일 오전 3: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. 2025년 11월 20일 오전 4:06 UTCresolved

   Management Console Access is restored to Operational Status

1. 2025년 10월 23일 오후 2: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. 2025년 10월 23일 오후 2:17 UTCidentified

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

3. 2025년 10월 23일 오후 2:21 UTCmonitoring

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

4. 2025년 10월 23일 오후 2:22 UTCresolved

   The login issue with Custom Cloud Console has been resolved.

1. 2025년 9월 22일 오후 6: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. 2025년 8월 18일 오후 4: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. 2025년 8월 18일 오후 8: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. 2025년 8월 19일 오후 12:37 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 2025년 8월 19일 오후 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. 2025년 8월 20일 오후 3: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. 2025년 7월 25일 오후 7: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. 2025년 7월 25일 오후 8:21 UTCidentified

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

3. 2025년 7월 25일 오후 9: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. 2025년 7월 25일 오후 10:32 UTCresolved

   This incident has been resolved.

5. 2025년 8월 27일 오후 2: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.