Duration: 1 hour and 2 minutes

Affected Components: Transaction Sequencing

Mar 4, 23:54:08 GMT+0
Investigating - Due to an investigation of network bottlenecks the Flashblocks streaming websocket endpoints are temporarily unavailable..

Mar 5, 00:55:49 GMT+0
Resolved - This incident has been resolved..

Duration: 10 minutes

Affected Components: Batch Submission, Public API, Withdrawals, , Deposits, Transaction Sequencing, Node Sync, Mainnet →

Mar 4, 23:04:00 GMT+0
Investigating - 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..

Mar 4, 23:10:00 GMT+0
Monitoring - We implemented a fix and are currently monitoring the result..

Mar 4, 23:14:00 GMT+0
Resolved - This incident has been resolved, signified by the restored stable chain progression..

Mar 4, 23:07:00 GMT+0
Identified - 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..

Duration: 4 hours and 2 minutes

Affected Components: Transaction Sequencing

Nov 19, 19:13:03 GMT+0
Identified - The problem has been diagnosed and a fix is being worked on by the flashbots team. .

Nov 19, 21:30:24 GMT+0
Monitoring - A fix has been applied and we are monitoring for stability..

Nov 19, 21:36:43 GMT+0
Resolved - This incident has been resolved, flashblocks are now operational again..

Nov 19, 17:34:30 GMT+0
Investigating - Following the activation of the Jovian hardfork, we detected some problems with op-rbuilder and are investigating the root cause..

Nov 19, 17:45:20 GMT+0
Investigating - To clarify, regular (non-flashblocks) usage is unaffected. Unsafe and safe head progression and the rest of the system are fully operational. .

Duration: 22 hours and 56 minutes

Affected Components: Transaction Sequencing

Sep 25, 18:00:00 GMT+0
Identified - We are planning for a scheduled maintenance for flashblocks during that time. Only flashblocks production will be affected, normal block production and systems should not be affected.

Sep 26, 00:03:35 GMT+0
Identified - Maintenance is still on going. No issues have come up, rather we are just monitoring our infrastructure for stability.

Sep 26, 16:55:50 GMT+0
Completed - Maintenance has completed successfully..

Duration: 22 minutes

Affected Components: Public API

Aug 19, 18:05:31 GMT+0
Resolved - This incident has been resolved..

Aug 19, 17:43:56 GMT+0
Monitoring - We experienced an outage of our mainnet public endpoint during routine cluster upgrade. We implemented a fix and are currently monitoring the result..

Affected Components: Withdrawals

May 14, 14:52:14 GMT+0
Resolved - This is a test and not a real security incident. This is dedicated for testing our Incident Response Process in case of an emergency.

May 14, 15:08:28 GMT+0
Resolved - Resolved DRILL TEST. .

Duration: 16 minutes

Affected Components: Withdrawals

Apr 14, 15:47:34 GMT+0
Investigating - This is test for testing our process for incident response this is a DRILL. .

Apr 14, 16:03:54 GMT+0
Resolved - This incident has been resolved..

Duration: 7 hours and 9 minutes

Affected Components: Deposits, Withdrawals, Batch Submission, Transaction Sequencing

Mar 5, 07:30:00 GMT+0
Identified - 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..

Mar 5, 11:16:00 GMT+0
Monitoring - 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: <https://github.com/ethereum/go-ethereum/releases/tag/v1.15.5> 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..

Mar 5, 12:58:45 GMT+0
Monitoring - 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: <https://github.com/ethereum/go-ethereum/releases/tag/v1.15.5> Nethermind: <https://github.com/NethermindEth/nethermind/releases/tag/1.31.4> Reth: <https://github.com/paradigmxyz/reth/releases/tag/v1.2.2> Erigon: <https://github.com/erigontech/erigon/releases/tag/v3.0.0-rc2> 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..

Mar 5, 14:38:56 GMT+0
Resolved - 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..

Duration: 1 hour and 28 minutes

Affected Components: Deposits, Withdrawals, Batch Submission, Node Sync, Public API, Transaction Sequencing

Dec 5, 19:32:00 GMT+0
Identified - 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..

Dec 5, 21:00:00 GMT+0
Resolved - This incident has been resolved..

Duration: 1 hour

