Unichain - Notice history

All systems operational

Operational

Public RPC - Operational

100% - uptime
Oct 2025 · 99.84%Nov · 99.65%Dec · 99.52%
Oct 2025
Nov 2025
Dec 2025

L2 Block Production - Operational

100% - uptime
Oct 2025 · 99.84%Nov · 100.0%Dec · 99.52%
Oct 2025
Nov 2025
Dec 2025

L1 Batch Posting - Operational

100% - uptime
Oct 2025 · 99.47%Nov · 99.61%Dec · 99.52%
Oct 2025
Nov 2025
Dec 2025

Node Syncing - Operational

100% - uptime
Oct 2025 · 99.84%Nov · 100.0%Dec · 99.52%
Oct 2025
Nov 2025
Dec 2025

Flashblocks Websocket Stream - Operational

100% - uptime
Oct 2025 · 100.0%Nov · 100.0%Dec · 99.52%
Oct 2025
Nov 2025
Dec 2025

Notice history

Dec 2025

Unichain Mainnet: Post-Fusaka Safe Head Stall
  • Postmortem
    Postmortem

    Unichain Mainnet erroneously posted the same batch transaction at two different nonces. This triggered a corner case in the consensus layer client that made it impossible for the L2 Safe Head to progress. OP Labs has a fix available: us-docker.pkg.dev/oplabs-tools-artifacts/images/op-node:v1.16.3. Please upgrade your consensus layer clients on Unichain to use this image until OP Labs provides a newer release.

  • Resolved
    Resolved

    We have identified that the root cause of the safe head stall on Unichain Mainnet is due to a bug in how op-node handles fetching blobs. All nodes operators will need to update their op-node tous-docker.pkg.dev/oplabs-tools-artifacts/images/op-node:e1db990da90a845e1943b1dc20f59e18099db538

  • Monitoring
    Monitoring
    We implemented a fix and are currently monitoring the result.
  • Identified
    Identified

    After working with OP Labs, we have identified both an issue in our batch submission and in the consensus client handling of such a case. We are trying to roll out a new version of the consensus client that fixes this issue.

  • Investigating
    Investigating
    We are currently investigating this incident.

Nov 2025

Oct 2025

Safe head stall and withdrawals delayed on Unichain Mainnet and Sepolia
  • Resolved
    Resolved
    This incident has been resolved.
  • Monitoring
    Monitoring

    We implemented a fix and are currently monitoring the result. The safe head is currently catching up.

  • Update
    Update
    We are continuing to work on a fix for this incident.
  • Update
    Update
    We are continuing to work on a fix for this incident.
  • Identified
    Identified
    We are continuing to work on a fix for this incident.
  • Update
    Update

    Still working on current fix.

  • Monitoring
    Monitoring

    We've identified a fix and are currently deploying and testing it.

  • Identified
    Identified
    We are continuing to work on a fix for this incident.

Oct 2025 to Dec 2025

Next