Is LucidLink down?

The issue has been identified and a fix is being implemented.

A fix has been implemented and we are monitoring the results.

A fix has been deployed and verified. We are now monitoring ongoing operations to ensure operation.

This incident has been resolved.

We are investigating intermittent connectivity issues affecting some customers hosted in the IBM us-south region. The issue appears to be network-related, and we are working with IBM to identify the cause and restore stable connectivity. We will provide further updates as more information becomes available.

We are continuing to investigate intermittent connectivity issues affecting some customers across multiple IBM Cloud regions. We are working closely with IBM Cloud to identify the root cause and restore stable connectivity. We will provide another update as soon as more information becomes available.

IBM has reviewed the network traces and confirmed that the packet loss occurred before traffic reached its network, indicating an issue with an upstream Internet service provider. Customer reports indicate that connectivity has returned to normal, and we are continuing to monitor the situation.

This incident has been resolved.

Customers with IBM filespaces are experiencing degraded performance since 8:00 AM UTC on the 7th of May, 2026. We are in contact with IBM and will update the status page upon progress.

We have identified the cause of the degraded performance for filespaces in the ams03 region. IBM has reported a fire at the data center facility serving this region. The facility has been safely evacuated with no injuries reported. IBM is currently working with emergency services to assess the impact on operations. While this is a third-party facility incident, we are monitoring the situation closely.

IBM continues to investigate the AMS03 data centre outage following the fire incident at the NorthC facility. The fire is reported to be contained, and NorthC is currently assessing damage to the underlying power infrastructure and associated repair timelines. At this time, there is still no ETA for restoration. IBM continues to recommend that customers remain on disaster recovery or failover paths where available. We are working closely with IBM and will continue coordinating directly with affected customers as additional information becomes available.

After the initial IBM walkthrough and assessment, all three server rooms are intact, with no visible smoke or water damage. - Server Room 1 remains without power due to non‑viable adjacent utility and cooling systems. - The utility and cooling systems for Server Room 2 and Server Room 3 appear to be intact; however, additional control‑plane actions are required to restore customer access. The recovery plan to restore customer access to resources in Server Room 2 and Server Room 3, while planning the migration of equipment and workloads from Server Room 1 to Server Room 3 is progressing as expected. IBM is working 24 hours a day, and we expect these actions to take several days to complete. IBM remains committed to transparent communications and will provide updates as we make progress on these actions. IBM continues to recommend that customers invoke or remain on their disaster recovery paths while assessment and potential repair actions are under review. We are working closely with IBM and will continue coordinating directly with affected customers as additional information becomes available.

IBM has provided a revised recovery estimate. As of May 10, 2026, 17:30 UTC, it is estimated that restoration of client connectivity to the ams03 region will begin in approximately 48 to 72 hours. When restoration begins, the goal is to return environments to their pre-outage state, to the extent technically possible.

As of May 12, 05:30 UTC, IBM has provided an updated estimate for the restoration of client connectivity. They anticipate initiating the reconnection process within the next 12 to 36 hours.

Connectivity to the Cloud Object Storage (COS) endpoints in the IBM ams03 region has been restored. We are currently monitoring the environment to ensure continued stability as traffic resumes. Clients may resume normal operations.

This incident has been resolved.