Affected Components: Public API

Sep 17, 22:30:00 GMT+0
Completed - Maintenance has completed successfully.

Sep 17, 21:30:01 GMT+0
Identified - Maintenance is now in progress.

Sep 17, 21:30:00 GMT+0
Identified - We are doing maintenance on the OP Sepolia public endpoint. No downtime is expected but be aware in case of intermittent issues..

Duration: 5 hours and 35 minutes

Affected Components: Public API, Deposits, Node Sync, Withdrawals, Batch Submission, Transaction Sequencing

Sep 6, 00:59:12 GMT+0
Resolved - False alarm, no network degradation occurred.

Sep 6, 00:53:38 GMT+0
Investigating - We are currently investigating this incident..

Duration: 19 minutes

Affected Components: Node Sync, Transaction Sequencing

Sep 3, 18:08:06 GMT+0
Identified - We have identified the cause of the stall, and are deploying a mitigation. Nodes may need to wait for the next safe head increase before they resume syncing..

Sep 3, 17:58:58 GMT+0
Investigating - We are currently investigating this incident..

Sep 3, 18:11:28 GMT+0
Monitoring - We have deployed the mitigations and the network is syncing again. At this time the network is fully operational..

Sep 3, 18:18:22 GMT+0
Resolved - This incident has been resolved..

Duration: 23 minutes

Affected Components: Public API, Node Sync, Transaction Sequencing

Aug 13, 17:23:25 GMT+0
Resolved - This incident has been resolved, safe and unsafe chain are advancing normally. Thanks for your patience with us!.

Aug 13, 17:18:24 GMT+0
Monitoring - The sequencer has caught up sequencing and the remaining network should pick up after the next safe head increase. This should resolve within the next few minutes..

Aug 13, 17:00:00 GMT+0
Investigating - We are investigating an OP Sepolia chain halt. All users are affected..

Duration: 16 minutes

Affected Components: Withdrawals

Aug 9, 16:03:16 GMT+0
Identified - We have identified the problem and are working on a fix. .

Aug 9, 16:15:38 GMT+0
Monitoring - We implemented a fix and are currently monitoring the result..

Aug 9, 16:02:56 GMT+0
Investigating - We are seeing a delay in our mainnet proposer instance submitting proposals on chain. .

Aug 9, 16:18:28 GMT+0
Resolved - This incident has been resolved, proposals have resumed..

Duration: 1 hour and 6 minutes

Affected Components: Transaction Sequencing

Aug 6, 18:17:05 GMT+0
Resolved - issue has been resolved and network is healthy..

Aug 6, 17:11:00 GMT+0
Investigating - OP Sepolia experienced a halt of the unsafe head for around 6 minutes. We have intervened to bring the network back to health and will continue to monitor the situation. .

Aug 6, 17:26:00 GMT+0
Monitoring - We have intervened to restore network health and will continue to monitor the situation..

Duration: 38 minutes

Affected Components: Node Sync, Transaction Sequencing

Jul 30, 20:00:00 GMT+0
Identified - We are planning for a scheduled maintenance during that time. No downtime is expected..

Jul 30, 20:00:01 GMT+0
Identified - Maintenance is now in progress.

Jul 30, 20:37:53 GMT+0
Completed - Maintenance was completed successfully. .

Aug 6, 18:18:03 GMT+0
Completed - Maintenance has completed successfully..

Duration: 10 minutes

Affected Components: Public API, Deposits, Node Sync, Withdrawals, Batch Submission, Transaction Sequencing, Deposits, Withdrawals, Batch Submission, Node Sync, Public API, Transaction Sequencing

Jul 23, 19:19:08 GMT+0
Investigating - Our team is investigating a chain halt on Sepolia. At this time, all users may experience problems interacting with the chain. We apologize for the inconvenience and will share an update once we have more information..

Jul 23, 19:23:02 GMT+0
Identified - Our team has identified the cause of the halt and is working on a fix..

Jul 23, 19:25:07 GMT+0
Monitoring - 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..

Jul 23, 19:28:59 GMT+0
Resolved - 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!.

Duration: 41 minutes

Affected Components: Node Sync, Transaction Sequencing

Jul 16, 20:00:01 GMT+0
Identified - Maintenance is now in progress.

