Our team has resolved the issue with legacy withdraws. You should be able to use the bridge interface normally. If you continue to experience an issue, please let us know on Discord.
Thanks for your patience with us!

The bridge interface for Goerli is working again for new withdraws and withdraws issued after February. For withdraws initiated before February we are still investigating.
Thanks for the patience!

Our team has resolved the head halt, and block production 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 head halt, and is monitoring the situation. No action is required on the part of replica operators. Nodes should automatically come back in sync as new data is posted to L1.

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

Our team continues to investigate the head halt on Goerli. While we are seeing the network start to recover, block production is still degraded.

We’ll continue to update you here.

Our team continues to investigate the head halt on Goerli. At this time, the chain remains halted.

We’ll continue to update you here.

Our team continues to investigate the head halt on Goerli.

We'll continue to update you here.

Our team continues to investigate the head halt on Goerli.

We'll continue to update you here.

Our team continues to investigate the head halt on Goerli. At this time, the chain remains halted.

We’ll continue to update you here.

This incident has been resolved as of 3/15 already.

We are resolving this incident. Please watch our Twitter for updates once we have published a fixed op-node release and node operators can remove the temporary flag.

We have publicly shared the immediate fix to solve the issue for node operators on Optimism Goerli. Major services and infrastructure that operate Optimism Goerli nodes are slowly starting to resume operations as they add the specified flag.

We will post an update when we have published a fixed op-node release and node operators can remove the temporary flag.

The sequencer is confirmed to be up and processing transactions, deposits, and withdrawals safely. All nodes serving the public RPC endpoint have been updated with the below flag.

Our team has identified the cause of the Optimism Goerli node halts.

With the L1 Goerli network upgrading to Shapella, a change during Shanghai was made to how the block hash is derived. We have checks inside the op-node to recompute the block hash to ensure your L1 RPC is being honest - these started failing with the Shanghai updates.
This will prevent any nodes being operated on Optimism Goerli from continuing to produce new blocks. The sequencer is confirmed to be up and processing transactions, deposits, and withdrawals safely.

If you operate nodes on Optimism Goerli:

To immediately fix this issue, please add a flag:
--l1.trustrpc=true
or
OP_NODE_L1_TRUST_RPC="true"
to disable these block hash checks.

We will be pushing a new release of the op-node in the coming days with a fix. After upgrading to that new release you will be able to remove the above flag.

Our team has mitigated most of the abusing traffic. However, out of an abundance of caution and to protect normal HTTP traffic we will continue disabling WebSocket services on the public endpoint.

Please use an infrastructure provider such as Alchemy in the meantime if you need WebSocket support.

Our team has resolved the RPC issue, and block production 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 issue with the RPC provider, 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 halt, and is actively working on a fix.

The issue is related to instability on an upstream RPC provider.

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

The issue has been resolved.

We implemented a fix and currently monitoring the result.

We have identified the issue, and are working on a fix. We expect to have the system back online within the next 15 minutes.

The bug has been identified and a fix was pushed to the sequencer. All replicas have automatically recovered and block production has resumed.

We have successfully re-synced the sequencer, and re-enabled transaction ingress. We are monitoring for further issues.

Re-syncing the sequencer caused a large chain reorganization on L2. If you are running an archival Optimism Goerli node, no action is necessary - the reorg was processed automatically. If you are running a full node, you will need to re-sync your node from the migrated Bedrock Goerli data directory.

Infrastructure providers may need some time to re-sync their nodes as a result of this issue. See their respective status pages for more information.

We’re sorry for any frustrations this outage caused our community, and are committed to sharing a post-mortem soon.

Our team has discovered that the earlier provider outage triggered a bug in an Optimism node, which caused syncing from Optimism and L1 to stop. Our team is currently syncing the sequencer, which is a process we anticipate could take up to several hours. Transactions submitted during the last two hours may be replayed if they are still in our transaction pool, otherwise they will be dropped.

We will be working with our infra partners to ensure they’re able to get Optimism nodes up and running as quickly as possible, and will update again here when we have new information or full resolution. In the meantime, there is no action required from users.

Transaction ingress on Goerli has been disabled while the sequencer catches up. We expect service to be restored within 15 minutes.

We're still seeing degraded performance on Goerli. We are working on a fix.

We have deployed a fix for the Goerli testnet, and are monitoring the result. Nodes may need a few minutes to come back in sync.

Mainnet has recovered.

One of our upstream RPC providers encountered an error. We're switching our infrastructure over to a new provider.