# SEC Reg SCI Rule 1001(a): 2-Hour RTO & Geographic DR Guide

> Engineering compliance with SEC Regulation SCI Rule 1001(a)(2)(v): 2-hour Recovery Time Objectives, NJ-to-Chicago geographic separation, and zero shared SPOFs.

Canonical: https://terminalledgerdesk.com/reports/sec-regulation-sci-rule-1001-two-hour-rto-geographic-backup-mandate
Last updated: 2026-11-14T19:50:25.021Z

**Publication:** Terminal Ledger Desk
**Category:** Reg Sci Disaster Recovery Outage Rca
**Published:** 2026-11-13T09:25:25.915Z
**Author:** Marcus Thorne, CQF (Certificate in Quantitative Finance (CQF), Low-Latency FIX & Matching Engine Architect)
**Reviewer:** Not recorded

## Answer-first summary

After Hurricane Sandy flooded Lower Manhattan in 2012 and shuttered US equity markets for two days, SEC Reg SCI Rule 1001(a)(2)(v) mandated out-of-region backup data centers capable of resuming trading within 2 hours.

## Key takeaways

- SEC Regulation SCI Rule 1001(a)(2)(v) requires covered venues to maintain geographically diverse backup sites capable of resuming trading within <= 2 hours (and shorter for Critical SCI systems).
- Placing DR 30 km away in the same New Jersey metro fails geographic diversity due to shared power grids, weather corridors, and carrier POPs—making NJ <-> Chicago (~1,180 km) the US standard.
- Meeting a 120-minute RTO across thousands of symbols requires 100%-capacity Warm Standby bare metal with local HSMs, local auth, and pre-pinned static DR session IPs.
- Because NJ-to-Chicago WAN replication is asynchronous (~7ms one-way), regional DR playbooks publish an authoritative Last_Persisted_ExecID cutoff and reopen cleanly via Call Auction.

## Related financial entities

- **CME Aurora Financial Data Center Standard** (CME-AURORA) — product: Dedicated CME Group hosting facility in Aurora, Illinois, housing the Globex matching engine and offering direct low-latency colocation to clearing members.
- **Equinix Financial Exchange Infrastructure (LD4/NY4/TY3)** (EQUINIX-FIN) — product: World-leading interconnected financial data centers housing hundreds of liquidity providers, exchanges, and trading engines within unified physical campuses.
- **High-Availability Trading Failover Architecture** (HA-CLUSTER) — product: Clustered server configuration designed to guarantee uninterrupted execution processing even during sudden hardware failure, power loss, or network partitions.

## Analysis

When **Hurricane Sandy** struck the New York/New Jersey coastline in October 2012, storm surges flooded telecom vaults and substations, forcing US equity exchanges to close for **two consecutive days**—the longest weather closure since the Blizzard of 1888. **SEC Regulation SCI Rule 1001(a)(2)(v)** (`17 CFR 242.1001`) ensured a regional catastrophe can never again freeze US capital markets overnight: every SCI entity must maintain **geographically diverse backup and recovery capabilities** designed to achieve **next-business-day AND `<= 2-hour` intraday resumption of trading**!

## What Qualifies as "Geographically Diverse" Under SEC Release 34-73639?

Anchored in our [SEC Reg SCI & Outage Post-Mortem Hub](/reports/sec-regulation-sci-exchange-disaster-recovery-outage-postmortem-hub), the SEC intentionally declined to prescribe an arbitrary minimum mile count (e.g., "250 miles"), imposing instead a stricter **Zero Shared Regional Vulnerability Test**:
- **Why `Secaucus NY4 -> Carteret NJ -> Mahwah NJ` Fails as Primary-to-DR**: Although NY4, Carteret, and Mahwah sit `25 to 55 km` apart inside the New Jersey liquidity triangle ([Equinix Financial Infrastructure](/engines/equinix-financial-infrastructure)), all three share the **same PJM/PSE&G regional power grid, Northeast hurricane/blizzard corridor, regional telecom carrier POPs, and metropolitan workforce commuting zone**!
- **Standard US Exchange Primary-to-DR Topology**: Consequently, `NYSE (ICE)`, `Nasdaq`, `Cboe`, and `MEMX` host their Primary colocation clusters in **Northern New Jersey (`Mahwah`, `Carteret`, `Secaucus`)** and place their Regulation SCI Disaster Recovery (`DR`) matching engines **`~1,150 km` away in Chicago (`Equinix CH4 / Cermak Road` or [Aurora Illinois](/engines/cme-aurora-colocation-standard))**—while Chicago-primary derivatives venues (`CME`, `ICE`) place DR back East in the **New York / New Jersey metro**!