Jul 16, 20:36:13 GMT+0
Identified - We have completed the rollback, and sync should be back to normal. We will monitor for any further issues..

Jul 16, 20:18:25 GMT+0
Identified - Ran into an issue during maintenance resulting in short unsafe head stall. Change has been reverted. Continuing to monitor..

Jul 16, 20:31:01 GMT+0
Identified - We are experiencing issues with node sync. At this time users my experience degraded performance syncing nodes or processing transactions..

Jul 16, 17:41:19 GMT+0
Identified - maintenance is delayed by 2 hours, will begin 8pm gmt..

Jul 16, 20:00:00 GMT+0
Identified - We are planning for a scheduled maintenance during that time to improve the reliability of our sequencer. No downtime is expected..

Jul 16, 20:40:48 GMT+0
Completed - We will postpone further maintenance until we root cause the issue mentioned earlier. At this time the network is fully operational..

Duration: 1 day, 15 hours and 49 minutes

Affected Components: Batch Submission

Jun 29, 00:05:00 GMT+0
Investigating - Due to heightened L2 block size on OP Sepolia, the batcher is seeing some performance degradation. This is causing the safe head to progress more slowly than usual. We are currently investigating. .

Jun 30, 14:28:07 GMT+0
Monitoring - We have identified and applied a potential fix for the batcher performance issue. We will continue to monitor the situation..

Jun 30, 15:54:23 GMT+0
Resolved - The safe head has now resumed normal operation. .

Duration: 32 minutes

Affected Components: Transaction Sequencing

Jun 26, 20:55:48 GMT+0
Monitoring - We were conducting some cluster maintenance and had unexpected short downtime. We have implemented a fix and are currently monitoring the result..

Jun 26, 21:28:08 GMT+0
Resolved - This incident has been resolved..

Duration: 3 hours and 56 minutes

Affected Components: Batch Submission, Transaction Sequencing

Jun 20, 17:10:29 GMT+0
Identified - We are currently experiencing elevated fees on OP Mainnet due to high blob fees on L1\. We are mitigating the issue by switching batch submission back to calldata. While the switch rolls out, users may experience higher fees than normal and the safe head may increase less often due to L1 congestion..

Jun 20, 17:17:06 GMT+0
Monitoring - 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..

Jun 20, 18:26:00 GMT+0
Monitoring - 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..

Jun 20, 21:06:10 GMT+0
Resolved - L2 fees are no longer elevated, L1 blob fees are trending down..

Duration: 49 minutes

Affected Components: Transaction Sequencing

Jun 11, 18:09:04 GMT+0
Resolved - This incident has been resolved..

Jun 11, 17:19:40 GMT+0
Investigating - Our team is investigating a sequencer outage on op-sepoolia. At this time, nodes will experience an unsafe head stall. We apologize for the inconvenience and will share an update once we have more information..

Jun 11, 17:26:39 GMT+0
Identified - 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..

Jun 11, 17:30:54 GMT+0
Monitoring - 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..

Duration: 1 hour and 17 minutes

Affected Components: Node Sync, Batch Submission, Transaction Sequencing

Jun 4, 17:18:12 GMT+0
Identified - We are upgrading our OP Sepolia cluster. We expect minor service interruptions while the upgrade completes. We expect the upgrade to take approximately 20 minutes..

Jun 4, 18:35:37 GMT+0
Completed - The cluster upgrade is complete..

Duration: 32 minutes

Affected Components: Transaction Sequencing

Jun 3, 20:00:24 GMT+0
Investigating - Our team is investigating an unsafe head stall on op-mainnet. At this time, node operators may experience a delay in receiving unsafe blocks. We apologize for the inconvenience and will share an update once we have more information..

Jun 3, 20:04:56 GMT+0
Monitoring - 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..

Jun 3, 20:32:21 GMT+0
Resolved - 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!.

Duration: 1 hour and 22 minutes

Affected Components: Transaction Sequencing

May 26, 21:36:27 GMT+0
Investigating - Our team is investigating an unsafe head stall on op-mainnet. At this time, node operators may see their node's unsafe head stall. We apologize for the inconvenience and will share an update once we have more information..

May 26, 21:44:15 GMT+0
Identified - 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..

