- Detected by Pingoru
- Mar 30, 2026, 07:31 PM UTC
- Resolved
- Mar 30, 2026, 09:01 PM UTC
- Duration
- 1h 29m
Affected: Gnosis - MainnetGnosis - MainnetMainnet — WebhooksMainnet — Streams
Timeline · 4 updates
-
investigating Mar 30, 2026, 07:31 PM UTC
We are investigating an issue impacting Gnosis (GNO) Mainnet Archive RPC where some requests are returning elevated HTTP 503 errors and may experience degraded availability. The team is actively working to identify the cause and restore normal service. We will follow up with an update by 20:00 UTC.
-
identified Mar 30, 2026, 08:03 PM UTC
Our team has identified the issue with the affected nodes and are currently working on recovery. We will follow up with an update by 20:30 UTC.
-
monitoring Mar 30, 2026, 08:31 PM UTC
A fix has been implemented and we are monitoring the results. We will follow up with an update by 21:00 UTC.
-
resolved Mar 30, 2026, 09:01 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 30, 2026, 11:53 AM UTC
- Resolved
- Mar 30, 2026, 01:30 PM UTC
- Duration
- 1h 37m
Affected: BNB - TestnetTestnet — WebSocket APITestnet — WebhooksTestnet — Streams
Timeline · 2 updates
-
investigating Mar 30, 2026, 11:53 AM UTC
We are currently investigating a block production stall on the Bitcoin Cash (BCH) mainnet. The network appears to have stopped producing new blocks, which is also confirmed by public explorers showing the same block height. We are monitoring the situation closely and will provide updates as they become available.
-
resolved Mar 30, 2026, 07:34 PM UTC
Bitcoin Cash (BCH) mainnet block production has resumed and the network is producing new blocks again. We will continue monitoring for stability.
Read the full incident report →
- Detected by Pingoru
- Mar 26, 2026, 11:47 PM UTC
- Resolved
- Mar 27, 2026, 12:45 AM UTC
- Duration
- 57m
Affected: Bitcoin Cash - TestnetTestnet — StreamsTestnet — Webhooks
Timeline · 2 updates
-
investigating Mar 26, 2026, 11:47 PM UTC
BCH Testnet is experiencing slow block production. We are investigating and will update with more information once it is available.
-
resolved Mar 27, 2026, 12:45 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 25, 2026, 10:29 AM UTC
- Resolved
- Mar 27, 2026, 11:24 AM UTC
- Duration
- 2d
Affected: Sonic - MainnetMainnet — Websockets APIMainnet — StreamsMainnet — Webhooks
Timeline · 4 updates
-
investigating Mar 25, 2026, 10:29 AM UTC
We are currently experiencing service disruptions on Sonic mainnet due to an upstream network-wide block stall. The network is stalled at block 66,026,794. This is a network-wide issue and is not isolated to Quicknode. The Sonic Foundation has been notified. All Sonic mainnet RPC endpoints are currently affected by the upstream network stall. New blocks are not being produced until the network resumes. We will provide the next update by 11:30am or sooner as information becomes available.
-
identified Mar 25, 2026, 01:26 PM UTC
We are currently experiencing service disruptions on Sonic mainnet RPC endpoints due to validator syncing issues. The Sonic team has clarified this is NOT a network stall. The Sonic network remains fully operational, continues to produce blocks, and transactions are processing as expected. The Sonic team has identified the issue and provided a fix requiring client upgrades to v2.1.6 and database resyncing. Our engineering team is actively applying this update to restore service. Sonic mainnet RPC endpoints are currently affected. Customers may experience request failures or timeouts until our nodes complete the upgrade and resync process. The native Sonic explorer remains operational: https://explorer.soniclabs.com/blocks For official updates from Sonic: https://x.com/SonicLabs/status/2036763965041021347 We will provide the next update by 3PM or sooner.
-
identified Mar 25, 2026, 03:48 PM UTC
Our engineering team is actively applying the Sonic client upgrades to v2.1.6 and database resyncing to restore service. Sonic Mainnet RPC endpoints are currently affected. Customers may experience request failures or timeouts until our nodes complete the upgrade and resync process. The native Sonic explorer remains operational: https://explorer.soniclabs.com/blocks For official updates from Sonic: https://x.com/SonicLabs/status/2036763965041021347
-
resolved Mar 27, 2026, 11:24 AM UTC
The issue affecting Sonic mainnet RPC endpoints has been resolved. Our engineering team successfully completed the Sonic client upgrades to v2.1.6 and database resyncing at 00:00 UTC on 27 March. All Sonic mainnet RPC endpoints are now fully operational. If you continue to experience any issues, please contact our support team. https://portal.usepylon.com/quicknode/forms/submit-a-support-ticket
Read the full incident report →
- Detected by Pingoru
- Mar 24, 2026, 04:31 PM UTC
- Resolved
- Mar 24, 2026, 08:40 PM UTC
- Duration
- 4h 9m
Affected: Tron - MainnetMainnet — REST APIMainnet — StreamsMainnet — Webhooks
Timeline · 4 updates
-
investigating Mar 24, 2026, 04:31 PM UTC
The Quicknode team is investigating the degraded performance of Tron Mainnet - we will update this page as we acquire new information. Users may experience 503 errors during this time.
-
investigating Mar 24, 2026, 05:11 PM UTC
We are continuing to investigate degraded performance on Tron Mainnet. At this time, we are seeing elevated 503 errors primarily in the EU region. Traffic is being shifted away from impacted capacity while we work to restore full service. We will share another update by 18:10 UTC (or sooner if there is a significant change).
-
monitoring Mar 24, 2026, 05:30 PM UTC
Our team has deployed a fix to mitigate the 503 errors. Users should now see successful responses when making requests. We are monitoring for stability.
-
resolved Mar 24, 2026, 08:40 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 24, 2026, 09:16 AM UTC
- Resolved
- Mar 25, 2026, 01:53 AM UTC
- Duration
- 16h 36m
Affected: Avalanche - Fuji TestnetFuji — WebSocket APIFuji — WebhooksFuji — Streams
Timeline · 4 updates
-
investigating Mar 24, 2026, 09:16 AM UTC
We are investigating intermittent 503 errors affecting the Avalanche Fuji Testnet. Some customers may experience temporary request failures or degraded performance. Our team is actively working to mitigate the issue and restore full service stability. We will provide an update as more information becomes available.
-
identified Mar 24, 2026, 09:53 AM UTC
We have identified this as an upstream network-wide issue affecting Avalanche Fuji Testnet infrastructure. The C-chain (EVM) is currently affected and blocks have stopped being produced. This is a network-wide issue and is not isolated to Quicknode. The Avalanche team has been notified and is investigating. All Avalanche Fuji Testnet RPC endpoints are currently affected. Customers may experience 503 errors, request failures, or timeouts until the network stabilizes. We will provide the next update by 11am or sooner as information becomes available.
-
monitoring Mar 24, 2026, 02:55 PM UTC
The upstream network issue has stabilized and blocks are now being produced. Our team is actively monitoring to ensure full service restoration. Customers should see improved performance, though some intermittent issues may still occur until all nodes are fully synchronized.
-
resolved Mar 25, 2026, 01:53 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 24, 2026, 02:45 AM UTC
- Resolved
- Mar 24, 2026, 03:20 AM UTC
- Duration
- 35m
Affected: BNB - TestnetTestnet — WebSocket APITestnet — WebhooksTestnet — Streams
Timeline · 4 updates
-
investigating Mar 24, 2026, 03:02 AM UTC
We have detected an issue on the BSC-Testnet Archive, due to which you would be seeing 503 errors. Our team is currently looking into it and will fix the situation as soon as possible.
-
identified Mar 24, 2026, 03:20 AM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Mar 24, 2026, 03:20 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Mar 24, 2026, 03:20 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 23, 2026, 11:45 PM UTC
- Resolved
- Mar 25, 2026, 12:33 AM UTC
- Duration
- 1d
Affected: Mantle - SepoliaSepolia — Websockets APISepolia — StreamsSepolia — Webhooks
Timeline · 2 updates
-
investigating Mar 23, 2026, 11:45 PM UTC
We are investigating intermittent 503 errors affecting the Mantle Sepolia Testnet. Some customers may experience temporary request failures or degraded performance. Our team is actively working to mitigate the issue and restore full service stability. We will provide an update as more information becomes available.
-
resolved Mar 25, 2026, 12:33 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 23, 2026, 05:17 PM UTC
- Resolved
- Mar 23, 2026, 10:20 PM UTC
- Duration
- 5h 3m
Affected: Arbitrum - SepoliaSepolia - WebSocket APISepolia — WebhooksSepolia — Streams
Timeline · 3 updates
-
investigating Mar 23, 2026, 05:17 PM UTC
We are investigating reports that Arbitrum Sepolia is stalled at block height 252,909,123 and may not be progressing normally. The Arbitrum foundation team is actively looking into the issue, and we are monitoring closely while coordinating updates. Customers may see stale “latest block” data until block production resumes.
-
monitoring Mar 23, 2026, 10:10 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Mar 23, 2026, 10:20 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 23, 2026, 01:10 PM UTC
- Resolved
- Mar 23, 2026, 10:04 PM UTC
- Duration
- 8h 54m
Affected: Peaq - MainnetMainnet — Websockets APIMainnet — StreamsMainnet — Webhooks
Timeline · 2 updates
-
investigating Mar 23, 2026, 01:10 PM UTC
We are currently investigating a block production stall on Peaq Mainnet. The same issue is reflected on the public block explorer, confirming this is a network-level incident. The Peaq Foundation has acknowledged the issue and is actively working on a resolution. We will provide further updates as they become available.
-
resolved Mar 23, 2026, 10:04 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 22, 2026, 09:04 PM UTC
- Resolved
- Mar 23, 2026, 06:46 PM UTC
- Duration
- 21h 41m
Affected: 0g - Mainnet0G Mainnet — WebSocket API0G Mainnet — Streams0G Mainnet — Webhooks
Timeline · 2 updates
-
investigating Mar 22, 2026, 09:04 PM UTC
The 0G Mainnet network appears to have stalled at block 28080128 - The Quicknode team is investigating and has reached out to the foundation for further information. This issue is network wide and is not isolated to Quicknode. We will update with more information once it is available.
-
resolved Mar 23, 2026, 06:46 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 22, 2026, 09:29 AM UTC
- Resolved
- Mar 23, 2026, 06:40 PM UTC
- Duration
- 1d 9h
Affected: Sei - Pacific-1 MainnetPacific-1 Mainnet — Tendermint JSON-RPC/REST APIPacific-1 Mainnet — Cosmos REST APIPacific-1 Mainnet — Websockets APIPacific-1 Mainnet — StreamsPacific-1 Mainnet — Webhooks
Timeline · 7 updates
-
investigating Mar 22, 2026, 09:29 AM UTC
We are currently experiencing service disruptions on Sei mainnet due to an upstream network-wide issue causing block stalls and elevated latency. This is a network-wide issue and is not isolated to Quicknode. All Sei mainnet RPC endpoints are currently affected. Customers may experience slower response times and blocks are not being produced consistently until the network stabilizes. We will provide the next update by 11AM or sooner as information becomes available.
-
investigating Mar 22, 2026, 01:03 PM UTC
The Sei Foundation has informed us that they are actively investigating this issue further. Customers may still experience slower response times. We will provide the next update by 2PM UTC or sooner as information becomes available.
-
monitoring Mar 22, 2026, 03:32 PM UTC
Block production has resumed, and the network stall appears resolved. Customers may continue to experience elevated latency on Sei Mainnet requests, particularly for heavy/debug methods. We are continuing to monitor
-
monitoring Mar 22, 2026, 05:49 PM UTC
Sei Mainnet has recovered and block production is stable. The upstream network stall impacting Sei Mainnet has been resolved.
-
monitoring Mar 22, 2026, 08:30 PM UTC
Our team is currently working on the ongoing latency being reported on the Sei Pacific network. A potential fix has been pushed and we are monitoring for stability. The next update will be at 21:00 UTC.
-
monitoring Mar 22, 2026, 09:23 PM UTC
Our team is continuing to monitor for stability on our Sei infrastructure following the fixes pushed by our engineers. Customers should now be experiencing decreases in their latency.
-
resolved Mar 23, 2026, 06:40 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 22, 2026, 07:13 AM UTC
- Resolved
- Mar 23, 2026, 02:20 AM UTC
- Duration
- 19h 6m
Affected: Hemi - TestnetTestnet — Websockets APITestnet — StreamsTestnet — Webhooks
Timeline · 2 updates
-
investigating Mar 22, 2026, 07:13 AM UTC
Hemi Testnet appears to have stalled at block 5,503,922. This is a chain-wide stall. Quicknode teams are actively working with the Foundation to restore normal block progression. We will provide an update as more information becomes available.
-
resolved Mar 23, 2026, 02:20 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 22, 2026, 06:44 AM UTC
- Resolved
- Mar 23, 2026, 09:57 PM UTC
- Duration
- 1d 15h
Affected: Blast - SepoliaSepolia — WebSocket APISepolia — WebhooksSepolia — Streams
Timeline · 2 updates
-
investigating Mar 22, 2026, 06:44 AM UTC
Blast Sepolia appears to have stalled at block 34,714,475. This is a chain-wide stall. Quicknode teams are actively working with the Foundation to restore normal block progression. We will provide an update as more information becomes available.
-
resolved Mar 23, 2026, 09:57 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 22, 2026, 05:40 AM UTC
- Resolved
- Mar 22, 2026, 05:45 PM UTC
- Duration
- 12h 4m
Affected: Ethereum - SepoliaSepolia — Websockets APISepolia Beacon — REST APISepolia — WebhooksSepolia — Streams
Timeline · 4 updates
-
investigating Mar 22, 2026, 05:40 AM UTC
We are investigating intermittent 503 errors affecting the Ethereum Sepolia Testnet. Some customers may experience temporary request failures or degraded performance. Our team is actively working to mitigate the issue and restore full service stability. We will provide an update as more information becomes available.
-
identified Mar 22, 2026, 06:19 AM UTC
Quicknode teams have identified the issue and are actively working to restore nodes. The next update will be provided before 08:00 AM UTC or sooner.
-
monitoring Mar 22, 2026, 08:03 AM UTC
Some nodes have recovered, and 503s have been mitigated. Quicknode teams are continuing to work to recover full capacity and monitor performance to ensure stability. We will provide the next update before 14:00 UTC or sooner.
-
resolved Mar 22, 2026, 05:45 PM UTC
This incident has now been resolved, and nodes have recovered.
Read the full incident report →
- Detected by Pingoru
- Mar 20, 2026, 07:40 PM UTC
- Resolved
- Mar 20, 2026, 10:12 PM UTC
- Duration
- 2h 31m
Affected: Starknet - SepoliaSepolia — Websockets API
Timeline · 2 updates
-
identified Mar 20, 2026, 08:38 PM UTC
We are currently aware of a network-wide issue affecting Starknet Testnet (Sepolia), where block production has significantly slowed down. This is a broader infrastructure issue being handled by the Starknet Foundation. We are actively monitoring the situation and will provide updates as new information becomes available. Starknet Status Page: https://status.starknet.io/incidents/896s468434dk
-
resolved Mar 21, 2026, 01:46 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 19, 2026, 08:26 PM UTC
- Resolved
- Mar 19, 2026, 08:33 PM UTC
- Duration
- 7m
Affected: Abstract - MainnetMainnet — WebSocket APIMainnet — Webhooks
Timeline · 2 updates
-
investigating Mar 19, 2026, 08:26 PM UTC
Abstract Mainnet has stalled network-wide at block 46,887,372. New blocks are not being produced until the network resumes. Network Explorer: https://explorer.mainnet.abs.xyz/
-
resolved Mar 19, 2026, 08:33 PM UTC
Network block production has resumed and our nodes are operating at tip.
Read the full incident report →
- Detected by Pingoru
- Mar 19, 2026, 11:41 AM UTC
- Resolved
- Mar 19, 2026, 04:53 PM UTC
- Duration
- 5h 11m
Affected: Base - MainnetMainnet — WebSocket APIMainnet —WebhooksMainnet — Streams
Timeline · 3 updates
-
investigating Mar 19, 2026, 11:41 AM UTC
We are currently investigating reports of degraded performance affecting Base endpoints. Users may experience elevated latencies and 503 errors when interacting with Base. We are actively investigating the root cause and are in contact with the Base Foundation. We will provide further updates as the situation develops.
-
monitoring Mar 19, 2026, 12:52 PM UTC
The root cause has been identified and a fix has been applied. Affected nodes are currently syncing and catching up. We are continuing to monitor the situation closely and will update this page once full stability is confirmed. We apologize for the inconvenience and thank you for your patience.
-
resolved Mar 19, 2026, 04:53 PM UTC
This incident has been resolved. A problematic block triggered degradation across affected nodes. The root cause has been identified and addressed, and all nodes are now fully synced and operating normally.
Read the full incident report →
- Detected by Pingoru
- Mar 19, 2026, 12:30 AM UTC
- Resolved
- Mar 19, 2026, 06:41 AM UTC
- Duration
- 6h 11m
Affected: Quicknode Token API
Timeline · 2 updates
-
investigating Mar 19, 2026, 04:18 AM UTC
The QuickNode team is investigating the degraded performance of qn_estimatePriorityFees. We will update this page as we acquire new information.
-
resolved Mar 19, 2026, 06:41 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 18, 2026, 11:31 AM UTC
- Resolved
- Mar 18, 2026, 12:13 PM UTC
- Duration
- 41m
Affected: ZKsync - MainnetAbstract - MainnetMainnet — Websockets APIMainnet — WebSocket APIMainnet — StreamsMainnet — WebhooksMainnet — WebhooksAbstract - TestnetTestnet — WebSocket APITestnet — Webhooks
Timeline · 2 updates
-
investigating Mar 18, 2026, 11:31 AM UTC
We are currently aware of a disruption affecting Abstract Mainnet and zkSync Era endpoints. Block height was stalled and requests may be impacted. The ZKsync Foundation has identified the issue and confirmed services should be restored soon. We are actively monitoring and will provide updates as the situation develops.
-
resolved Mar 18, 2026, 12:13 PM UTC
Block production has resumed on both Abstract Mainnet/Testnet and zkSync Era. Endpoints are operating normally and requests should be processing as expected. We will continue to monitor for any residual impact or instability.
Read the full incident report →
- Detected by Pingoru
- Mar 18, 2026, 03:00 AM UTC
- Resolved
- Mar 18, 2026, 05:00 AM UTC
- Duration
- 1h 59m
Affected: Base - MainnetMainnet — WebSocket APIMainnet —WebhooksMainnet — Streams
Timeline · 4 updates
-
investigating Mar 18, 2026, 02:24 AM UTC
We are currently investigating this issue.
-
investigating Mar 18, 2026, 02:38 AM UTC
We are continuing to investigate this issue.
-
monitoring Mar 18, 2026, 03:18 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Mar 18, 2026, 05:24 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 17, 2026, 07:11 PM UTC
- Resolved
- Mar 18, 2026, 12:12 AM UTC
- Duration
- 5h
Affected: Quicknode FaucetSingle Flight RPCQuicknode StreamsQuicknode FunctionsQuicknode WebhooksQuickNode Dashboard
Timeline · 9 updates
Read the full incident report →
- Detected by Pingoru
- Mar 12, 2026, 09:59 PM UTC
- Resolved
- Mar 16, 2026, 08:34 PM UTC
- Duration
- 3d 22h
Affected: Ethereum - SepoliaSepolia — Websockets APISepolia — WebhooksSepolia — Streams
Timeline · 2 updates
-
identified Mar 12, 2026, 09:59 PM UTC
We're currently seeing degraded performance on Ethereum Sepolia in the APAC region. Our engineering team is actively working to restore node health.
-
resolved Mar 16, 2026, 08:34 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 12, 2026, 05:23 PM UTC
- Resolved
- Mar 15, 2026, 06:23 PM UTC
- Duration
- 3d
Affected: Solana - MainnetMainnet — Websockets APIMainnet — StreamsMainnet — Webhooks
Timeline · 2 updates
-
investigating Mar 12, 2026, 05:23 PM UTC
The Quicknode team is investigating the degraded performance of the gRPC API on Solana Mainnet affecting all regions - we will update this page as we acquire new information. Users may experience 503 errors, and timeouts during this time.
-
resolved Mar 15, 2026, 06:23 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 11, 2026, 09:51 AM UTC
- Resolved
- Mar 11, 2026, 10:48 AM UTC
- Duration
- 57m
Affected: Cyber - MainnetMainnet - Websockets APIMainnet — StreamsMainnet — Webhooks
Read the full incident report →