![120-minute SEC Regulation SCI Rule 1001(a)(2)(v) disaster recovery cutover timeline from T+0 Primary STONITH Fence to T+25 Seq Cutoff, T+60 Member Logon, and T+100 Chicago Reopen Auction](/api/figure?type=flow&title=SEC%20Reg%20SCI%20120-Minute%20Regional%20Failover%20Execution%20Timeline&subtitle=T%2B0%20Fence%20NJ%20-%3E%20T%2B25%20Publish%20Last%20Trade%20Seq%20-%3E%20T%2B60%20CH4%20Logons%20-%3E%20T%2B100%20Reopen%20Cross&steps=T%2B0..15m%20%20Fence%20NJ%3A%3ADeclare%20DR%3B%20kill%20NJ%20BGP%2Flasers%20%280%20split%29%7CT%2B15..35m%20%20Seq%20Cut%3A%3APublish%20Last_Trade_ID%3B%20purge%20Day%20CLOB%7CT%2B35..75m%20%20Member%20Up%3A%3ARule%201004%20brokers%20logon%20to%20CH4%20ports%7CT%2B75..105m%20%20Uncross%3A%3A30m%20Pre-Open%20IOP%20-%3E%20Resume%20%3C%20120m!&metrics=STATUTORY%20RTO%3A%3A%3C%3D%202%20Hours%3A%3A17%20CFR%20242.1001%28a%29%282%29%28v%29%7CPRIMARY%20%3C-%3E%20DR%3A%3A~1%2C180%20km%3A%3ANJ%20Triangle%20%3C-%3E%20Chicago%20CH4%7CSHARED%20GRID%2FPOP%3A%3A0%20Permitted%3A%3ASeparate%20power%2C%20carrier%20%26%20staff%7CHARDWARE%20STATE%3A%3AWarm%20Active%3A%3A100%25%20capacity%20pre-racked%20in%20DR)

## Anatomy of the 120-Minute (`2-Hour`) Intraday Cutover Clock

Achieving a verifiable **`<= 120-minute` RTO** across 8,000+ listed symbols and 400 clearing members under our [HA Trading Failover Architecture](/engines/ha-trading-failover-architecture) requires pre-provisioned **Warm/Hot Standby Hardware** (cold cloud provisioning or restoring tape backups cannot finish in 120 minutes!):
1. **`T + 0..15 min` (`Declaration & Primary Fence`)**: Executive Incident Commander confirms primary site unrecoverable; shoots STONITH optical/BGP fence on Primary NJ ports so split-brain dual matching is physically impossible.
2. **`T + 15..35 min` (`WAN Log Drain & Last-Seq Cutoff`)**: Chicago DR cluster drains final replicated journal frames, publishes the authoritative **`Last_Processed_Trade_ID / Timestamp`** bulletin to all members, and purges unexecuted `Day` orders.
3. **`T + 35..75 min` (`Member Session Logon & Drop-Copy Sync`)**: Designated Rule 1004 broker-dealers ([annual SIFMA/FIA DR test](/reports/annual-sifma-fia-industry-wide-disaster-recovery-failover-test-plan)) connect pre-pinned Chicago sessions (`FIX` / `OUCH` / `BOE`) and verify `35=A` sequence state.
4. **`T + 75..105 min` (`Pre-Open Order Entry & Imbalance Broadcast`)**: Continuous quotes build inside a `Pre-Open` reserve state ([graceful market-halt reopening call auctions](/reports/graceful-market-halt-reopening-call-auction-order-book-purge-states)) before uncrossing well inside the `120-minute` statutory ceiling!

