QuickNode Status

Resolved: This incident has been resolved.

Monitoring: Nodes are producing new blocks again. We will keep monitoring this situation.

Investigating: We are currently investigating this issue.
We expect to provide an update in the next 30 mins.

Resolved: This incident has been resolved.

Monitoring: We have applied a fix, expect to see node to recover in the next 20 minutes.

Investigating: We are currently investigating this issue - we expect to provide an update within 30 minutes.

Resolved: This incident has been resolved.

Monitoring: The network is progressing once again. We are monitoring performance to ensure stability and will provide an update upon confirmation or if further action is required.

Identified: Public explorer stalled at block 23202037, foundation is aware and working on getting service restored ASAP. In meantime degraded performance is expected. As we progress toward a resolution, please expect the next update on or before 21:00 UTC.

https://lineascan.build

Identified: The issue has been identified by the foundation, and a fix is being implemented. https://linea.statuspage.io/incidents/wtrzr0qmgd4c

As we progress toward a resolution, please expect the next update on or before 22:00 UTC.

Identified: There is a degraded performance observed with the foundation's sequencer. Our engineers are closely listening to updates from the foundation.

https://linea.statuspage.io/incidents/wtrzr0qmgd4c

Investigating: We are currently investigating this issue.

Resolved: All Polygon mainnet Bor and Erigon nodes have been fully restored and are operating normally. We will continue monitoring to ensure stability and address any potential issues. Thank you for your patience.

Monitoring: Most of the Bor and Erigon nodes have recovered and are now serving requests. We are actively monitoring performance and working to restore service to full capacity.

We will provide the next update by 12:00 UTC or sooner.

Monitoring: The Bor nodes have been recovered, and the QuickNode team is working closely with the foundation to fully recover the Erigon nodes. We will provide the next update by 07:00 UTC or sooner.

Monitoring: We are working closely with the Polygon Foundation and monitoring Erigon nodes as they re-sync.

Impact: Polygon API and Polygon Streams may return null responses or fail on some calls. Customer Action: No action needed; retry affected calls with exponential backoff.

Next Update: By 03:30 UTC.

Monitoring: We have implemented Bor new release v2.2.11-beta2, our Bor nodes are recovered. We will continue to monitor the situation. We expect to provide next update by 16:00 UTC.

Identified: Our Erigon nodes are showing signs of recovery; however, Bor nodes remain impacted at this time.

We’ve been informed that a new Heimdall and Bor release, which includes a Heimdall hardfork, is scheduled to go live in approximately 1 hour. The hardfork is expected to occur at 13:00 UTC. The Polygon Foundation will publish the new release once available, and we will begin deployment shortly thereafter.

We will provide the next update by 13:00 UTC.

Thank you for your patience.

Identified: Our engineers are closely listening to updates from the foundation.

As we progress toward a resolution, please expect the next update on or before 12:00 UTC.

https://status.polygon.technology/incidents/c8nc05x3qvmg

Investigating: Our engineers are currently investigating issues with the Polygon mainnet node infrastructure (primarily impacting archive calls).

As we progress toward a resolution, expect the next update on or before 6:00 UTC.

Resolved: This incident has been resolved.

Monitoring: QuickNode teams have been working with the foundation team on this incident. The foundation team has deployed fixes, and nodes have also been recovered. We are continuing to monitor to ensure full stability.

We will provide the next update by 09:00 UTC or sooner.

Identified: The Foundation has confirmed a network-wide outage. QuickNode teams are closely following their guidance to recover nodes. Requests that depend on new blocks may fail or return stale data.

We will provide the next update by 10:00 UTC or sooner.

Investigating: The Fuel Mainnet is stuck at block 32,381,820. Requests depending on new blocks may fail or return stale data. QuickNode teams are investigating and will update with more information once it is available. We will provide the next update by 08:00 UTC or sooner.

Resolved: This incident has been resolved.

Monitoring: QuickNode teams have been working with the foundation team on this incident. The foundation team has recovered the sequencer, and affected nodes have also been recovered. We are continuing to monitor to ensure full stability.

We will provide the next update by 10:00 UTC or sooner.

Investigating: The Scroll Testnet is stuck at block 12,201,189. Requests depending on new blocks may fail or return stale data. QuickNode teams are investigating and will update with more information once it is available. We will provide the next update by 10:00 UTC or sooner.

Resolved: This incident has been resolved.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: 503 mitigated, our engineering team continues to monitor for efficacy heading towards a full resolution.

Investigating: We are investigating the degraded performance issue on the Solana mainnet, which may intermittently cause 503 errors. As we progress toward a resolution, expect the next update on or before 17:00 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 by the foundation, and a fix is being implemented. https://linea.statuspage.io/incidents/p0d5fkghnv02

As we progress toward a resolution, please expect the next update on or before 9:00 UTC.

Identified: There is a degraded performance observed with the foundation's sequencer. Our engineers are closely listening to updates from the foundation.

https://linea.statuspage.io/incidents/p0d5fkghnv02

Investigating: The Linea Mainnet is stuck at block 23,145,386.

Resolved: This incident has been resolved.

Monitoring: As of 03:45 UTC, services have been fully restored and are operating normally. Our engineers will continue to monitor the node infrastructure, and we will share the next update on or before 6.00 UTC.

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

Investigating: We are investigating the degraded performance issue on the Solana mainnet, which may intermittently cause 503 errors. As we progress toward a resolution, expect the next update on or before 5:00 UTC.

Resolved: This incident has been resolved.

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

Identified: We're currently experiencing an issue where historical archive data for blocks prior to 158817115 before August 8th, 2025 at 23:59 UTC are unavailable, returning HTTP 422 "UNKNOWN_BLOCK" errors.

Our engineering team is working with the Near foundation team on restoring of blocks prior to 158817115 with a snapshot. Expected duration minimum of five days, expect the next update on Sept 9th at 17:00 UTC as we progress toward a resolution.

Identified: We're currently experiencing an issue where historical archive data for blocks prior to 158817115 before August 8th, 2025 at 23:59 UTC are unavailable, returning HTTP 422 "UNKNOWN_BLOCK" errors.

Our engineering team is working with the Near foundation team on restoring of blocks prior to 158817115 with a snapshot. Expected duration minimum of five days, expect the next update on Aug 25 at 17:00 UTC as we progress toward a resolution.