Optimism - Notice history

All systems operational

100% - uptime

Public API - Operational

100% - uptime
Jan 2024 · 100.0%Feb · 100.0%Mar · 100.0%

Previous page

Next page

Jan 2024
Feb 2024
Mar 2024

Deposits - Operational

100% - uptime
Jan 2024 · 100.0%Feb · 100.0%Mar · 100.0%

Previous page

Next page

Jan 2024
Feb 2024
Mar 2024

Withdrawals - Operational

100% - uptime
Jan 2024 · 100.0%Feb · 100.0%Mar · 100.0%

Previous page

Next page

Jan 2024
Feb 2024
Mar 2024

Transaction Sequencing - Operational

100% - uptime
Jan 2024 · 100.0%Feb · 99.68%Mar · 100.0%

Previous page

Next page

Jan 2024
Feb 2024
Mar 2024

Batch Submission - Operational

100% - uptime
Jan 2024 · 100.0%Feb · 100.0%Mar · 100.0%

Previous page

Next page

Jan 2024
Feb 2024
Mar 2024

Node Sync - Operational

100% - uptime
Jan 2024 · 100.0%Feb · 99.68%Mar · 100.0%

Previous page

Next page

Jan 2024
Feb 2024
Mar 2024
100% - uptime

Public API - Operational

100% - uptime
Jan 2024 · 100.0%Feb · 100.0%Mar · 100.0%

Previous page

Next page

Jan 2024
Feb 2024
Mar 2024

Deposits - Operational

100% - uptime
Jan 2024 · 100.0%Feb · 100.0%Mar · 100.0%

Previous page

Next page

Jan 2024
Feb 2024
Mar 2024

Withdrawals - Operational

100% - uptime
Jan 2024 · 100.0%Feb · 100.0%Mar · 100.0%

Previous page

Next page

Jan 2024
Feb 2024
Mar 2024

Transaction Sequencing - Operational

100% - uptime
Jan 2024 · 100.0%Feb · 100.0%Mar · 100.0%

Previous page

Next page

Jan 2024
Feb 2024
Mar 2024

Batch Submission - Operational

100% - uptime
Jan 2024 · 100.0%Feb · 100.0%Mar · 100.0%

Previous page

Next page

Jan 2024
Feb 2024
Mar 2024

Node Sync - Operational

100% - uptime
Jan 2024 · 100.0%Feb · 100.0%Mar · 100.0%

Previous page

Next page

Jan 2024
Feb 2024
Mar 2024

Notice history

Mar 2024

No notices reported this month

Feb 2024

OP Mainnet RPC Instability
  • Resolved
    Resolved

    Start time: 4pm Feb 16th PST

    End time: 10:44pm Feb 16th PST

    At 4pm Feb 16th PST we started experiencing downgraded RPC calls on our endpoints. This affected a percentage of traffic to mainnet.optimism.io. Users were still able to transact as long as they retried their requests. The issue was localized to one third-party upstream RPC provider. The rest of the network was not impacted.

    Our team identified the cause of the problem at 10pm Feb 16th PST and started a recovery at 10:10pm. RPC calls should now be operating as expected.

OP Mainnet planned pause (withdraws only)
  • Completed
    February 15, 2024 at 3:01 PM
    Completed
    February 15, 2024 at 3:01 PM

    Withdraws now are unpaused.

  • Update
    February 15, 2024 at 2:01 PM
    In progress
    February 15, 2024 at 2:01 PM

    Withdraws now are paused.

  • In progress
    February 15, 2024 at 2:00 PM
    In progress
    February 15, 2024 at 2:00 PM
    Maintenance is now in progress
  • Planned
    February 15, 2024 at 2:00 PM
    Planned
    February 15, 2024 at 2:00 PM

    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).

Unsafe Head Stall on Mainnet
  • Resolved
    Resolved

    Our team has resolved the unsafe head stall.

    If you're a node operator and your nodes are still stuck, try restarting op-node and op-geth. If you continue to experience an issue, please let us know on Discord.

    This issue was in no way related to tomorrow's planned pause of OP Mainnet.

  • Monitoring
    Monitoring
    The fix has been fully rolled out, and the network is fully operational. We will continue monitoring the situation in case any additional instability is observed. No action is required from users or node operators.
  • Update
    Update
    We are continuing to roll out a potential fix for the unsafe head stall. At this time, the fix has rolled out across our infrastructure and we are waiting for the sequencer to come back online. No action is required from users or node operators. We will continue to update this page.
  • Update
    Update
    We are continuing to roll out a potential fix for the unsafe head stall. At this time no action is required from users or node operators. We will continue to update this page as the fix rolls out.
  • Identified
    Identified
    We have identified a potential root cause of the unsafe head stall. At this time the network is functional, however until the fix is fully rolled out the possibility of continued instability remains. We will continue to update this page as the fix rolls out.
  • Investigating
    Investigating

    We are reopening this incident after reports of additional instability.

  • Resolved
    Resolved
    Our team has resolved the unsafe head stall. If you continue to experience an issue, please let us know on Discord.
  • Monitoring
    Monitoring
    We have observed both the safe and unsafe parts of the chain advancing. At this time the network is fully operational. We will continue monitoring the situation.
  • Identified
    Identified
    We have identified the cause of the unsafe head stall and have applied a fix. At this time node operators may observe a single-block reorg of the unsafe chain. Chain sync should be back to normal at this time.
  • Investigating
    Investigating
    We are investigating reports of an unsafe head stall on OP Mainnet.
OP Goerli Sync Instability
  • Resolved
    Resolved
    This incident has been resolved.
  • Monitoring
    Monitoring
    The fix has been rolled out, and nodes should be able to sync normally.
  • Identified
    Identified
    We have identified an issue with an upstream node provider causing sync instability on OP Goerli. We are rolling out a fix. At this time, node operators may continue to experience slow or unstable sync until the fix is fully deployed.
  • Investigating
    Investigating
    We are investigating reports of slow or unstable syncing on OP Goerli.

Jan 2024

OP Sepolia Planned Pause
  • Completed
    January 23, 2024 at 6:00 PM
    Completed
    January 23, 2024 at 6:00 PM

    Maintenance has completed successfully

  • In progress
    January 23, 2024 at 5:00 PM
    In progress
    January 23, 2024 at 5:00 PM

    Maintenance is now in progress

  • Planned
    January 23, 2024 at 5:00 PM
    Planned
    January 23, 2024 at 5:00 PM

    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.

Degraded Performance on Public Endpoint
  • Resolved
    Resolved

    This incident has been resolved.

  • Monitoring
    Monitoring

    We have transitioned our infrastructure to use a new upstream provider in order to mitigate the degraded performance on the public endpoint. The rollout may take a few minutes to fully take effect. At this time, users should no longer see degraded performance.

  • Investigating
    Investigating

    We are investigating reports of degraded performance on the public endpoint. At this time some users may experience errors querying the chain or submitting new transactions through the public endpoint. To mitigate the issue, we will be switch upstream infrastructure providers. This process may take a few minutes to complete.

Jan 2024 to Mar 2024

Next