Unichain - Notice history

All systems operational

Operational

Public RPC - Operational

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

Previous page

Next page

Oct 2025
Nov 2025
Dec 2025

L2 Block Production - Operational

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

Previous page

Next page

Oct 2025
Nov 2025
Dec 2025

L1 Batch Posting - Operational

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

Previous page

Next page

Oct 2025
Nov 2025
Dec 2025

Node Syncing - Operational

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

Previous page

Next page

Oct 2025
Nov 2025
Dec 2025

Flashblocks Websocket Stream - Operational

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

Previous page

Next page

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

Unichain - L2 Batches are not being submitted to L1
  • Resolved
    Resolved
    This incident has been resolved.
  • Identified
    Identified

    We have identified an upstream issue with our TEE signers that has made batch posting functionality flaky.

  • Investigating
    Investigating
    We are currently investigating this incident.
Unichain Mainnet: Transactions are not being included in new blocks
  • Resolved
    Resolved

    This incident has been resolved. An upgrade to the TEE builder had a poor interaction with our proxy, leading to transactions not being submitted properly.

  • Identified
    Identified

    Many users are reporting that their swaps and transactions are stuck. We have identified an issue with Unichain's proxy where it is not forwarding transactions to our TEE builder.

  • Investigating
    Investigating

    We have noticed that many transactions are getting stuck within Unichain Mainnet's mempool and are subsequently not being added to newly produced blocks. This means user swaps and regular transactions are not being submitted to the chain.

Unichain Mainnet Safe Head Stall
  • Resolved
    Resolved
    This incident has been resolved.
  • Update
    Update

    We've identified a fix and are rolling it out. Some rollup nodes are starting to recover on mainnet already.

  • Monitoring
    Monitoring

    We are posting batches, but our internal beacon chain RPC is having issues. Internal rollup nodes are unable to derive from L1, but the safe head is being advanced on-chain.

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

Oct 2025

Safe head stall and withdrawals delayed on Unichain Mainnet and Sepolia
  • Postmortem
    Postmortem

    https://uniswaplabs.notion.site/Public-Postmortem-Unichain-Mainnet-and-Sepolia-Safe-Head-Stall-Withdrawal-Delay-28dc52b2548b802c89b7cb36af3e16e5

  • 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