May 26, 22:08:59 GMT+0
Identified - 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..

May 26, 22:16:11 GMT+0
Monitoring - 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..

May 26, 22:58:33 GMT+0
Resolved - 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!.

Duration: 23 hours and 48 minutes

Affected Components: Withdrawals

May 23, 07:54:00 GMT+0
Resolved - This incident has been resolved..

May 22, 20:06:00 GMT+0
Identified - We have experienced some downtime from the proposer on mainnet. The root cause has been identified and a fix has been applied. Withdrawal proving was affected for several hours but is now operational. Withdrawal finalization was not impacted..

Duration: 17 days, 9 hours and 12 minutes

Affected Components: Node Sync, Transaction Sequencing

May 18, 08:10:00 GMT+0
Investigating - We became aware of a slowdown in the unsafe head of our sequencer today at 09:10 UTC. This impacted other nodes in the network, presenting as an unsafe head stall for approximately 9 minutes. The performance issue resolved on its own after approximately 20 minutes. We are aware of the root cause and will be issuing further communications in due course. .

May 19, 13:31:59 GMT+0
Investigating - We continue to see intermittent degraded performance on the sequencer's unsafe head..

May 19, 14:07:01 GMT+0
Monitoring - 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..

May 21, 23:44:48 GMT+0
Monitoring - We observed another period (approximately 5 minutes) of slow blocks. Block production has resumed and we are continuing to monitor..

Jun 4, 17:21:37 GMT+0
Resolved - 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..

Duration: 25 minutes

Affected Components: Public API, Deposits, Node Sync, Withdrawals, Batch Submission, Transaction Sequencing

May 14, 17:32:16 GMT+0
Identified - We have identified the cause of the issue and have applied a fix. .

May 14, 17:18:44 GMT+0
Investigating - We are currently investigating this incident..

May 14, 17:41:12 GMT+0
Monitoring - We implemented a fix and are currently monitoring the result..

May 14, 17:43:58 GMT+0
Resolved - This incident has been resolved..

Duration: 44 minutes

Affected Components: Transaction Sequencing

May 11, 22:44:21 GMT+0
Investigating - We are investigating reports of an unsafe head stall on OP Mainnet..

May 11, 22:49:42 GMT+0
Investigating - We have identified that an unsafe head stalled occurred, but has since self-resolved. We are investigating the root cause. At this time the network is fully operational..

May 11, 23:28:06 GMT+0
Resolved - We have identified the root cause of the unsafe head stall, and will prioritize a fix. At this time the network remains fully operational. No action is required from any user..

Duration: 38 minutes

Affected Components: Node Sync, Transaction Sequencing

Apr 30, 05:09:28 GMT+0
Investigating - Our team is investigating reports of unsafe head stalls on OP Mainnet. At this time, all users may experience degraded performance syncing nodes or submitting transactions. We apologize for the inconvenience and will share an update once we have more information..

Apr 30, 05:25:54 GMT+0
Investigating - Our team continues to investigate reports of unsafe head stalls. At this time, users may continue experience degraded performance syncing nodes or submitting transactions..

Apr 30, 05:33:12 GMT+0
Identified - Our team has identified the cause of the unsafe head stall, and is actively working on a fix. The issue was related to degraded sync performance of an internal beacon node. At this time, some users may still experience degraded performance syncing nodes or submitting transactions. However, we expect the issue to be resolved for the majority of users..

Apr 30, 05:34:27 GMT+0
Monitoring - 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..

Apr 30, 05:47:39 GMT+0
Resolved - Our team has resolved the unsafe head stall. The system 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!.

Duration: 4 minutes

Affected Components: Withdrawals

Feb 15, 15:01:51 GMT+0
Completed - Withdraws now are unpaused..

Feb 15, 14:00:00 GMT+0
Identified - On Thursday, Feb 15th 9:00am ET (6:00am PT), withdraws from OP Mainnet L2 to L1 will be paused as part of a planned maintenance window lasting one hour. During the pause withdraws to L1 will be rejected. The network will be unpaused at 10:00am ET (7:00am PT)..

Feb 15, 14:01:00 GMT+0
Identified - Withdraws now are paused..

Feb 15, 14:00:01 GMT+0
Identified - Maintenance is now in progress.

