Optimism - Notice history

This incident has been resolved. Node sync is fully back to normal.

We have applied a fix for the slow block sync. At this time, nodes should be syncing as normal. We will continue monitoring the network.

We are investigating reports of slow block sync.

Our team has resolved the OP Goerli head 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 implemented a fix to resolve the OP Goerli chain halt, 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 OP Goerli Head Halt, and is actively working on a fix.

The issue is the result of an internal problem with our sequencer L1 connection.

At this time, all users will continue to experience a Goerli chain halt until we have restarted the relevant services with a fixed configuration.

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

Our team has resolved the Goerli head stall for some node operators, and public infrastructure should now be fully operational for all users.

As a precaution, we advise all OP Stack node operators (including mainnet chains) to change their op-node to use ws instead of http for the l2 connection to op-geth while we're investigating the underlying issue further. So if you use --l2 http://localhost:8551 to connect to op-geth, change that to --l2 ws://localhost:8551. No need to restart op-geth. We don't expect the issue that affected some Goerli nodes to be a risk to any mainnet OP Stack nodes, but still advise node operators to change this setting as a precaution.

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 Goerli head stall for some node operators, and is actively working on a fix.

At this time, some users of public infrastructure and node operators will continue to experience a head stall.

We advise node operators to change their op-node to use ws instead of http for the l2 connection to op-geth as a quick remedy while we're working on a proper fix. So if you use --l2 http://localhost:8551 to connect to op-geth, change that to --l2 ws://localhost:8551. No need to restart op-geth.

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