PIVTR-D
ROracle Cloud playbook · Provider and accidental

Regional outage or service disruption

An OCI region or service fails, and workloads run degraded until Oracle recovers it or you fail over to another region. In the AWS us-east-1 event of October 19 and 20, 2025, an empty DNS record for the DynamoDB regional endpoint led to failures in dependent services, including IAM and STS authentication and EC2 launches. On OCI, an outage of the home region limits IAM changes in every region, so move traffic to a working region first and contain any parallel security incident with network rules and resource actions.

Look here

LogSearch for
OCI Status dashboardOracle's view of the outage, at https://ocistatus.oraclecloud.com/, or https://gov.ocistatus.com/ for government regions. Event reports carry a reference number and a preliminary root cause. Current state by service and region: https://ocistatus.oraclecloud.com/api/v2/components.json
Console AnnouncementsOutages specific to your tenancy. An announcement subscription sends them to a Notifications topic: oci announce announcements list -c <tenancy-ocid> --all
Home regionWhether the failed region is your home region. Users, groups, policies, compartments, dynamic groups and federation resources change only there. Check is-home-region in the output of oci iam region-subscription list
Identity domainsSign-in and administration while a domain's region is down. OCI might fail the domain over to its disaster recovery region in read-only mode. Users can sign in, and nobody can update users, groups or domain settings. Users cannot change passwords, and a user in the force password reset state has no access until the outage ends
Your own endpointsBack-end health behind each load balancer, and Health Checks monitors: oci lb backend-set-health get --load-balancer-id <ocid> --backend-set-name <name>
Log deliveryGaps in delivery by Audit, Logging and Connector Hub, which are regional. Note the window in which they delivered nothing, and export Audit for that window after recovery

Contain

#Item
1Record the start time, the affected services and the status event reference number. Rule out an attack before treating the failure as an outage
2Shift DNS to the standby region. A FAILOVER steering policy with a Health Checks monitor moves traffic when the primary answer is unhealthy. To force it, set isDisabled on the primary answer: oci dns steering-policy update --steering-policy-id <ocid> --answers file://answers.json
3Fail over an Autonomous AI Database to its cross-region standby, from the standby region: oci db autonomous-database fail-over --autonomous-database-id <standby-ocid> --peer-db-id <primary-ocid> --region <standby-region>
4Run a Full Stack Disaster Recovery failover plan in the standby disaster recovery (DR) protection group: oci disaster-recovery dr-plan-execution create-failover --plan-id <ocid> --region <standby-region>
5Log every emergency change, temporary policy, security rule and credential made during the outage, with an owner and a revert time
6Warn staff and customers that phishing uses outages as a lure, including fake status pages and fake support contacts. Publish the real status channel

Eradicate and recover

#Item
1After Oracle marks the event Resolved, fail back with a planned switchover and restore the DNS answers
2Revert every emergency change on the log. Find policies and rules created in the window with CreatePolicy, UpdatePolicy, AddNetworkSecurityGroupSecurityRules and UpdateSecurityList in Audit
3Record the data loss of each database failover. The Console banner states the Autonomous AI Database manual failover loss in minutes
4Request service credits through your account manager within 60 days of the breach of the service level agreement (SLA), with evidence of the breach
5Subscribe the tenancy to its disaster recovery region pairing and replicate identity domains there, so sign-in and IAM principal authentication survive a home region outage
6Exercise the plan with the regional outage tabletop, and follow Recover
Watch out
  • During a home region outage you cannot deactivate a user, reset a password or change a policy. Contain a parallel security incident with network rules and resource actions in the working regions.
  • IAM changes made in the home region can take several minutes to reach the other regions, so a revert takes effect after a delay as well.
  • Automatic failover does not apply to a cross-region Autonomous AI Database standby, and a manual failover can lose data.
  • An RSS subscription to the Status dashboard sends events for all services and regions. Filter them before paging anyone.

Oracle documentation: Status service, Console Announcements, subscribing to announcements, managing regions, disaster recovery and identity domains, Traffic Management overview, Autonomous Data Guard manual failover, Full Stack Disaster Recovery plan types, Audit log event contents, service level agreements; OCI CLI help for dns steering-policy update, db autonomous-database fail-over, disaster-recovery dr-plan-execution and lb backend-set-health. AWS summary of the Amazon DynamoDB service disruption in us-east-1. Checked September 2026. Rechecked October 2026: every command against OCI CLI 3.94.2.

Adapts material from Dynamic Incident Response: A Framework for Security Teams by Joshua Wright, © 2026 The Escal Institute of Advanced Technologies, Inc. d/b/a SANS Institute, licensed under CC BY 4.0. Figures reproduced under that license. Changes were made. Not published by, endorsed by, or affiliated with the SANS Institute.