QuickNode Status

Investigating: Sui Mainnet appears to have stalled at block 234,608,191 The QuickNode team is investigating with the SUI Chain Team and will update with more information once it is available.

Investigating: We are currently investigating an issue affecting Ink network. Block production is stalled at block height 34,900,022.

Our engineering team is actively working to restore service.

We will provide updates as we have more information.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to work on a fix for this issue.

Identified: We are performing a mandatory security upgrade across all Ethereum networks. The update addresses a security issue on the peering networking on the Geth client.

No downtime is expected, but customers may experience brief connection interruptions and a small number of HTTP 503 responses as services restart and resynchronize with the network.

Geth: Moisture Filters (v1.16.8) https://github.com/ethereum/go-ethereum/releases/tag/v1.16.8

Resolved: This incident has been resolved.

Monitoring: Blocks are syncing on the Blast Sepolia Network. We are monitoring performance to ensure stability and will provide an update upon confirmation or if further action is required within 10 minutes.

Investigating: The Blast Sepolia Network is experiencing intermittent block stalls - The Quicknode team is investigating and will update with more information once it is available.

Resolved: This incident has been resolved.

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

Identified: As per the foundation recommendation, our engineers are deploying the fix version across the Polygon mainnet archive node infrastructure. As our engineers work towards a resolution, please find the next update on or before 6:00 UTC

Investigating: Our team is working alongside the Polygon Foundation to address a network-wide issue affecting archive nodes.

Customers may experience increased error rates, including 503 responses, along with failed or timing-out requests when querying historical (archive) data. This behavior is expected until a solution is provided by the Foundation.

Standard (non-archive) Polygon endpoints are not affected at this time, and our team is actively working to restore archive capacity and mitigate customer impact.

The Quicknode Support team will update this status by 3:00 UTC.

Resolved: This incident has been resolved.

Investigating: Cyber Sepolia appears to have stalled at block 5,776,486 - The Quicknode team is investigating and will update with more information once it is available.

Resolved: This incident has been resolved.

Monitoring: The Polygon archive nodes have recovered, we continue to monitor them for performance.

Investigating: The Quicknode team is investigating the degraded performance of Polygon Mainnet Archive Nodes.

Customers may experience increased error rates, including 503 responses, along with failed or timing-out requests when querying historical (archive) data.

Standard (non-archive) Polygon endpoints are not affected at this time, and our team is actively working to restore archive capacity and mitigate customer impact.

We will update this page as we acquire new information.

Resolved: This incident has been resolved.

Investigating: We are currently investigating an issue affecting Tempo Testnet nodes. Block height is stalled at 301,478 and nodes are not progressing to the current tip.

Our engineering team is actively investigating the root cause and working toward a resolution. We will provide the next update on or before 03:00 1/11 UTC.

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.

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

Identified: Our team has pushed a fix and nodes are in the recovering stage. We will provide an update by 13:00 PM UTC.

Identified: Our engineers are actively working to restore capacity. The next update will be provided on or before 11:00 AM UTC.

Investigating: We are currently investigating this issue.

Resolved: This incident has been resolved.

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

Identified: We have identified the cause of the ongoing degradation affecting Polygon archive endpoints. Mitigation efforts are underway to reduce error rates while we continue investigating a longer-term resolution.

Non-archive Polygon endpoints remain unaffected. We will continue to provide updates as recovery progresses.

Investigating: The Quicknode team is investigating the degraded performance of Polygon Mainnet Archive Nodes.

Customers may experience increased error rates, including 503 responses, along with failed or timing-out requests when querying historical (archive) data.

Standard (non-archive) Polygon endpoints are not affected at this time, and our team is actively working to restore archive capacity and mitigate customer impact.

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: We have identified a possible root cause for Flow Testnet EVM - Our engineers are working on a fix.

The Support Team will provide an update by 17:30 UTC.

Investigating: The Quicknode team is investigating the degraded performance of Flow Testnet EVM. No action needed from users at this time but you may see an increase in error rates during this incident.

The Support Team will provide an update by 17:00 UTC.