QuickNode incident

Lisk Mainnet Degraded Performance - Stale Data

Minor Resolved View vendor source →

QuickNode experienced a minor incident on May 15, 2026 affecting Mainnet — JSON-RPC API and Mainnet — Websockets API and 1 more component, lasting 4d 22h. The incident has been resolved; the full update timeline is below.

Started
May 15, 2026, 03:03 PM UTC
Resolved
May 20, 2026, 01:32 PM UTC
Duration
4d 22h
Detected by Pingoru
May 15, 2026, 03:03 PM UTC

Affected components

Mainnet — JSON-RPC APIMainnet — Websockets APIMainnet — StreamsMainnet — Webhooks

Update timeline

  1. investigating May 15, 2026, 03:03 PM UTC

    The QuickNode team is investigating degraded performance of Lisk Mainnet - customers may experience stale data on block-dependent calls (e.g. eth_blockNumber) while archive nodes catch up to chain head. We will update this page as we acquire new information.

  2. identified May 19, 2026, 03:28 PM UTC

    The Quicknode team is continuing to address the degraded performance of Lisk Mainnet and we are working with the foundation to resolve the issue. Customers may continue to experience stale data on block-dependent calls (e.g. eth_blockNumber) while archive nodes catch up to chain head. We will update this page as we acquire new information.

  3. resolved May 20, 2026, 01:32 PM UTC

    This incident has been resolved.