Oracle Cloud Outage History

Oracle Cloud reported a regional disruption in US East (Ashburn) networking that prevented users from starting existing instances or creating new ones in the Ashburn region. The outage began on Mar 3, 2026 2:30 PM UTC and was resolved by Mar 4, 2026 9:25 AM UTC, lasting approximately 18 hours and 55 minutes. The impact was localized to the US East (Ashburn) networking component, and there was no indication of a global service outage. The provider published two status updates during the incident to communicate progress and recovery.

Oracle Cloud experienced a regional networking outage in Saudi Arabia West (Jeddah). The incident began at 8:50 AM UTC when the networking component went down, causing connectivity in the Jeddah area to be disrupted. The outage lasted about 25 minutes and was resolved by 9:15 AM UTC. The impact was localized to this region, affecting users and workloads relying on the affected networking path.

The provider issued 2 official status updates during the incident. User reports showed a notable rise around 8:15 AM UTC, consistent with regional connectivity issues. The outage did not appear to affect other Oracle Cloud regions.

Oracle Cloud experienced a regional outage affecting multiple Oracle Cloud Infrastructure regions, with users in India, Saudi Arabia, UAE, Jordan, Egypt, Ireland, Poland, Vietnam, and South Africa reporting outages or degraded performance. The incident began at 7:48 AM UTC and was resolved by 8:41 AM UTC, lasting about 53 minutes. StatusGator detected the outage at Oct 30, 2025 7:48 AM UTC, ahead of any official acknowledgement on Oracle Cloud's status page.

Oracle Cloud experienced global login issues due to authentication errors, preventing access to the cloud console and APIs for many users. Reports from multiple regions—including the United States, Singapore, India, and Australia—indicate widespread login failures.

The incident lasted about 35 minutes from the early warning at 7:03 AM UTC to resolution at 7:38 AM UTC. StatusGator detected the issue at May 19, 2025 7:03 AM UTC, ahead of any official acknowledgment. Oracle Cloud did not publish an official status update during the incident in the data provided.