Duration: 1 hour

Affected Components: Deposits, Withdrawals

Jan 23, 18:00:00 GMT+0
Completed - Maintenance has completed successfully.

Jan 23, 17:00:01 GMT+0
Identified - Maintenance is now in progress.

Jan 23, 17:00:00 GMT+0
Identified - We will be conducting a test of our forthcoming pausability features on the Sepolia network on noon EST on Tuesday, January 23rd, lasting for approximately 1 hour. At this time the following methods on our Bridge contracts will revert if called: - OptimismPortal.proveWithdrawalTransaction() - OptimismPortal.finalizeWithdrawalTransaction() - L1CrossDomainMessenger.relayMessage() - StandardBridge.finalizeBridgeERC20() - StandardBridge.finalizeBridgeETH() - L1ERC721Bridge.finalizeBridgeERC721() This is part of ongoing efforts to improve the security of our system and our ability to respond to an incident. Thank you..

Duration: 1 hour

Dec 20, 20:42:03 GMT+0
Completed - Maintenance has completed successfully..

Dec 20, 20:38:49 GMT+0
Identified - OP Goerli network paused successfully..

Dec 20, 20:30:00 GMT+0
Identified - On Wednesday, Dec 20th 12:30pm PST, OP Goerli will be paused as part of a planned maintenance window lasting approximately one hour. During the pause, the L1 state will be frozen point-in-time and transactions will be rejected, until the unpause is issued. OP Mainnet and OP Sepolia won't be affected..

Dec 20, 20:30:01 GMT+0
Identified - Maintenance is now in progress.

Dec 20, 20:41:50 GMT+0
Identified - OP Goerli network unpaused. Transaction hash: https://goerli.etherscan.io/tx/0x64cb6431423c4b08cedc3f06b3737c57de723e221c68423fc72b8326c0d9156b.

Dec 20, 20:30:01 GMT+0
Identified - Pause transaction: https://goerli.etherscan.io/tx/0xbbda99c8af39e983468876286cc4565d1dc86f59470173fe281d3d65abc7e460.

Duration: 10 minutes

Affected Components: Node Sync, Batch Submission, Withdrawals, Public API, Transaction Sequencing

Aug 28, 17:10:28 GMT+0
Completed - Maintenance has completed successfully..

Aug 28, 17:00:01 GMT+0
Identified - Maintenance is now in progress.

Aug 28, 17:00:00 GMT+0
Identified - On Monday, August 28th at 17:00 UTC, we are upgrading the OP Mainnet sequencer deployment configuration to enable future zero downtime deployments. As part of this planned maintenance, users can expect up to five minutes of downtime on OP Mainnet. We’ll update this status once the maintenance window is completed and OP Mainnet is fully operational on https://status.optimism.exchange/ .

Duration: 13 minutes

Affected Components: Deposits, Transaction Sequencing

Jul 12, 20:00:00 GMT+0
Identified - On Wednesday, July 12, 2023 at 20:00 UTC, we are upgrading the version of op-geth on the OP Mainnet sequencer to reduce the average transaction inclusion latency from 2-4 seconds to 0-2 seconds. As part of this planned maintenance, users can expect up to five minutes of downtime on the OP Mainnet Sequencer. We’ll update this status once the maintenance window is completed and the OP Mainnet Sequencer is fully operational. .

Jul 12, 20:02:40 GMT+0
Identified - The sequencer is temporarily down for scheduled maintenance. We are upgrading the version of op-geth on the OP Mainnet sequencer to reduce the average transaction inclusion latency from 2-4 seconds to 0-2 seconds. Users can expect up to five minutes of downtime on the OP Mainnet Sequencer. We’ll update this status once the maintenance window is completed and the OP Mainnet Sequencer is fully operational..

Jul 12, 20:12:36 GMT+0
Completed - OP Mainnet Sequencer maintenance has completed safely!.

Jul 12, 20:09:44 GMT+0
Identified - Sequencer downtime is taking longer than the expected time. Please standby for updates. The sequencer is temporarily down for scheduled maintenance. We are upgrading the version of op-geth on the OP Mainnet sequencer to reduce the average transaction inclusion latency from 2-4 seconds to 0-2 seconds. We’ll update this status once the maintenance window is completed and the OP Mainnet Sequencer is fully operational..

