Loading
Applying language and content...
Loading status page
Checking service and reports...
52 Quicknode incidents · 2026年6月 — official updates, affected components, duration and resolution details.
Vana Mainnet はブロック 9228400 で固定されているようです。 Quicknodeチームは調査を行い、利用可能な情報を更新します.
当社のエンジニアは、ノードインフラストラクチャを復元するための基盤と密接に連携しています.
修正を実装し、結果を監視しています.
公式のインシデント更新を自動翻訳しています。
The Quicknode team is investigating the degraded performance of Blast Mainnet - we will update this page as we acquire new information.
A fix has been applied to mitigate the degraded performance on Blast Mainnet. We are monitoring the situation and will provide further updates as needed.
The degraded performance affecting Blast Mainnet has been resolved. All systems are operating normally.
公式のインシデント更新を自動翻訳しています。
We are investigating an issue with BSC Testnet that is causing 503 errors. We will update this page as we acquire new information.
The issue has been identified and a fix is being implemented.
A fix has been identified using bsc-reth v0.1.0-fix, which resolves the stuck block issue at block 118,130,132. Nodes are being upgraded and are processing normally. We are monitoring BSC Testnet for continued stability.
The issue affecting BSC Testnet has been resolved. A fix was deployed using the updated bsc-reth v0.1.0-fix image, which addressed the stuck block at 118,130,133. All nodes are processing normally. We will continue to monitor for stability.
公式のインシデント更新を自動翻訳しています。
We are investigating an increase in 503 errors affecting HyperEVM in the NRT (Tokyo) region. Users in this region may experience failed or degraded requests. We will provide updates as our investigation progresses.
Additional backend nodes have been added to the NRT region. We are monitoring the situation to confirm stability and will provide further updates as needed.
This incident has been resolved.
公式のインシデント更新を自動翻訳しています。
Berachain Mainnet appears to have stalled at block 23,259,488. The QuickNode team is investigating and will update with more information once it is available.
Our engineers have successfully unwound the affected nodes past the stalled block and syncing has resumed. We are monitoring Berachain Mainnet for continued stability and will provide further updates as needed.
This incident has been resolved.
公式のインシデント更新を自動翻訳しています。
We are investigating elevated 503 errors affecting our US-East region. Multiple chains may be impacted. Our team is actively investigating and will provide updates as more information becomes available.
We have identified the root cause of the elevated 503 errors in the US-East region. Our engineers are actively working on recovery. We will continue to monitor and provide updates as the situation progresses.
The elevated errors affecting chains in the US-Region has been addressed. Our team is monitoring for stability.
This incident has been resolved.
公式のインシデント更新を自動翻訳しています。
Optimism Mainnet appears to have stalled at block 153924191. The Quicknode team is investigating and will update this page as more information becomes available.
Optimism Mainnet block height is advancing again. We are monitoring the network for continued stability and will provide further updates if needed. https://status.optimism.io/cmrazrvph0am30rns9tzwb2oa
The Optimism Mainnet network stall at block 153924191 has been resolved. The network is advancing normally. We will continue to monitor for stability. https://status.optimism.io/cmrazrvph0am30rns9tzwb2oa
公式のインシデント更新を自動翻訳しています。
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
公式のインシデント更新を自動翻訳しています。
The Quicknode team is investigating the degraded performance in the US-EAST region. You may see increased error rates, response times, or timeouts while we work to resolve this. We will provide an update as more information becomes available.
The Quicknode team has identified the degraded performance issue in the US-EAST region. This issue should have been mitigated. We are actively monitoring this and will provide an update as we acquire new information.
The degraded performance issue has been mitigated. The Quicknode team is continuing to monitor performance to ensure stability.
This incident has been resolved.
公式のインシデント更新を自動翻訳しています。
We are investigating stale block data being served from the Blockbook service, specifically for `bb_getblock`. Our team will update this page as more information becomes available to us.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
公式のインシデント更新を自動翻訳しています。
Abstract Testnet appears to have stalled at block 18,145,825. The QuickNode team is investigating and will update with more information once it is available.
This incident has been resolved.
Abstract Mainnet appears to have stalled at block 72,953,577. Matter Labs is currently performing database maintenance. The Quicknode team will update with more information once it is available.
This incident has been resolved.
Mantle Sepolia appears to have stalled at block 40763249. The QuickNode team is investigating and has notified the Mantle Foundation. We will update this page as we acquire new information.
The Mantle Sepolia network stall has been resolved. Block production has resumed and the network is operating normally. We will continue to monitor for stability.
The Quicknode team is investigating the degraded performance of Tempo Testnet - we will update this page as we acquire new information.
We have identified the root cause of the degraded performance on Tempo Testnet. All affected nodes are being recovered via a cross-region copy. We will post another update once recovery is complete.
All affected nodes have been recovered and services are operating normally. We are monitoring Tempo Testnet for stability ahead of a planned stress test at 22:00 UTC. We will continue to provide updates as needed.
This incident has been resolved.
The QuickNode team is investigating the degraded performance of TON Mainnet API. Some users many experience 503s at this time. We will update this page as we acquire new information.
This incident has been resolved.
Flow Testnet EVM (JSON-RPC API) nodes stalled at block height 118,361,371. Our team is actively investigating and will provide an update once more information becomes available.
This incident has been resolved.
The Quicknode team is investigating the degraded performance of Ethereum Hoodi Testnet. Some users may experience 503 errors at this time. We will update this page as we acquire new information.
The Quicknode team has identified the root cause of the recent degradation affecting the Ethereum Hoodi nodes. Currently, the historical blob data for Ethereum Hoodi nodes is limited to slots >= 3,375,000. Requests for blob data prior to this slot may be temporarily unavailable. We are working on restoring complete historical blob coverage and will keep this page updated as the work progresses.
We are investigating an issue with Hedera Testnet resulting in elevated 503 errors. Users may experience failed or interrupted requests. Our team is actively investigating and will provide updates as more information becomes available.
We have identified the root cause of the elevated 503 errors on Hedera Testnet. The issue was caused by rate limiting (429s) on an upstream node. The affected node has been addressed and service has been restored. We are monitoring for continued stability.
This incident has been resolved.
Base Mainnet is experiencing a chain-wide stall. The Quicknode team is investigating and will update this page as more information becomes available. For reference, please see the Base status page: https://status.base.org/incidents/5c4gm1wzbjs4
Nodes have been restarted and the chain stall has been resolved. 503 errors are no longer observed. We are monitoring the service for continued stability as backfill requests normalize.
This incident has been resolved.
We are currently performing maintenance and an upgrade on HyperEVM and Hypercore gRPC. Users may experience disruptions during this time. We will provide updates as the work progresses.
The HyperEVM and Hypercore maintenance / upgrade has been completed. All systems are operating normally.