Unichain - Notice history

All systems operational

Operational

Public RPC - Operational

100% - uptime
May 2025 · 100.0%Jun · 100.0%Jul · 100.0%

Previous page

Next page

May 2025
Jun 2025
Jul 2025

L2 Block Production - Operational

100% - uptime
May 2025 · 100.0%Jun · 100.0%Jul · 100.0%

Previous page

Next page

May 2025
Jun 2025
Jul 2025

L1 Batch Posting - Operational

100% - uptime
May 2025 · 100.0%Jun · 100.0%Jul · 100.0%

Previous page

Next page

May 2025
Jun 2025
Jul 2025

Node Syncing - Operational

100% - uptime
May 2025 · 100.0%Jun · 100.0%Jul · 100.0%

Previous page

Next page

May 2025
Jun 2025
Jul 2025

Notice history

Jul 2025

No notices reported this month

Jun 2025

Unichain Mainnet Unsafe Head Stall
  • Resolved
    Resolved

    Active sequencer is restarted and unsafe head is progressing.

  • Identified
    Identified

    Unichain Mainnet sequencer stalled for almost 10 minutes during planned maintenance period.

May 2025

Unichain Infrastructure upgrade
  • Completed
    May 23, 2025 at 3:29 PM
    Completed
    May 23, 2025 at 3:29 PM
    Maintenance has completed successfully.
  • Update
    May 22, 2025 at 10:49 PM
    In progress
    May 22, 2025 at 10:49 PM

    Maintenance is taking longer than estimated. Unichain Sepolia is almost finished upgrading the fleet and Unichain Mainnet is pending. The Maintenance period will be increased by 2 hours.

  • In progress
    May 22, 2025 at 8:33 PM
    In progress
    May 22, 2025 at 8:33 PM

    We are upgrading the machines running our various rollup nodes to be able to handle Unichain's growth for the foreseeable future. We do not expect any outages or downtime in this period, but large upgrades such as this can have impact on chain performance if something goes wrong.

Unichain Sepolia - Safe Head is stalled due to L1 Batcher Degradation
  • Resolved
    Resolved

    All systems are operational and L1 batches for all transactions over the incident period have been submitted to the L1.

  • Monitoring
    Monitoring

    L1 Batches are being regularly posted now and the backlog of L2 transactions is being reduced.

  • Identified
    Identified

    The infrastructure supporting the L1 Batcher has began OOM'ing. Engineers have identified a fix and are deploying it, currently.

May 2025 to Jul 2025

Next