Optimism Outage History

Optimism is up right now

Pingoru has recorded 24 incidents for Optimism: 4 in the last 12 months and 0 in the last 90 days.

Source: status.optimism.io

24incidents recorded
4last 12 months
0last 90 days
102 minutestypical duration
Incidents per month
012AprMayJunJulAugSepOctNov0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOctNov0%
Pingoru began tracking Optimism in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202600 of 720 (0%)
May 202600 of 744 (0%)
June 202600 of 720 (0%)
July 202612 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 744 (0%)
November 202600 of 99 (0%)

Incidents, newest first

Major July 7, 2026 Blocks produced not being distributed to the network 1h 32m Mainnet (Transaction Sequencing)

Started Jul 07, 2026, 06:03 PM UTC· resolved Jul 07, 2026, 07:35 PM UTC

  1. investigating Jul 07, 2026, 06:03 PM UTC

    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..

  2. monitoring Jul 07, 2026, 06:23 PM UTC

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

  3. investigating Jul 07, 2026, 06:38 PM UTC

    We are currently investigating this incident. The sequencer is producing blocks but some nodes participating in the network are not syncing.

  4. monitoring Jul 07, 2026, 06:47 PM UTC

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

  5. resolved Jul 07, 2026, 07:35 PM UTC

    This incident has been resolved..

  6. resolved Jul 07, 2026, 07:35 PM UTC

    This incident has been resolved.

  7. monitoring Jul 07, 2026, 07:35 PM UTC

    # **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..

Read the full incident report →

Minor March 4, 2026 Flashblocks 1h 1m Overall

Started Mar 04, 2026, 11:54 PM UTC· resolved Mar 05, 2026, 12:55 AM UTC

  1. investigating Mar 04, 2026, 11:54 PM UTC

    Due to an investigation of network bottlenecks the Flashblocks streaming websocket endpoints are temporarily unavailable..

  2. resolved Mar 05, 2026, 12:55 AM UTC

    This incident has been resolved..

Read the full incident report →

Minor March 4, 2026 OP Mainnet slow block building and intermittent chain stalls 10m Overall

Started Mar 04, 2026, 11:04 PM UTC· resolved Mar 04, 2026, 11:14 PM UTC

  1. investigating Mar 04, 2026, 11:04 PM UTC

    OP Mainnet has been observed to have various issues within its internal components causing delayed block building and sporadic chain stalls. We're investigating the incident..

  2. identified Mar 04, 2026, 11:07 PM UTC

    The incident's root cause has been identified to be the problems with the networking infrastructure backing the communication between various critical block building components. We are continuing to work on a fix for this incident..

  3. monitoring Mar 04, 2026, 11:10 PM UTC

    We implemented a fix and are currently monitoring the result..

  4. resolved Mar 04, 2026, 11:14 PM UTC

    This incident has been resolved, signified by the restored stable chain progression..

Read the full incident report →

Major November 19, 2025 op-sepolia: Flashblocks outage 4h 2m Overall

Started Nov 19, 2025, 05:34 PM UTC· resolved Nov 19, 2025, 09:36 PM UTC

  1. investigating Nov 19, 2025, 05:34 PM UTC

    Following the activation of the Jovian hardfork, we detected some problems with op-rbuilder and are investigating the root cause..

  2. investigating Nov 19, 2025, 05:45 PM UTC

    To clarify, regular (non-flashblocks) usage is unaffected. Unsafe and safe head progression and the rest of the system are fully operational. .

  3. identified Nov 19, 2025, 07:13 PM UTC

    The problem has been diagnosed and a fix is being worked on by the flashbots team. .

  4. monitoring Nov 19, 2025, 09:30 PM UTC

    A fix has been applied and we are monitoring for stability..

  5. resolved Nov 19, 2025, 09:36 PM UTC

    This incident has been resolved, flashblocks are now operational again..

Read the full incident report →

