All systems operational

Mainnet
100.0% uptime

Public API

100.0% uptime
Jun 2023 · 100.0%Jul · 100.0%Aug · 100.0%
Jun 2023100.0% uptime
Jul 2023100.0% uptime
Aug 2023100.0% uptime

Bridge UI

100.0% uptime
Jun 2023 · 100.0%Jul · 100.0%Aug · 100.0%
Jun 2023100.0% uptime
Jul 2023100.0% uptime
Aug 2023100.0% uptime

Deposits

100.0% uptime
Jun 2023 · 100.0%Jul · 100.0%Aug · 100.0%
Jun 2023100.0% uptime
Jul 2023100.0% uptime
Aug 2023100.0% uptime

Withdrawals

100.0% uptime
Jun 2023 · 100.0%Jul · 100.0%Aug · 100.0%
Jun 2023100.0% uptime
Jul 2023100.0% uptime
Aug 2023100.0% uptime

Transaction Sequencing

100.0% uptime
Jun 2023 · 100.0%Jul · 100.0%Aug · 100.0%
Jun 2023100.0% uptime
Jul 2023100.0% uptime
Aug 2023100.0% uptime

Batch Submission

100.0% uptime
Jun 2023 · 100.0%Jul · 100.0%Aug · 100.0%
Jun 2023100.0% uptime
Jul 2023100.0% uptime
Aug 2023100.0% uptime

Node Sync

100.0% uptime
Jun 2023 · 100.0%Jul · 100.0%Aug · 100.0%
Jun 2023100.0% uptime
Jul 2023100.0% uptime
Aug 2023100.0% uptime

Goerli

100.0% uptime

Public API

100.0% uptime
Jun 2023 · 100.0%Jul · 100.0%Aug · 100.0%
Jun 2023100.0% uptime
Jul 2023100.0% uptime
Aug 2023100.0% uptime

Bridge UI

100.0% uptime
Jun 2023 · 100.0%Jul · 100.0%Aug · 100.0%
Jun 2023100.0% uptime
Jul 2023100.0% uptime
Aug 2023100.0% uptime

Deposits

100.0% uptime
Jun 2023 · 100.0%Jul · 100.0%Aug · 100.0%
Jun 2023100.0% uptime
Jul 2023100.0% uptime
Aug 2023100.0% uptime

Withdrawals

100.0% uptime
Jun 2023 · 100.0%Jul · 100.0%Aug · 100.0%
Jun 2023100.0% uptime
Jul 2023100.0% uptime
Aug 2023100.0% uptime

Transaction Sequencing

100.0% uptime
Jun 2023 · 100.0%Jul · 100.0%Aug · 100.0%
Jun 2023100.0% uptime
Jul 2023100.0% uptime
Aug 2023100.0% uptime

Batch Submission

99.99% uptime
Jun 2023 · 100.0%Jul · 99.96%Aug · 100.0%
Jun 2023100.0% uptime
Jul 202399.96% uptime
Aug 2023100.0% uptime

Node Sync

100.0% uptime
Jun 2023 · 100.0%Jul · 100.0%Aug · 100.0%
Jun 2023100.0% uptime
Jul 2023100.0% uptime
Aug 2023100.0% uptime

Sepolia

100.0% uptime

Public API

100.0% uptime
Jun 2023 · 100.0%Jul · 100.0%Aug · 100.0%
Jun 2023100.0% uptime
Jul 2023100.0% uptime
Aug 2023100.0% uptime

Bridge UI

100.0% uptime
Jun 2023 · 100.0%Jul · 100.0%Aug · 100.0%
Jun 2023100.0% uptime
Jul 2023100.0% uptime
Aug 2023100.0% uptime

Deposits

100.0% uptime
Jun 2023 · 100.0%Jul · 100.0%Aug · 100.0%
Jun 2023100.0% uptime
Jul 2023100.0% uptime
Aug 2023100.0% uptime

Withdrawals

100.0% uptime
Jun 2023 · 100.0%Jul · 100.0%Aug · 100.0%
Jun 2023100.0% uptime
Jul 2023100.0% uptime
Aug 2023100.0% uptime

Transaction Sequencing

100.0% uptime
Jun 2023 · 100.0%Jul · 100.0%Aug · 100.0%
Jun 2023100.0% uptime
Jul 2023100.0% uptime
Aug 2023100.0% uptime

Batch Submission

100.0% uptime
Jun 2023 · 100.0%Jul · 100.0%Aug · 100.0%
Jun 2023100.0% uptime
Jul 2023100.0% uptime
Aug 2023100.0% uptime

Node Sync

100.0% uptime
Jun 2023 · 100.0%Jul · 100.0%Aug · 100.0%
Jun 2023100.0% uptime
Jul 2023100.0% uptime
Aug 2023100.0% uptime

Notice history

Jul 2023

