LucidLink incident

Azure Blob Storage connectivity issues

Resolved after 9 hours 34 minutes, affecting LucidLink (North America) and LucidLink (Latin America) and 1 more, on December 31, 2024.

resolved Jan 01, 2025, 12:40 AM UTC

At 0:00 UTC time all Azure-backed filespaces started working normally as expected with this leap-year bug.

Started
Dec 31, 2024, 02:26 PM UTC
Resolved
Jan 01, 2025, 12:00 AM UTC
Duration
9h 34m
Detected by Pingoru
Dec 31, 2024, 02:26 PM UTC

Affected components

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

Update timeline

  1. investigating Dec 31, 2024, 02:26 PM UTC

    Several customers reported connectivity issues in multiple regions of Azure Blob Storage. We are in contact with Microsoft and will update upon progress.

  2. identified Dec 31, 2024, 04:43 PM UTC

    The issue has been identified as a leap year bug and our team is working on implementing a fix for a future release. In the meantime, a temporary workaround would be to set the date of the client system to one day ahead of today (1/1/2025). We expect the issue to be resolved automatically tomorrow.

  3. resolved Jan 01, 2025, 12:40 AM UTC

    At 0:00 UTC time all Azure-backed filespaces started working normally as expected with this leap-year bug.

Your product runs on more than LucidLink

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →