LucidLink incident

Wasabi connectivity issues affecting all regions

Major Resolved View vendor source →

LucidLink experienced a major incident on November 30, 2024 affecting LucidLink (North America) and LucidLink (Latin America) and 1 more component, lasting 3h 11m. The incident has been resolved; the full update timeline is below.

Started
Nov 30, 2024, 01:38 AM UTC
Resolved
Nov 30, 2024, 04:50 AM UTC
Duration
3h 11m
Detected by Pingoru
Nov 30, 2024, 01:38 AM UTC

Affected components

LucidLink (North America)LucidLink (Latin America)LucidLink (Asia-Pacific)LucidLink (Europe)

Update timeline

  1. investigating Nov 30, 2024, 01:38 AM UTC

    Customers using Wasabi storage are experiencing connectivity issues affecting all regions.

  2. monitoring Nov 30, 2024, 04:18 AM UTC

    Update received from Wasabi status page at https://status.wasabi.com/incidents/dcb131s9f3sy Monitoring We have isolated the issue and resolution is underway. We expect all regions except us-east-1 to be successful. There is still some level of error responses being seen in Ashburn and we continue to work on that. We will continue to monitor all regions and update their status as well as that of us-east-1 as we continue to make progress. Nov 30, 2024 - 03:43 UTC Update We continue to investigate the issue. Some traffic continues to receive errors. Nov 30, 2024 - 03:08 UTC Investigating We are currently investigating reported network errors across all regions. Access to both Console and S3 services may return errors. We will update this page as we have more information. Nov 30, 2024 - 00:20 UTC This incident affects: US-Central-1 (Texas), US-East-1 (N. Virginia), US-East-2 (N. Virginia), US-West-1 (Oregon), CA-Central-1 (Toronto), EU-Central-1 (Amsterdam), EU-Central-2 (Frankfurt), EU-West-1 (London), EU-West-2 (Paris), EU-West-3 (London), EU-South-1 (Milan), AP-Northeast-1 (Tokyo), AP-Northeast-2 (Osaka), AP-Southeast-1 (Singapore), AP-Southeast-2 (Sydney), Wasabi Account Control API, Wasabi Account Control Manager Console, and Wasabi Management Console.

  3. resolved Nov 30, 2024, 04:50 AM UTC

    This incident has been resolved.