Issues Accessing WACM Console

What to do

• Check whether you use Wasabi Wasabi Account Control Manager Console. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 1h 30m it lasted.

  Anything that failed between 2025-01-06 06:30 UTC and 2025-01-06 08:00 UTC may need a replay.

• Subscribe to Wasabi's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=wasabi works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Wasabi 3

1. investigatingJan 6, 2025, 6:30 AM UTC

   We are currently investigating issues with accessing the WACM Console. Users may experience HTTP 404 or 502 error responses.

   provider

2. resolvedJan 6, 2025, 8:00 AM UTC

   This incident has been resolved.

   provider

3. postmortemJan 8, 2025, 9: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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.