IBM Cloud Suffers 4-Hour Blackout in Amsterdam Datacenter After Fire Outage – Customers Left Without Support

IBM Cloud Outage: Amsterdam Datacenter Fire Disrupts Services

IBM Cloud customers faced significant disruptions Thursday morning after a fire at a datacenter in the Netherlands knocked an entire European facility offline. While users reported total service failures lasting at least four hours, the incident highlighted a concerning gap between real-time system failures and IBM’s official status reporting.

The Root Cause: Fire in Almere

The outage centered on the AMS3 datacenter, located near Amsterdam and a few miles from Schiphol airport. According to an IBM spokesperson, the disruption was caused by a fire at a NorthC datacenter in Almere, which serves IBM and several other clients. IBM confirmed that the facility was evacuated and no injuries were reported.

The impact was immediate, and severe. Reports from Dutch media indicated that fire brigade units from both Amsterdam and Schiphol attended the scene to combat the blaze. For IBM Cloud users, this translated into a complete loss of access to resources hosted within the AMS3 facility.

Communication Failures and the “Status Page” Gap

One of the most contentious aspects of the outage was the lack of transparency in IBM’s official communication channels. While customers reported that services were down for at least four hours, the IBM Cloud status page reportedly showed no issues during the peak of the crisis.

Independent monitoring services corroborated the user reports:

• StatusGator: Flagged the platform as “service down” based on reports from multiple users, with the final outage log recorded at 2325 UTC.
• Downdetector: Showed a surge of reports starting around 0715 UTC and continuing until approximately 1200 UTC.

Affected customers expressed frustration over the lack of support. Some reported that “Sev 1” (Severity One) tickets went unanswered for several hours, and critical information was only obtained after contacting account managers directly.

A Pattern of Instability

This incident is not an isolated event. IBM Cloud has struggled with reliability over the past year, experiencing a Severity One incident where customers were unable to access resources. Similar login failures and service disruptions were also documented in May and June of the previous year.

Changes to Technical Support

The difficulty in reporting these outages may be exacerbated by recent changes to IBM’s support structure. In September, IBM updated its Basic Support tier, removing the ability for Basic users to open or escalate technical support cases via the portal or APIs. Under the current model, Basic users are limited to self-reporting service issues through the Cloud Console.

FAQ: Understanding the AMS3 Outage

Why didn’t the IBM status page show the outage?

Users reported that the status page remained green despite the AMS3 datacenter being offline. This suggests a lag or failure in the automated monitoring systems that trigger public status updates.

What is a “Sev 1” ticket?

A Severity 1 (Sev 1) ticket is the highest priority support request, typically reserved for critical system failures that cause a complete loss of service for a business.

How does the new Basic Support tier affect users?

Since September, Basic Support users can no longer use APIs or the support portal to escalate technical cases. They must rely on self-reporting via the Cloud Console, which can slow down the resolution process during major outages.

Looking Ahead

As enterprises increasingly rely on hybrid and multi-cloud strategies, the AMS3 incident serves as a reminder of the risks associated with single-region dependency. For organizations operating in Europe, this event underscores the necessity of robust disaster recovery plans and real-time monitoring tools that operate independently of the provider’s own status dashboards.