QuickNode Status

Monitoring: Our nodes are back at the chain tip, healthy, and 503 errors have cleared. To accelerate stabilization, we have temporarily blocked the following high-load methods: • trace_filter • debug_traceBlockByNumber • debug_traceBlockByHash • debug_traceTransaction • debug_traceCall We will provide another update by 23:00 UTC, or sooner.

Identified: Our nodes are in the process of recovering, and 503 error rate is dropping. To expedite recovery, we have temporarily blocked the following resource-intensive methods: trace_filter debug_traceBlockByNumber debug_traceBlockByHash debug_traceTransaction debug_traceCall

We will provide another update by 03:30 UTC

Investigating: We are currently experiencing elevated 503 errors on Polygon-Amoy. Our team is working to restore nodes fully, but customers may encounter an increased 503 error rate in the meantime. We will share another update by 23:30 UTC

Resolved: This incident has been resolved.

Monitoring: Aptos Foundation has released v1.38.3-rc which addresses the underlying bug. Our engineering team is currently testing and monitoring this patch before deploying to production. We will provide the next update today by 13:00 UTC or sooner.

Identified: The QuickNode team is actively working with the Aptos Foundation team. The Foundation is preparing to release a new version shortly, which will include a fix to mitigate the issue.

Investigating: We've detected a bug in the new aptos release 1.38.0 and 1.38.2 which is causing timeouts of RPC calls, we're in contact with the Foundation to resolve this.

Resolved: This incident has been resolved.

Monitoring: The foundation has implemented a fix and we are monitoring the situation.

Investigating: We are currently observing intermittent stalled block progression and instability on Linea Mainnet.

This issue originates upstream from the foundation. Linea has acknowledged the incident and is actively investigating. You can track their official updates here: https://linea.statuspage.io/incidents/2nqgy3f4bhbc

We will continue monitoring the situation and will update this page as soon as more information becomes available.

Resolved: This incident has been resolved.

Monitoring: Our Tron infrastructure has recovered. We are monitoring performance to ensure stability and will provide an update upon confirmation or if further action is required within 10 minutes.

Investigating: Mitigations have been put in place to address the immediate 503 errors you may have received on Tron in the APAC region. You may see heightened latency while our team continues to investigate the underlying cause of the node degradation with the Tron Team.

We will update this status no later than 04:00 UTC.

Investigating: The QuickNode team is investigating the degraded performance of Tron Mainnet in the APAC Region. You may see heightened error rates while we work to mitigate the issue.

We will update this page no later than 20 UTC.

Resolved: This incident has been resolved.

Investigating: We are currently experiencing disruptions affecting multiple Quicknode platform pages due to Cloudflare errors. Affected services include Dashboards, docs and other platform pages. Customers may experience HTTP 500 errors or be unable to access these services.

Quicknode RPC endpoints and services remain fully operational. Only landing pages and dashboards are affected.

Resolved: This incident has been resolved.

Investigating: We are actively tracking connectivity issues across several networks in US-E related to an upstream provider. We are continuing to monitor and mitigate connection problems where possible. No customer action is required at this time. We will share another update by 14:30 UTC

Resolved: This incident has been resolved.

Identified: Our team has deployed a fix to mitigate the degraded performance issue. Some customers may still encounter intermittent HTTP 503 responses while the mitigation is in progress.

We will provide the next update by 17 November at 14:00 UTC or sooner.

Investigating: We are currently experiencing elevated traffic on the Aptos. Customers may experience HTTP 503 errors. Retrying requests may temporarily mitigate the issue.

Our teams are working on this and will provide the next update by 17 November at 14:00 UTC or sooner.

Resolved: This incident has been resolved.

Identified: Dashboard endpoint logs are delivering as expected. We are monitoring performance to ensure stability and will provide an update upon confirmation or if further action is required within 10 minutes.

Identified: We have identified the issue impacting the delivery of in-dashboard RPC logs and are implementing a fix. Customers may notice missing or delayed logs in the dashboard. RPC traffic remains fully operational and unaffected. Next update will be on November 16th at 13:00 UTC or earlier

Investigating: Our team is investigating an issue that is impacting the delivery of in-dashboard RPC Logs. http://dashboard.quicknode.com/endpoints/{id}/logs. Next update scheduled November 16th, 5:00 UTC.

Resolved: This incident has been resolved.

Investigating: An issue is affecting Unichain Mainnet and Unichain Sepolia L2 Safe Head advancement and L1 Batch Posting. This is a network wide issue. See Unichain's status page for more info: https://status.unichain.org/cmi1vita8005dfg4en1srqgm9

Resolved: Polygon Amoy has been updated with the foundation provided fix, this incident has been resolved.

Identified: We continue to coordinate with the Polygon foundation on this issue. The team is actively debugging but expects a delay in releasing a fix due to the weekend. They will roll out the resolution as soon as available. Expect the next update on or before Tuesday, November 18th, 10:00 UTC.

Identified: We are closely listening to updates from the foundation. As we progress toward a resolution, expect the next update on or before 15th Nov, 10:00 UTC.

Investigating: There is a bug with the Erigon client we use for archive data where it has halted syncing at block 29020819

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

Resolved: This incident has been resolved.

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

Identified: We are currently experiencing elevated traffic on the Aptos shared node infrastructure. We will provide the next update on or before 15 November at 10:00 UTC as we work toward a resolution.

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: The issue has been identified, and a fix is being implemented.

As we progress toward a resolution, expect the next update on or before 15th Nov, 8:00 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.

Investigating: Response logs for endpoints are failing to populate.

Customers will be unable to access logs via their dashboard or Console API until resolved, and may notice gaps once logs are restored. Our team is actively working on a solution and will provide another update by 4:00 UTC.

Investigating: Response logs for endpoints are failing to populate.

Customers will be unable to access logs via their dashboard or Console API until resolved, and may notice gaps once logs are restored. Our team is actively working on a solution and will provide another update by 3:00 UTC.