QuickNode Status

Resolved: This incident has been resolved.

Monitoring: We have replaced the affected backend infrastructure. Latency and timeouts on select RPC methods on Robinhood Mainnet have returned to normal, and affected Streams have caught up. We are continuing to monitor.

Identified: We have identified the root cause of the increased latency and timeouts affecting Robinhood Mainnet on select methods, including debug_traceBlockByNumber, eth_getBlockReceipts, eth_getLogs, and eth_getBlockByNumber. Our engineers have disabled the affected backends and are actively working to restore full service. Some stream-based services may continue to experience delays as they catch up. We will provide another update as the situation progresses.

Investigating: The Quicknode team is investigating degraded performance of Robinhood Mainnet - we are seeing increased latency and timeouts on select RPC methods. We will update this page as we acquire new information.

Resolved: The issue affecting our API authentication has been resolved. The incident was limited to a small number accounts. All services, including Quicknode Streams, KV Store, and Webhooks, are operating normally.

Investigating: We are investigating an issue with our internal Quicknode API that is causing authentication failures for multiple accounts. Quicknode Streams, KV Store REST API, and Webhooks are currently affected. We will update this page as we acquire new information.