QuickNode Status

Resolved: This incident has been resolved.

Monitoring: A fix has been implemented for the Story mainnet block height stall at block 20,818,218, and we are monitoring the results. We will provide another update once we confirm the network is stable.

Investigating: We are currently investigating an issue where Story mainnet has stalled at block height 20,818,218. We'll provide an update as soon as we have more information.

Resolved: Sui has officially marked JSON-RPC as deprecated and is requiring developers to migrate to either gRPC or GraphQL RPC by July 2026. You can read more in Sui's blogs below: https://docs.sui.io/develop/accessing-data/data-serving https://docs.sui.io/develop/accessing-data/json-rpc-migration

The good news: Quicknode has you covered with support of both gRPC and GraphQL for Sui, and we've just made gRPC even more accessible with two new additions:

• gRPC-web transport support - enabling browser-based clients to connect seamlessly over port 443
• gRPC traffic now served over port 443 - simplifying firewall and infrastructure configuration

If you need help getting started with gRPC or GraphQL on Quicknode, please check out our docs: https://www.quicknode.com/docs/sui

Monitoring: Sui has officially marked JSON-RPC as deprecated and is requiring developers to migrate to either gRPC or GraphQL RPC by July 2026. You can read more in Sui's blogs below: https://docs.sui.io/develop/accessing-data/data-serving https://docs.sui.io/develop/accessing-data/json-rpc-migration

The good news: Quicknode has you covered with support of both gRPC and GraphQL for Sui, and we've just made gRPC even more accessible with two new additions:

• gRPC-web transport support  - enabling browser-based clients to connect seamlessly over port 443
• gRPC traffic now served over port 443 - simplifying firewall and infrastructure configuration

If you need help getting started with gRPC or GraphQL on Quicknode, please check out our docs: https://www.quicknode.com/docs/sui

Resolved: This incident has been resolved.

Monitoring: The intermittent 503s on Solana Mainnet have resolved. The AMS, FRA, SIN, and NRT regions observed the intermittent 503s. We are monitoring for stability.

Investigating: The Quicknode team is investigating the degraded performance of Solana Mainnet - we will update this page as we acquire new information.

Resolved: This incident has been resolved.

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

Identified: The issue has been identified and a fix is being implemented.

Investigating: We are currently investigating this issue.

Resolved: This incident has been resolved.

Investigating: Our team is actively in discussion with the foundation to address the prolonged 503s on Polygon Amoy Testnet. You may continue to experience 503 errors and timeouts. We will provide updates as more information becomes available.

Investigating: We're currently investigating prolonged 503s on Polygon Amoy Testnet following the conclusion of Polygon's scheduled stress test. You may continue to experience 503 errors and timeouts. We will provide updates as more information becomes available.

Investigating: Polygon Labs is running load/stress testing on Amoy Testnet starting at 12:00 PM UTC today. You may experience higher-than-usual latency or elevated network load during this window. No action is needed on your end, we're monitoring and will update this page if anything requires attention.

Resolved: This issue has been resolved.

Monitoring: All regions remain healthy and will continue to monitor.

Monitoring: All regions remain healthy and will continue to monitor.

Monitoring: The foundation feed disconnected and caused our backends to lag and has since recovered.

Investigating: The Quicknode team is currently investigating degraded performance on Robinhood Mainnet.

Resolved: This incident has been resolved.

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

Investigating: The Quicknode team is investigating the degraded performance of Solana Mainnet gRPC in the JFK region - we will update this page as we acquire new information.

Resolved: This incident has been resolved.

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

Identified: The issue has been identified and a fix is being implemented.

Investigating: Our team is investigating degradation on Sui Mainnet archive nodes.

Resolved: This incident has been resolved. Hyperliquid Testnet is operating normally.

Investigating: We've identified this as an upstream issue with Hyperliquid Testnet and are waiting on a fix from the Hyperliquid team. We'll update this page as soon as we have more information.