QuickNode incident

Base Mainnet Block Production Disruption

Minor Resolved View vendor source →

QuickNode experienced a minor incident on June 25, 2026 affecting Mainnet — JSON-RPC API and Mainnet — WebSocket API and 1 more component, lasting 4h 29m. The incident has been resolved; the full update timeline is below.

Started
Jun 25, 2026, 04:07 PM UTC
Resolved
Jun 25, 2026, 08:36 PM UTC
Duration
4h 29m
Detected by Pingoru
Jun 25, 2026, 04:07 PM UTC

Affected components

Mainnet — JSON-RPC APIMainnet — WebSocket APIMainnet —WebhooksMainnet — Streams

Update timeline

  1. investigating Jun 25, 2026, 04:07 PM UTC

    Base Mainnet block production is currently unhealthy during the activation of the Beryl Upgrade. For more information, please refer to the Base status page: https://status.base.org/incidents/5c4gm1wzbjs4

  2. identified Jun 25, 2026, 05:04 PM UTC

    The Base Team has identified the issue with a problematic block interfering with subsequent block building. Their team is working on several threads to remediate. We will provide further updates as the situation develops. For more information, please refer to the Base status page: https://status.base.org/incidents/5c4gm1wzbjs4

  3. identified Jun 25, 2026, 05:28 PM UTC

    The Base team is continuing to debug and have isolated a consensus problem that caused an invalid block to be sequenced. This prevented new blocks from being created following block 47806542. The Base team is working on a fix to resume block propagation to the network while further isolating the root cause of the problematic block. For more information, please refer to the Base status page: https://status.base.org/incidents/5c4gm1wzbjs4

  4. monitoring Jun 25, 2026, 06:46 PM UTC

    A fix has been implemented and we are monitoring the results.

  5. resolved Jun 25, 2026, 08:36 PM UTC

    This incident has been resolved.