| US SCI Entity Group | Primary Production Campus | Geographically Diverse DR Campus | Approx. Separation | Primary Connectivity Fabric |
| :--- | :--- | :--- | :--- | :--- |
| **NYSE Group (`ICE` Pillar)** | Mahwah, New Jersey (`NY2/Mahwah`) | **Cermak Road, Chicago, IL (`CH4`)** | `~1,150 km` | ICE Global Network (`IGN`) |
| **Nasdaq US Equities/Options** | Carteret, New Jersey (`NY11`) | **Chicago, Illinois (`Equinix CH4`)** | `~1,170 km` | Nasdaq Financial Framework |
| **Cboe Global Markets** | Secaucus, New Jersey (`Equinix NY5`) | **Chicago, Illinois (`CH4`)** | `~1,180 km` | Cboe Titanium / Extranet |
| **CME Group (`CFTC DCO/DCM`)** | Aurora, Illinois (`DC3`) | **New York / New Jersey Metro** | `~1,190 km` | CME Globex Hub / Google Cloud DR |

## US Exchange Primary vs Regulation SCI Backup Site Topology Matrix

Publicly documented primary data centers and geographically diverse Reg SCI DR facilities across major US venues.

```formula
RTO_Total = T_detect_and_decide + T_primary_stonith_fence + T_wan_log_reconcile + T_member_connectivity + T_reopen_call_auction <= 120 minutes

Asynch Replication Unreconciled Window Bound (RPO_regional_disaster):
 Delta_InFlight_Bytes <= Bandwidth_WAN_Gbps * OneWay_Propagation_Delay_Sec
 At 2.0 Gbps sustained journal stream * 0.007 sec (7 ms NJ->CHI) = ~1.75 MB (~12,000 events)
 Handled Deterministically: Venue publishes exact Last_Persisted_DR_ExecID; any NJ ack > Cutoff is officially busted/void!
```

## Eliminating Hidden Single Points of Failure (`DNS`, `HSMs`, `Auth`, `Staffing`)

SEC Office of Compliance Inspections and Examinations (`EXAMS`) auditors look past server racks to hunt **hidden logical dependencies** that still route back through New Jersey during a Chicago failover:
- **Authentication & PKI / HSMs**: If Chicago FIX gateways query an `LDAP / Kerberos / Hardware Security Module (HSM)` sitting solely in Mahwah NJ to validate member TLS certs, Chicago logon fails 100% when NJ goes dark!
- **Staffing Geographic Split (`Bus-Factor Independence`)**: Rule `1001(a)` requires operational personnel outside the primary disaster zone trained and credentialed to run the Chicago site without NJ NOC staff.
- **Pre-Established Static DR IPs**: Avoid relying on dynamic public DNS updates mid-crisis—see [BGP Anycast & DNS TTL pitfalls during DR cutovers](/reports/bgp-anycast-dns-ttl-pitfalls-during-broker-gateway-dr-ip-cutovers).

