Oracle Cloud Infrastructure (OCI) suffered a disruption early today in parts of Europe, affecting identity services and triggering frustration among users—many of whom found themselves locked out of essential systems with no official acknowledgment from Oracle’s own status dashboard.
Reports began surfacing around 0700 UTC, with outage tracker Downdetector showing a spike in complaints shortly after 0800 UTC. By 0830, user-submitted alerts had peaked, with connectivity and login failures concentrated around the Germany Central (Frankfurt) region. Attempted failovers to Amsterdam’s Netherlands Northwest region also appeared ineffective, according to some users.
Oracle, despite repeated requests, did not immediately issue a public explanation or confirm the scale of the problem.
The timing adds weight to ongoing questions about the transparency and reliability of Oracle’s cloud arm. Only weeks earlier, the company reversed its public assurances, admitting a security lapse had compromised Oracle Cloud Classic—an older platform that some users still rely on. After downplaying the incident, Oracle privately contacted affected customers to confirm that an attacker had accessed legacy infrastructure and published usernames from two outdated servers.
That breach—though technically outside OCI—drew scrutiny from the U.S. Cybersecurity and Infrastructure Security Agency (CISA). In mid-April, the agency urged Oracle users to audit embedded credentials and verify that the attack hadn’t exposed any of them, issuing a formal alert to that effect.
Now, with OCI’s European footprint temporarily unstable and its public communication murky, Oracle faces renewed pressure to restore trust. For customers already wary of migrating critical infrastructure to the platform, the lack of clarity only compounds concerns.
In a sector where milliseconds matter and reputations can hinge on uptime, silence during an outage speaks volumes.
