Base incident

Safe head delay from high transaction volume

Major Resolved View vendor source →

Base experienced a major incident on October 10, 2025 affecting Batch submission, lasting 2h 54m. The incident has been resolved; the full update timeline is below.

Started
Oct 10, 2025, 09:40 PM UTC
Resolved
Oct 11, 2025, 12:35 AM UTC
Duration
2h 54m
Detected by Pingoru
Oct 10, 2025, 09:40 PM UTC

Affected components

Batch submission

Update timeline

  1. identified Oct 10, 2025, 09:40 PM UTC

    Heavy transaction volume on Base L2 is causing delays in batching data to Ethereum. Node operators may experience node client syncing delays and applications on Base may notice a lagging safe head. Block building (unsafe head) continues to function normally.

  2. identified Oct 10, 2025, 10:54 PM UTC

    The safe head is still lagging behind, and the Base sequencing is currently limiting the amount of calldata it can include in L2 blocks. This is to ensure the safe head can progress on L1. Users may experience delays in transaction inclusion, and potentially a high rate of transaction drops.

  3. resolved Oct 11, 2025, 12:35 AM UTC

    This incident has been resolved. Base chain is functioning properly.