QuickNode Status

Resolved: This incident has been resolved.

Monitoring: Stellar Foundation identified the root cause and is working on a permanent fix. We have applied the workaround they provided and our nodes are now operational. We will continue monitoring to ensure stability until the permanent fix is released.

Investigating: We are investigating problems with Stellar Testnet endpoints. Currently experiencing 503 errors following upstream Stellar Testnet horizon disruption: https://status.stellar.org/incidents/60h5qgd5vz31 Stellar Mainnet endpoints continue to operate without disruption.

Resolved: This incident has been resolved.

Investigating: We are currently investigating degraded performance impacting Polygon Amoy nodes in the IAD region. Users may experience 503s and elevated latency during this time. Our engineers are looking into root cause and we will provide a status update as soon as possible.

Resolved: All affected nodes are now operational and performing as expected. Thank you for your patience during this incident.

Monitoring: More nodes are back at the tip. The QuickNode team is monitoring and recovering the node to full capacity. We will update you with more information as soon as it becomes available.

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

Identified: The QuickNode teams are working with the foundation team and have recovered some of the nodes. Some nodes are back at the tip. We will update you with more information as soon as it becomes available.

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

Investigating: The zkEVM mainnet nodes appear to have stalled at block 29,263,644. The QuickNode teams are investigating and will update you with more information as soon as it becomes available.

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

Resolved: This incident has been resolved.

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

Investigating: ZKsync Mainnet is currently experiencing network performance degradation. You may experience requests resulting in 503 errors and/or elevated latency. We're awaiting new information from the foundation and will provide an update as soon as possible.

Resolved: Block 151,960,880 will remain the earliest available block until our standard pruning policy reaches its threshold at a distance of 1,832,727 blocks. Once standard pruning resumes, we will continue to retain the most recent 1,832,727 blocks as detailed in our "Node Type" documentation: https://www.quicknode.com/docs/platform/supported-chains-node-types

Investigating: Our engineers are actively investigating and working on extending the data availability window. We’ll provide the next update on or before 31 Jan at 2:00 PM UTC.

Resolved: This issue has been resolved. Solana Streams and Webhooks are now operating normally, and stream delivery is no longer experiencing delays behind the tip of the chain. We will continue to monitor to ensure ongoing stability.

Monitoring: We have identified the issue impacting Solana Streams and Webhooks that caused intermittent delays behind the tip of the chain. A fix has been implemented, and we are actively monitoring the system to ensure performance has stabilized.

Investigating: We are investigating an issue impacting Solana Streams and Webhooks that may cause intermittent delivery delays for some streams, resulting in events lagging behind the tip of the chain. Our team is actively working to identify the root cause and restore normal performance.