Duration: 23 minutes

Jun 27, 10:30:00 GMT+0
Identified - We are going to update the Goerli sequencer. A few minutes of sequencer downtime can be expected..

Jun 27, 10:53:14 GMT+0
Completed - Update has completed successfully..

Jun 27, 10:45:01 GMT+0
Identified - Update is now in progress..

Duration: 19 minutes

Affected Components: Public API

Jun 12, 21:19:13 GMT+0
Completed - Maintenance has completed successfully..

Jun 12, 21:00:00 GMT+0
Identified - We are planning for a scheduled maintenance during that time. No downtime is expected but please be aware just in case..

Duration: 6 hours and 48 minutes

Affected Components: Deposits, Withdrawals, Public API, Transaction Sequencing

Jun 6, 16:36:54 GMT+0
Identified - We are now starting to execute the L2 portion of the migration. This is the longest step in the migration process, and could take up to 1.5 hours. During this phase of the migration, ETH balances and withdrawals will be migrated. Successful completion of this stage will conclude the L2 portion of the migration, and we will perform all related checks before moving on to subsequent phases..

Jun 6, 18:50:28 GMT+0
Identified - The Bedrock sequencer has started up. Images, and data directories for node operators can be found [here](https://community.optimism.exchange/docs/useful-tools/networks/#links). Key external OP Mainnet infrastructure is starting to come back online. View the [OP Mainnet Infra Tracker](https://oplabs.notion.site/External-OP-Mainnet-Bedrock-Upgrade-Infra-Status-Tracker-07d7c9c0916243b8b743b74af77d37f9?pvs=4) to follow along. .

Jun 6, 16:00:32 GMT+0
Identified - The migration has started. Legacy network deposits and withdrawals have been paused. Transaction acceptance on the legacy sequencer has been halted..

Jun 6, 18:26:31 GMT+0
Identified - L1 smart contract upgrades have been successfully implemented. The portal has been unpaused, and deposits/withdrawals have been re-enabled..

Jun 6, 17:44:27 GMT+0
Identified - Node Operators: Docker images are now available in our community hub docs. `op-node` version: https://github.com/ethereum-optimism/optimism/releases/tag/op-node%2Fv1.1.0 (Docker Images are in the release notes) `op-geth` version: https://github.com/ethereum-optimism/op-geth/releases/tag/v1.101105.2 (Docker Images are in the release notes) Please await the upload of the Migrated Datadir before you can fully spin up your OP Mainnet Bedrock nodes..

Jun 6, 16:00:00 GMT+0
Identified - The OP Mainnet Bedrock Upgrade is expected to run for 2-4 hours. Find all of the details here: https://optimism.exchange/bedrock-upgrade Watch for updates on this status page for: * Images for node operators * Datadirs for both full node and archival node operators * Notifications on when deposits, withdrawals, and the sequencer are back live..

Jun 6, 19:10:01 GMT+0
Identified - For node operators: We have received reports that the [full node Bedrock datadir](https://community.optimism.exchange/docs/useful-tools/networks/#parameters-for-node-operators) is taking a long time to download. Since it is available on GCS, you can use parallel downloader tools like `aria2` to make it faster. This method has seen download speeds in excess of 100MB/s. Some recommendations: - Run the download on a high-network box in the cloud. - Use aria2 or the gcloud storage cp command to download the file in parallel. .

Jun 6, 19:38:02 GMT+0
Identified - For Archival node operators: While we recommend using the `legacy-geth` archival datadir we upload [once it's ready](https://community.optimism.exchange/docs/useful-tools/networks/#links), given the size of the archival data disk and the time it'll take for it to become available (up to 24 hours), we recommend preserving your legacy archival nodes and routing archival traffic to them if possible. To check if your legacy archival node is able to serve traffic, please do the following: Verify that the head block number is `105235062` Verify that the head block hash is `0x21a168dfa5e727926063a28ba16fd5ee84c814e847c81a699c7a0ea551e4ca50` If both of these criteria are true, then your legacy archival node is on the same block as the archival datadir and can be used to serve user traffic. You can set `--rollup.historicalrpc <l2geth-rpc>` on `op-geth` and it will forward requests for historical data it can't handle to `l2geth`..

Jun 6, 18:20:01 GMT+0
Identified - The migrated (Bedrock) datadir required to spin up `op-geth` has been successfully hosted and is now ready for distribution. Full Node Operators are now fully unblocked to spin up. Archival Node Operators will need to wait for the archival datadir, which may take an additional 5-10 hours. The datadir can be downloaded from the link found in the OP Mainnet docs: https://community.optimism.exchange/docs/useful-tools/networks/#links.

Jun 6, 22:48:17 GMT+0
Completed - Much of our our core OP Mainnet infra is back online! Continue to track https://oplabs.notion.site/External-OP-Mainnet-Bedrock-Upgrade-Infra-Status-Tracker-07d7c9c0916243b8b743b74af77d37f9?pvs=4 for updates on other key infrastructure in the OP Mainnet ecosystem. The Bridge UI has been unpaused. Deposits and Withdrawals can now be executed on OP Mainnet from: https://app.optimism.exchange/bridge/.

Jun 6, 21:52:17 GMT+0
Identified - The public endpoint is back live: https://mainnet.optimism.exchange/ This should unblock most wallets to begin working again..

Duration: 30 minutes

Affected Components: Public API

Mar 28, 19:40:00 GMT+0
Identified - [Planned] migrating public endpoint backend to new infrastructure. there may be some temporary hiccups.

Mar 28, 20:10:15 GMT+0
Completed - Maintenance completed..

Duration: 18 minutes

Mar 3, 15:44:30 GMT+0
Identified - Maintenance is now in progress..

Mar 3, 15:43:43 GMT+0
Identified - We are upgrading our infrastructure on Goerli to support the Regolith hardfork. We expect approximately 15 minutes of downtime..

Mar 3, 16:01:48 GMT+0
Completed - Maintenance has completed successfully. We will monitor the network for any issues..

Duration: 55 minutes

Affected Components: Deposits, Withdrawals, Transaction Sequencing, Public API

Jan 26, 22:00:00 GMT+0
Identified - We will be performing some necessary upgrades to our mainnet Kubernetes infrastructure. We expect no more than 15 minutes of downtime as we perform these upgrades..

Jan 26, 22:54:31 GMT+0
Completed - Maintenance has completed successfully, sequencer is back online..

Jan 26, 22:00:01 GMT+0
Identified - Maintenance is now in progress.

Duration: 23 hours and 58 minutes

Jan 12, 18:07:31 GMT+0
Identified - Update: We're wrapping up the last bit of prep work before halting the Optimism Goerli network and beginning the upgrade. Please standby, the migration will begin shortly..

Jan 13, 17:57:40 GMT+0
Completed - The Optimism Bridge is back online - deposits and withdrawals are now functional: https://app.optimism.exchange/bridge.

Jan 12, 18:00:01 GMT+0
Identified - Maintenance is now in progress.

Jan 12, 21:04:15 GMT+0
Identified - The Optimism Goerli migration to the Bedrock release is in its final stages! There were some unexpected delays that we will be addressing to ensure the Optimism Mainnet upgrade takes less time. The Optimism Goerli Sequencer has been upgraded to the Bedrock release and is back online at https://goerli-sequencer.optimism.exchange ! Transactions are now being accepted, and we are testing to see that Deposits and Withdrawals are functional. op-node image is live at: [us-docker.pkg.dev/oplabs-tools-artifacts/images/op-node:v0.10.9](url) .

Jan 12, 19:14:09 GMT+0
Identified - The final blocks on the legacy Optimism Goerli sequencer have been mined and batch submitted to L1. The last block mined was block number 4061223, and the first block of the Bedrock release will be block number 4061224..

Jan 12, 18:20:58 GMT+0
Identified - The upgrade to the Bedrock Release of the Optimism Goerli Network has begun! Transactions to the Sequencer are halted (`eth_sendRawTransaction` RPC calls will be rejected by the Sequencer). Deposits and Withdrawals are paused. The Public RPC Endpoint (https://goerli.optimism.exchange/) will stay up with only read access..

Jan 12, 19:51:27 GMT+0
Identified - The Optimism Goerli Bedrock upgrade is almost complete. We are working on spinning the Sequencer back online. Expect final `op-node` and `op-geth` images shortly..

Jan 12, 18:00:00 GMT+0
Identified - On January 12 at 1800 UTC, the OP Labs engineering team will begin the work to migrate Optimism’s Goerli Testnet to Bedrock. We expect the migration to take between thirty minutes and 2 hours, during which the Goerli network will be unavailable until the upgrade is complete. For more information about what to expect on upgrade day, please see the [Upgrade Guide](https://community.optimism.exchange/docs/developers/bedrock/upgrade-guide/)..

Jan 12, 21:51:50 GMT+0
Completed - The Optimism Goerli network upgrade to the Bedrock release is complete! Deposits, Withdrawals, and transactions to the Sequencer are now back live. The public `https://goerli.optimism.exchange` endpoint is back up and will resume accepting transactions shortly. The Optimism Bridge Frontend is still being updated. Follow along as third party infrastructure projects spin back online here: https://oplabs.notion.site/External-Optimism-Goerli-Bedrock-Upgrade-Infra-Status-Tracker-86e67c08c09a4a85ae7987fca6fb1ddb.

Affected Components: Public API

Oct 12, 20:39:06 GMT+0
Completed - Maintenance complete..

Duration: 30 minutes

Affected Components: Public API

Sep 8, 18:00:01 GMT+0
Identified - Maintenance is now in progress.

Sep 8, 18:00:00 GMT+0
Identified - From September 8th 2PM EDT - 2:30PM EDT we will be undergoing planned maintenance to upgrade the public API endpoint for mainnet. There may be minimal downtime for users of the public endpoint during this window..

Sep 8, 18:30:00 GMT+0
Completed - Maintenance has completed successfully.

Duration: 1 hour

Aug 25, 18:00:01 GMT+0
Identified - Maintenance is now in progress.

Aug 25, 18:00:00 GMT+0
Identified - From August 25th 2PM EDT - 3PM EDT we will be undergoing planned maintenance to upgrade the public API endpoint for the goerli-devnet from our self-hosted nodes to infrastructure provided by Alchemy. There may be minimal downtime for users of the public endpoint during this window..

Aug 25, 19:00:00 GMT+0
Completed - Maintenance has completed successfully.

Duration: 1 hour

Affected Components: Public API

Jun 23, 18:00:01 GMT+0
Identified - Maintenance is now in progress.

Jun 23, 19:00:00 GMT+0
Completed - Maintenance has completed successfully.

Jun 23, 18:00:00 GMT+0
Identified - We are upgrading our public endpoint infrastructure to add support for splitting traffic between multiple providers, an action we committed to as part of our token launch retrospective. During this upgrade, there may be up to 30 minutes of downtime as we provision new load balancers. To avoid downtime, please switch to a third-party provider or run your own node before then..

Jun 23, 18:38:43 GMT+0
Identified - We have completed the update, and are monitoring for issues..

Duration: 1 hour

Affected Components: Public API, Transaction Sequencing

Jun 9, 18:00:01 GMT+0
Identified - Maintenance is now in progress.

Jun 9, 18:00:00 GMT+0
Identified - We are upgrading our infrastructure on mainnet. We expect less than 5 minutes of downtime as services restart..

Jun 9, 19:00:00 GMT+0
Completed - Maintenance has completed successfully.

Duration: 44 minutes

Jun 7, 18:11:15 GMT+0
Identified - We are upgrading our infrastructure on Kovan. There should be less than 5 minutes of downtime as services restart..

Jun 7, 18:55:28 GMT+0
Completed - Maintenance has completed successfully..

Duration: 1 day, 23 hours and 55 minutes

Affected Components: Public API

May 31, 21:15:59 GMT+0
Identified - We have temporarily limited archive node functionality until load subsides..

Jun 2, 21:10:54 GMT+0
Completed - Archive limitations have been removed..

Duration: 2 hours and 21 minutes

Affected Components: Public API, Transaction Sequencing

Mar 29, 18:00:00 GMT+0
Identified - We are planning for a scheduled maintenance during this time. No more than 5 minutes of downtime is expected..

Mar 29, 18:05:18 GMT+0
Identified - Maintenance is now in progress..

Mar 29, 20:20:57 GMT+0
Completed - Maintenance has completed successfully..