Degraded Performance - Solana Mainnet

Incident Report for QuickNode

Resolved

This incident has been resolved.
Posted Feb 14, 2025 - 21:51 UTC

Monitoring

A fix has been implemented and we are monitoring the results.
Posted Feb 05, 2025 - 20:09 UTC

Identified

Our team is actively working to mitigate an increase in 503s on the network.
Posted Feb 04, 2025 - 23:33 UTC

Update

We are pleased to inform you that all backends have been successfully upgraded, and the issue with 503 errors has been significantly improved.

We appreciate your patience and cooperation, and we will continue working closely with the foundation to resolve the identified bugs.

Once the issue has been fully resolved, we will increase the rate limits. Thank you for your understanding.
Posted Jan 29, 2025 - 14:28 UTC

Update

We are continuing to monitor for any further issues.
Posted Jan 29, 2025 - 14:25 UTC

Update

We have isolated the issue specifically in the US region. The EU and APAC regions are functioning normally.

The getSignatureStatuses method is currently restricted to a maximum of 10 requests per second until the issue is fully resolved.

Users may still experience intermittent 503 errors in the US region when using the following methods: getFirstAvailableBlock, getSignatureStatuses, getSignaturesForAddress, getBlocksWithLimit, getBlocks, and getInflationReward.
Posted Jan 25, 2025 - 01:12 UTC

Update

intermittent 503s on getSignaturesforaddress; method limited to 100rps until further notice
Posted Jan 23, 2025 - 20:10 UTC

Monitoring

A fix has been implemented and we are monitoring the results.
Posted Jan 22, 2025 - 23:33 UTC

Investigating

The QuickNode team is investigating the degraded performance of Solana Mainnet - we will update this page as we acquire new information.
Posted Jan 22, 2025 - 22:28 UTC
This incident affected: Solana (Mainnet — JSON-RPC API, Mainnet — Websockets API).