Optimism - Notice history

Our team has resolved the chain halt, and the chain should now be fully operational for all users. If you continue to experience an issue, please let us know on Discord. Thanks for your patience with us!

Our team has identified the cause of the chain halt, and has deployed a fix.

We expect the chain to move again shortly.

We’ll continue to share updates as we have them.

Our team has identified the cause of the halt and is working on a fix.

The safe head has now resumed normal operation.

We have identified and applied a potential fix for the batcher performance issue. We will continue to monitor the situation.

L2 fees are no longer elevated, L1 blob fees are trending down.

Blob data availability fees returned to stability. Batch submission is operational and utilizing blobs again. We will continue to monitor the L1 data fees for changes.

We have performed the switch back to calldata. Users should observe a more stable safe head, as well as lower fees. We will switch back to blobs once the L1 congestion subsides.

Our team has implemented a fix to resolve the unsafe head stall on op-sepolia and is monitoring the situation.

Transactions are being included again and op-sepolia nodes should resume following the chain and seeing the unsafe head progress.

Our team has identified the cause of the unsafe head stall. The issue is the result of an outage in the L1 nodes used by the sequencer.

At this time, users will continue to see a stall in block production and transactions will not be included.

Our team has resolved the unsafe head stall, and op-mainnet should now be fully operational for all users. If you continue to experience an issue, please let us know on Discord.

Thanks for your patience with us!

Our team has implemented a fix to resolve the unsafe head stall, and is monitoring the situation.

We'll post an update as soon as the issue is fully resolved.

Our team is continuing to work on a fix for the unsafe head stall. At this time, node operators may see a stalled or sporadically updating unsafe head.

The issue is the result of instability in L1 nodes, causing blob data to be periodically unavailable to the sequencer.

We'll continue to update you here.

Our team has identified the cause of the unsafe head stall, and is actively working on a fix. At this time, node operators will continue to experience a stalled unsafe head. We’ll continue to share updates as we have them.

We have resolved the performance issues on OP Mainnet. The performance issues were a result of transactions with a high I/O cost coinciding with op-geth's automated background compaction. We have implemented multiple mitigations to avoid such scenarios happening in the future. We will also be upgrading the underlying hardware OP Mainnet runs on in order to provide additional buffer.

We observed another period (approximately 5 minutes) of slow blocks. Block production has resumed and we are continuing to monitor.

The unsafe head is currently performing as normal, however we may still see occasional slow unsafe heads as we roll out performance fixes to the network. We will continue to update this issue if extended periods of slow unsafe heads occur.

No action is required from users.

We continue to see intermittent degraded performance on the sequencer's unsafe head.

We have identified the cause of the issue and have applied a fix.