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

Our team has implemented a fix to resolve the slow block production, and is monitoring the situation.

Our team has identified the cause of the slow block production, and is actively working on a fix.

This was the result of a misconfiguration. At this time, users will continue to experience slow syncing until the updated configuration rolls out.

Our team has resolved the Optimism Goerli safe & unsafe head hatl, and transaction sequencing 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!

L1 has started finalizing again, and the network 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 mitigate the instability on L1, and is monitoring the situation.

We’ll post an update as soon as the issue is fully resolved. At this time, syncing from L1 and withdrawals should be operational.

Our team has identified the cause of the batch submitter lag, and is actively working on a fix.

This appears related to ongoing finality issues on Ethereum mainnet.

At this time, users syncing from L1 will experience delays receiving blocks and users attempting to post withdrawals will experience delays until our backlog of state proposals clears.

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

Our team has resolved the safe head halt, and the Optimism Goerli network 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 slow safe head progression & safe head halt, and has deployed a fix.

The issue is the result of unusually high throughput on Optimism Goerli with which the batcher couldn't temporarily keep up given its current configuration. We tweaked the configuration and expect the safe head to catch up soon.

At this time, user will continue to experience a safe head halt or slow safe head progression.

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

Our team has resolved the block production stall. Nodes should be able to fully sync 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 block production stall, and is monitoring the situation.

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

Our team has identified the cause of the block production stall, and is actively working on a fix.

One of our read-only replicas failed, which caused requests for newly created blocks from the sequencer to fail. The sequencer itself was unaffected.

At this time, node operators may continue to experience instability as we recover the failed replica.

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