Goerli Full Sync Issues
  • Resolved
    Resolved

    OP Goerli is no longer experiencing node halts, which were caused by the L1 Goerli testnet reorg. As shared in the previous status, full node operators do need to take one of the following actions:

    1. Delete Geth’s datadir, then replace it with the fully-synced archival database available from https://datadirs.optimism.io/goerli-bedrock-archival-2023-07-29.tar.zst.
    2. Make a call to eth_getblockbynumber with finalized as the block tag. Then, roll the full node back to that block value + 1 using debug_setHead.
    3. Resync the full node from a backup prior to block 12572500, or from genesis.

    This issue is resolved and we will be sharing a full post-mortem when ready.

  • Monitoring
    Monitoring

    We have identified the root cause of this issue.

    The L1 Goerli testnet experienced a large reorg of approximately 18 blocks. In addition to the large reorg, a significant number of blocks were missed, resulting in one large reorg and many missing blocks. This caused a large (>256 block) reorg on OP Goerli. Currently, users operating full nodes on OP Goerli will experience a node halt. These nodes will not sync new blocks from the OP Goerli network, and may return inconsistent data over RPC. Users operating archival nodes on OP Goerli are not affected and we do not expect this issue to occur in any capacity on OP Mainnet.

    To resolve this issue, full node operators need to perform one of these actions:

    1. Delete Geth’s datadir, then replace it with the fully-synced archival database available from https://datadirs.optimism.io/goerli-bedrock-archival-2023-07-29.tar.zst.
    2. Make a call to eth_getblockbynumber with finalized as the block tag. Then, roll the full node back to that block value + 1 using debug_setHead.
    3. Resync the full node from a backup prior to block 12572500, or from genesis.

    We apologize for the inconvenience and will share a full post-mortem when ready.

  • Investigating
    Investigating

    Our team is investigating reports of issues with full node sync. At this time, users syncing full nodes may experience degraded performance.

    We apologize for the inconvenience and will share an update once we have more information.

Mainnet Safe Head Stall
  • Resolved
    Resolved

    Our team has resolved the safe head stall. Safe-only sync 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!

  • Identified
    Identified

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

    The issue is the result of an improperly closed channel. This is a known issue with the batcher, and will most likely resolve itself within the next hour.

    At this time, users syncing the safe head only will continue to experience delays receiving new blocks until a new batch is posted.

    Please wait while the improperly closed channel automatically expires.

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

  • Investigating
    Update

    Our team continues to investigate the safe head stall. At this time, users who only sync the safe head will continue to experience delays receiving new blocks. Users syncing the unsafe head will continue receiving new blocks. Transactions are being processed on the sequencer as normal.

    We narrowed down the issue to a problem submitting a batch to L1. These issues typically resolve themselves within an hour.

    We’ll continue to update you here.

  • Investigating
    Investigating

    Our team is investigating reports of a safe head stall on mainnet. At this time, users who only sync the safe head may experience delays receiving new blocks until a new batch is posted.

    We apologize for the inconvenience and will share an update once we have more information.

Jun 2023

OP Mainnet Bedrock Upgrade
  • Update
    June 06, 2023 at 9:52 PM
    In progress
    June 06, 2023 at 9:52 PM

    The public endpoint is back live: https://mainnet.optimism.io/

    This should unblock most wallets to begin working again.

  • Update
    June 06, 2023 at 7:38 PM
    In progress
    June 06, 2023 at 7:38 PM

    For Archival node operators: While we recommend using the legacy-geth archival datadir we upload once it's ready, 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.

  • Update
    June 06, 2023 at 7:10 PM
    In progress
    June 06, 2023 at 7:10 PM

    For node operators:
    We have received reports that the full node Bedrock datadir 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.
  • Update
    June 06, 2023 at 6:50 PM
    In progress
    June 06, 2023 at 6:50 PM

    The Bedrock sequencer has started up.

    Images, and data directories for node operators can be found here. Key external OP Mainnet infrastructure is starting to come back online. View the OP Mainnet Infra Tracker to follow along.

  • Update
    June 06, 2023 at 6:26 PM
    In progress
    June 06, 2023 at 6:26 PM

    L1 smart contract upgrades have been successfully implemented. The portal has been unpaused, and deposits/withdrawals have been re-enabled.

  • Update
    June 06, 2023 at 6:20 PM
    In progress
    June 06, 2023 at 6:20 PM

    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.io/docs/useful-tools/networks/#links

  • Update
    June 06, 2023 at 5:44 PM
    In progress
    June 06, 2023 at 5:44 PM

    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.

  • Update
    June 06, 2023 at 4:36 PM
    In progress
    June 06, 2023 at 4:36 PM

    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.

  • In progress
    June 06, 2023 at 4:00 PM
    In progress
    June 06, 2023 at 4:00 PM

    The migration has started. Legacy network deposits and withdrawals have been paused.

    Transaction acceptance on the legacy sequencer has been halted.

  • Planned
    June 06, 2023 at 4:00 PM
    Planned
    June 06, 2023 at 4:00 PM

    The OP Mainnet Bedrock Upgrade is expected to run for 2-4 hours. Find all of the details here:
    https://optimism.io/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 2023 to Aug 2023