Lisk Mainnet Degraded Performance - Stale Data

Incident Report for Quicknode

Resolved

This incident has been resolved.

Posted May 20, 2026 - 13:32 UTC

Identified

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.

Posted May 19, 2026 - 15:28 UTC

Investigating

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.

Posted May 15, 2026 - 15:03 UTC

This incident affected: Lisk (Select Access) (Mainnet — JSON-RPC API, Mainnet — Websockets API, Mainnet — Streams, Mainnet — Webhooks).