![Time consumed across DR failover phases comparing Pre-Pinned Warm Hardware (98 mins total) vs Cold Cloud Spin-Up (260 mins - Fails Reg SCI) and DNS-Dependent Cutover (175 mins)](/api/figure?type=bars&title=Total%20Cutover%20Time%20by%20DR%20Readiness%20Architecture%20%28Minutes%29&subtitle=Why%20only%20pre-racked%20Warm%2FHot%20Standby%20hardware%20clears%20the%20120-minute%20Reg%20SCI%20gate&steps=Warm%20Pre-Pinned%20CH4%20Standby%20%28Pass%29%3A%3A98%20mins%20total%20%2822m%20margin%20inside%20120m!%29%7CCritical%20SCI%20Dual-Hot%20SIP%20%28Pass%29%3A%3A14%20mins%20total%20%28CTA%2FUTP%20rapid%20cutover%29%7CPublic%20DNS%2FFirewall%20Re-Point%20%28Fail!%29%3A%3A175%20mins%20total%20%28Resolver%20cache%20stalls%29%7CCold%20Bare-Metal%20%2F%20Snapshot%20Boot%20%28Fail!%29%3A%3A260%20mins%2B%20%28Violates%20Rule%201001%28a%29!%29&metrics=DR%20CAPACITY%3A%3A100%25%20Prod%3A%3AMust%20sustain%20full%20market%20load%7CAUTH%20%2F%20HSM%3A%3ALocal%20in%20DR%3A%3AZero%20callback%20to%20dead%20NJ%20site%7CGTC%20ORDERS%3A%3AVenue%20Policy%3A%3AReplicated%20or%20canceled%20per%20spec%7CANNUAL%20PROOF%3A%3ARule%201004%3A%3ALive%20industry%20Saturday%20failover)

## Broker-Side Preparedness: Why Having Zero Chicago Presence Leaves You Blind

If Nasdaq and NYSE fail over to `Equinix CH4 Chicago` at `11:30 AM ET` and your firm only leased cross-connects in `NY4/Carteret` with **zero Chicago colocation or extranet circuits**, your latency jumps from `25 microseconds` to `14+ milliseconds`—or fails completely! Maintain pre-tested [FIX API](/software/fix-api) DR sessions in Chicago and stress 2-hour unhedged freeze risk in our [Terminal Margin VaR & ES Calculator](/calculators/terminal-margin-var-es-calculator).

## Frequently asked questions

### Does SEC Regulation SCI require zero data loss (RPO = 0) if a meteor or grid collapse destroys the entire primary state instantaneously?

No—physics forbids 0-nanosecond synchronous replication across 1,180 km without adding 14ms to every colocation order! Instead, Rule 1001 requires deterministic reconciliation: exchanges replicate state continuously within milliseconds, publish the exact final Trade/Sequence ID recovered at the DR site, and instruct members to reconcile Drop-Copy fills against that cutoff.

### Can a backup DR data center run on scaled-down 25% hardware capacity to save CapEx?

Never! Regulation SCI explicitly mandates that backup and recovery facilities possess sufficient capacity to handle full production peak volatility volumes—because the exact day a regional disaster strikes is guaranteed to generate massive institutional hedging volume!

### Why must Primary NJ optical ports and BGP routes be forcibly fenced ("STONITH") BEFORE activating Chicago DR?

If power flickers back on in New Jersey 40 minutes after Chicago DR opens without hard fencing, half of Wall Street would route orders to NJ while the other half trades in Chicago—creating two conflicting national order books ("Split-Brain") in the exact same ticker symbols!

### How often must an SCI entity review and submit its system compliance reports to Senior Management and the SEC?

Rule 1003(b) requires an objective annual SCI Review (including penetration testing at least every 3 years and annual control assessments) presented to Senior Management and the Board, then filed electronically with the SEC on Form SCI within 60 days.


## Source URLs

- https://www.ecfr.gov/current/title-17/chapter-II/part-242/section-242.1001
- https://www.sec.gov/files/rules/final/2014/34-73639.pdf
- https://www.nyse.com/markets/nyse/trading-info

## Citation

- APA: Marcus Thorne, CQF. (2026). SEC Regulation SCI Rule 1001(a): 2-Hour RTO & Geographically Diverse Backup Site Architecture. Terminal Ledger Desk. https://terminalledgerdesk.com/reports/sec-regulation-sci-rule-1001-two-hour-rto-geographic-backup-mandate
- Canonical article: [SEC Regulation SCI Rule 1001(a): 2-Hour RTO & Geographically Diverse Backup Site Architecture](https://terminalledgerdesk.com/reports/sec-regulation-sci-rule-1001-two-hour-rto-geographic-backup-mandate)
- Site research index: [Terminal Ledger Desk](https://terminalledgerdesk.com/llms-full.txt)
