# Wasabi: System Errors when connecting to Wasabi services

> Wasabi status incident “System Errors when connecting to Wasabi services” on 2025-03-17: impact none (vendor’s label), -204 min, 2 update(s). Archived by Rewindex.

Canonical: https://rewindex.com/company/wasabi/incidents/j760hz4904dc
Last updated: 2025-03-31T04:02:14Z

- Impact (vendor’s label): none
- Status: postmortem
- Started: 2025-03-17 17:53 UTC · Resolved: 2025-03-17 14:30 UTC · Duration: -204 min
- Updates: 2
- [Vendor status page: https://stspg.io/frd07xym6f1d](https://stspg.io/frd07xym6f1d)
- [Company: Wasabi](https://rewindex.com/company/wasabi.md)

## Timeline of updates

- **resolved** 2025-03-17 14:30 UTC: Between 10:40 to 10:50 UTC, we experienced errors with connecting to the Wasabi Web Console, STS, and IAM services. Our Operations Team has taken corrective action and there is no longer any further impact, and all services are now running without issue.
- **postmortem** 2025-03-31 04:02 UTC: On 17 March 2025 from 10:34 UTC to approximately 10:50 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 which impacted the ability for internal services to communicate effectively within all Wasabi services. Wasabi Engineering and Operations teams were notified by our automated monitoring systems at 10:34 UTC 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 noted that automatic restarts of the services did not clear the issue, prompting manual intervention to perform a manual restart of internal service nodes, which corrected the issue and allowed for client connections to resume successfully. By 10:50 UTC, all internal services were restarted and all services returned to normal operating conditions.

## Cite this

Status incident (vendor impact label: none) posted by Wasabi, started 2025-03-17 17:53 UTC, resolved after -204 min, 2 update(s).

- Canonical URL: https://rewindex.com/company/wasabi/incidents/j760hz4904dc
- Citation: Wasabi, “System Errors when connecting to Wasabi services” (2025-03-17 17:53 UTC). Archived by Rewindex: https://rewindex.com/company/wasabi/incidents/j760hz4904dc (CC BY 4.0).
- Markdown link: `[Wasabi: System Errors when connecting to Wasabi services (2025-03-17)](https://rewindex.com/company/wasabi/incidents/j760hz4904dc)`


---
Canonical: https://rewindex.com/company/wasabi/incidents/j760hz4904dc · Markdown: https://rewindex.com/company/wasabi/incidents/j760hz4904dc.md · JSON: https://rewindex.com/api/v1/companies/wasabi/incidents/j760hz4904dc · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-04T13:44:37.806Z