Cel2 Status - Notice history

Experiencing partially degraded performance

100% - uptime

Forno - Operational

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

Previous page

Next page

May 2026
Jun 2026
Jul 2026

Block production - Operational

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

Previous page

Next page

May 2026
Jun 2026
Jul 2026

Transaction Sequencing - Operational

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

Previous page

Next page

May 2026
Jun 2026
Jul 2026

Batch submission (safe block progression) - Operational

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

Previous page

Next page

May 2026
Jun 2026
Jul 2026

Block finalization - Operational

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

Previous page

Next page

May 2026
Jun 2026
Jul 2026

Deposits - Operational

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

Previous page

Next page

May 2026
Jun 2026
Jul 2026

Withdraws - Operational

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

Previous page

Next page

May 2026
Jun 2026
Jul 2026

Data Availability Layer (EigenDA) - Operational

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

Previous page

Next page

May 2026
Jun 2026
Jul 2026

Notice history

Jul 2026

No notices reported this month

Jun 2026

Celo Sepolia: Network incident
  • Resolved
    UTC
    Resolved

    Root cause: an operational misconfiguration briefly left two sequencers active at the same time, which produced a competing chain and a large reorg.

    The misconfigured sequencer has been stopped and the affected nodes have been resynced to the canonical chain. Forno endpoints are serving current data again; apps that saw lag or stale reads should now be back to normal, with no action required.

    Note for node operators: nodes running the op-geth client (particularly pruned full nodes) may not rejoin automatically after a deep reorg of this kind. If a node stays stuck, wiping its data directory and letting it re-sync resolves it. We also recommend migrating from op-geth to op-reth (as planned for Today for Celo Sepolia), which recovered from this event automatically without intervention: https://forum.celo.org/t/upcoming-transition-from-op-geth-to-op-reth-on-celo/13448

  • Investigating
    UTC
    Investigating

    Investigating — Celo Sepolia: some RPC endpoints returning stale data

    Posted 2026-06-24

    Impact: Since ~22:00 UTC on June 23, a subset of Celo Sepolia read/RPC nodes fell behind the chain and may have returned stale block, balance, or transaction data. Block production, finalization, and the canonical chain were not affected — the network continued producing and finalizing blocks normally throughout.

    Cause: A misconfigured secondary sequencer briefly produced a competing chain. The network correctly stayed on the canonical chain, but several read-replica nodes followed the orphaned branch and became stuck, unable to automatically rejoin.

    Current status: The misconfigured sequencer has been stopped and the affected read nodes are being resynced from the canonical chain. Writes, block production, and finalization are unaffected. Apps relying on the affected RPC endpoints may see lag or stale reads until resync completes.

    Next update: in ~1 hour, or when resync completes.

May 2026

No notices reported this month

May 2026 to Jul 2026

Next