Optimism - Notice history

All systems operational

100% - uptime

Public API - Operational

100% - uptime
Jun 2026 · 100.0%Jul · 100.0%Aug · 100.0%
Jun 2026
Jul 2026
Aug 2026

Deposits - Operational

100% - uptime
Jun 2026 · 100.0%Jul · 100.0%Aug · 100.0%
Jun 2026
Jul 2026
Aug 2026

Withdrawals - Operational

100% - uptime
Jun 2026 · 100.0%Jul · 100.0%Aug · 100.0%
Jun 2026
Jul 2026
Aug 2026

Transaction Sequencing - Operational

100% - uptime
Jun 2026 · 100.0%Jul · 99.99%Aug · 100.0%
Jun 2026
Jul 2026
Aug 2026

Batch Submission - Operational

100% - uptime
Jun 2026 · 100.0%Jul · 100.0%Aug · 100.0%
Jun 2026
Jul 2026
Aug 2026

Node Sync - Operational

100% - uptime
Jun 2026 · 100.0%Jul · 100.0%Aug · 100.0%
Jun 2026
Jul 2026
Aug 2026
100% - uptime

Public API - Operational

100% - uptime
Jun 2026 · 100.0%Jul · 100.0%Aug · 100.0%
Jun 2026
Jul 2026
Aug 2026

Deposits - Operational

100% - uptime
Jun 2026 · 100.0%Jul · 100.0%Aug · 100.0%
Jun 2026
Jul 2026
Aug 2026

Withdrawals - Operational

100% - uptime
Jun 2026 · 100.0%Jul · 100.0%Aug · 100.0%
Jun 2026
Jul 2026
Aug 2026

Transaction Sequencing - Operational

100% - uptime
Jun 2026 · 100.0%Jul · 100.0%Aug · 100.0%
Jun 2026
Jul 2026
Aug 2026

Batch Submission - Operational

100% - uptime
Jun 2026 · 100.0%Jul · 100.0%Aug · 100.0%
Jun 2026
Jul 2026
Aug 2026

Node Sync - Operational

100% - uptime
Jun 2026 · 100.0%Jul · 100.0%Aug · 100.0%
Jun 2026
Jul 2026
Aug 2026

Notice history

Aug 2026

No notices reported this month

Jul 2026

Blocks produced not being distributed to the network
  • Postmortem
    UTC
    Postmortem

    OP Mainnet external nodes and RPC providers stalled on a stale head (7 July 2026)

    Status: Resolved


    Impact

    External nodes and third-party RPC providers were stuck at a stale head for ~22 minutes (17:59 to 18:22 UTC). Because major providers were serving that stale head, transaction throughput was near zero for about 16 minutes of that window, and submissions routed through those providers did not land. Reads continued to be served, though against a stale state. There was no reorg, no safe-head or finality violation, and no funds were at risk.


    Root cause

    A routine infrastructure upgrade disrupted a network connection our sequencers depend on. The connection failed silently rather than erroring, which throttled block production and pushed new blocks outside the window for normal peer-to-peer propagation. External nodes recovered once the affected range was posted to L1


    Remediation

    We deployed a fix removing the dependency responsible for the slowdown and made the affected connections fail cleanly when infrastructure cycles. We're also strengthening internal alerting and node peering so issues of this kind are detected and contained faster.

  • Resolved
    UTC
    Resolved
    This incident has been resolved.
  • Monitoring
    UTC
    Monitoring

    Most infrastructure providers have recovered, we are continuing to monitor and work with infrastructure providers to resolve syncing issues.

  • Investigating
    UTC
    Investigating

    We are currently investigating this incident after a brief unsafe head stall. The sequencer is now producing blocks but some nodes participating in the network are not syncing.

Jun 2026

No notices reported this month

Jun 2026 to Aug 2026

Next