Major August 19, 2025 Mainnet Public Endpoint Outage 21m

Started Aug 19, 2025, 05:43 PM UTC· resolved Aug 19, 2025, 06:05 PM UTC

  1. monitoring Aug 19, 2025, 05:43 PM UTC

    We experienced an outage of our mainnet public endpoint during routine cluster upgrade. We implemented a fix and are currently monitoring the result..

  2. resolved Aug 19, 2025, 06:05 PM UTC

    This incident has been resolved..

Read the full incident report →

Minor May 14, 2025 [TESTING] Pause on Mainnet Incident Response DRILL –

Started May 14, 2025, 02:52 PM UTC· resolved May 14, 2025, 02:52 PM UTC

  1. resolved May 14, 2025, 02:52 PM UTC

    This is a test and not a real security incident. This is dedicated for testing our Incident Response Process in case of an emergency.

  2. resolved May 14, 2025, 03:08 PM UTC

    Resolved DRILL TEST. .

Read the full incident report →

Minor April 14, 2025 [TESTING] Pause on Sepolia Incident Response DRILL 16m

Started Apr 14, 2025, 03:47 PM UTC· resolved Apr 14, 2025, 04:03 PM UTC

  1. investigating Apr 14, 2025, 03:47 PM UTC

    This is test for testing our process for incident response this is a DRILL. .

  2. resolved Apr 14, 2025, 04:03 PM UTC

    This incident has been resolved..

Read the full incident report →

Minor March 5, 2025 All Sepolia OP-Stack chains: intermittent safe head stalls caused by L1 Sepolia Pectra deposit issue 7h 8m

Started Mar 05, 2025, 07:30 AM UTC· resolved Mar 05, 2025, 02:38 PM UTC

  1. identified Mar 05, 2025, 07:30 AM UTC

    All OP-Stack chains on Sepolia experience intermittent safe head stalls caused by an issue regarding deposits processing on L1 Sepolia. This is an ongoing situation since the Sepolia Pectra activation at 7:29 UTC and we are monitoring it while client teams work on fixing Sepolia..

  2. monitoring Mar 05, 2025, 11:16 AM UTC

    The L1 Execution-layer clients are testing and soon publishing releases that fix the identified L1 issue. Official L1 client release communications will follow. L1 Go-ethereum already has a ready release: L1 testnet node operators are strongly recommended to upgrade to these releases. The beacon-chain validators of the L1 Sepolia network are expected to deploy the fix in coordination around 2 PM UTC. After L1 node upgrades and the 2PM UTC deployment the L2 batch-submission issue is expected to resolve..

  3. monitoring Mar 05, 2025, 12:58 PM UTC

    L1 Sepolia Testnet is expected to update in 1 hour, at 2 PM UTC, to new L1 Execution-Layer Client releases. It is strongly recommended to update to these releases on Sepolia testnet. No action is needed on other L1 networks. Geth: Nethermind: Reth: Erigon: Sepolia L1 nodes that do not update are expected to fall out of sync, which may prevent batch-submission and stops L2 nodes from syncing..

  4. resolved Mar 05, 2025, 02:38 PM UTC

    L1 Sepolia testnet has been updated and is stable again. For any L1 execution-engine replicas, please update to the releases in the previous status-update, if not already updated. Batch-submission and syncing of L2 testnets should be stable now that the L1 testnet is stable again..

Read the full incident report →

Minor December 5, 2024 OP Mainnet Safe Head Stall 1h 28m

Started Dec 05, 2024, 07:32 PM UTC· resolved Dec 05, 2024, 09:00 PM UTC

  1. identified Dec 05, 2024, 07:32 PM UTC

    OP Mainnet experienced a safe head stall from \~19:30- 21:00 UTC. The incident is already resolved and the safe head has caught up..

  2. resolved Dec 05, 2024, 09:00 PM UTC

    This incident has been resolved..

Read the full incident report →