QuickNode Status

Resolved: This incident has been resolved.

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

Identified: Our team has identified a bug in the latest release of the Polygon-Amoy client that is causing node instability. This issue has been brought to the attention of the Foundation, and we are actively working on a solution. While our work toward full recovery continues, the previously mentioned trace methods will remain disabled. Customers may also experience sporadic 503 errors.

We will provide another update by 6:00 UTC, or sooner.

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