On 12 July 2021 21:36 UTC, there was a service event that caused an interruption in service across all Wasabi regions. The service event was a result of the unavailability of a working host on the primary Wasabi Global Database (GDB) infrastructure. Under normal circumstances, there are multiple secondary GDB instances, but these backup resources were not available at the time. To resolve the service event, the entire GDB instance was required to be restarted, taking approximately 46 minutes to complete. The GDB instance was restored at 22:22 UTC and service was returned to operational.
Event Details
On Monday 12 July 2021 the primary GDB instance became unavailable, leading to errors on connections via S3, IAM, STS and the Wasabi Console from all regions. The Wasabi Operations team immediately moved to restore service to the primary GDB instance. Immediate attempts to restore the individual service failed and thus the GDB instance needed to be shut down and restarted. This consumed the majority of the downtime period. When the database service resumed, activity from all regions resumed and service was restored to normal.