System Errors to access Wasabi services

Incident Report for Wasabi Technologies

Postmortem

On 27 March 2025 from 10:09 UTC to approximately 10:14 UTC, Wasabi services in our Ashburn (us-east-1), Manassas (us-east-2), Hillsboro (us-west-1), Plano (us-central-1), Amsterdam (eu-central-1), Tokyo (ap-northeast-1), Osaka (ap-northeast-2), London (eu-west-1), and Frankfurt (eu-central-2) regions were unavailable due to an issue, impacting customer traffic and Web Console connectivity. Wasabi Engineering and Operations teams were notified by our automated monitoring systems of an issue with a spike in connection between internal service worker nodes. This spike led to the inability to open new connections within the services.

Wasabi’s Operations Team manually restarted the services, which corrected the issue and allowed for client connections to resume successfully. By 10:14 UTC, all internal services were restarted and all services returned to normal operating conditions.

Posted 3 days ago. Apr 03, 2025 - 21:11 UTC

Resolved

Between 10:09PM to 10:14PM UTC, we experienced errors with connecting to the Wasabi Web Console, STS, and IAM services. It was a temporary issue, auto-resolved and Operations Team validated it. There is no longer any further impact, and all services are now running without issue.
Posted 10 days ago. Mar 27, 2025 - 22:09 UTC
This incident affected: US-Central-1 (Texas), US-East-1 (N. Virginia), US-East-2 (N. Virginia), US-West-1 (Oregon), EU-Central-1 (Amsterdam), EU-Central-2 (Frankfurt), EU-West-2 (Paris), AP-Northeast-1 (Tokyo), AP-Northeast-2 (Osaka), and Wasabi Management Console.