Wasabi experienced a minor incident on January 6, 2025 affecting Wasabi Account Control Manager Console, lasting 1h 30m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jan 08, 2025, 09:30 PM UTC
We are currently investigating issues with accessing the WACM Console. Users may experience HTTP 404 or 502 error responses.
- resolved Jan 08, 2025, 09:30 PM UTC
This incident has been resolved.
- postmortem Jan 08, 2025, 09:31 PM UTC
On 06 January 2025 from 05:54 UTC to 08:02 UTC, Wasabi Account Control Manager Console \(WACM\) was unavailable, resulting in HTTP 4XX or 5XX errors when trying to access the WACM URL. The issue was caused by a failure in restarting internal services responsible for maintaining web service availability. This failure was further worsened by delays due to heavy database load, which the service relies on. Once the team identified a database lock as the cause of the slowness and the extended time required to reestablish the service, the long-running query causing the delay was terminated. The services were then restarted successfully, restoring the web service to its normal state.