QuickNode Status

Resolved: The network has returned to normal operations. Our engineers have confirmed stability, and the issue has been fully resolved. If you continue to experience any problems, please don't hesitate to reach out.

Investigating: Our engineers are closely listening to updates from the foundation. As we progress toward a resolution, please expect the next update on or before 10:00 UTC.

Investigating: We are currently investigating this issue.

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

Resolved: The network has returned to normal operations. Our engineers have confirmed stability, and the issue has been fully resolved. If you continue to experience any problems, please don't hesitate to reach out.

Investigating: Our engineers are closely listening to updates from the foundation. As we progress toward a resolution, please expect the next update on or before 10:00 UTC.

Investigating: We are currently investigating this issue.

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

Resolved: The network has returned to normal operations. Our engineers have confirmed stability, and the issue has been fully resolved. If you continue to experience any problems, please don't hesitate to reach out.

Investigating: Our engineers are closely listening to updates from the foundation. As we progress toward a resolution, please expect the next update on or before 10:00 UTC.

Investigating: We are currently investigating this issue.

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

Resolved: The network has returned to normal operations. Our engineers have confirmed stability, and the issue has been fully resolved. If you continue to experience any problems, please don't hesitate to reach out.

Investigating: Our engineers are closely listening to updates from the foundation. As we progress toward a resolution, please expect the next update on or before 10:00 UTC.

Investigating: We are currently investigating this issue.

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

Resolved: This incident has been resolved.

Monitoring: 503s have been mitigated and nodes are recovering. We will provide an update once a full resolution has been reached.

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: 503s have been mitigated and nodes are recovering. We will provide an update once a full resolution has been reached.

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: The foundation has provided a fix, and it has been deployed across QuickNode's Berachain-Mainnet infrastructure. All nodes have synced to the tip of the network and are progressing as expected. No further customer impact is expected. Please get in touch with support for any additional questions: https://support.quicknode.com/

Investigating: The Berachain network has been intentionally halted by validators while the core team performs an emergency hard fork to address a Balancer V2 exploit on the BEX.

QuickNode is monitoring the situation and will restore normal operations once the Berachain Foundation completes the fix and provides instructions to resume.

Resolved: The foundation has provided a fix, and it has been deployed across QuickNode's Berachain-Mainnet infrastructure. All nodes have synced to the tip of the network and are progressing as expected. No further customer impact is expected. Please get in touch with support for any additional questions: https://support.quicknode.com/

Investigating: The Berachain network has been intentionally halted by validators while the core team performs an emergency hard fork to address a Balancer V2 exploit on the BEX.

QuickNode is monitoring the situation and will restore normal operations once the Berachain Foundation completes the fix and provides instructions to resume.

Resolved: The foundation has provided a fix, and it has been deployed across QuickNode's Berachain-Mainnet infrastructure. All nodes have synced to the tip of the network and are progressing as expected. No further customer impact is expected. Please get in touch with support for any additional questions: https://support.quicknode.com/

Investigating: The Berachain network has been intentionally halted by validators while the core team performs an emergency hard fork to address a Balancer V2 exploit on the BEX.

QuickNode is monitoring the situation and will restore normal operations once the Berachain Foundation completes the fix and provides instructions to resume.

Resolved: The foundation has provided a fix, and it has been deployed across QuickNode's Berachain-Mainnet infrastructure. All nodes have synced to the tip of the network and are progressing as expected. No further customer impact is expected. Please get in touch with support for any additional questions: https://support.quicknode.com/

Investigating: The Berachain network has been intentionally halted by validators while the core team performs an emergency hard fork to address a Balancer V2 exploit on the BEX.

QuickNode is monitoring the situation and will restore normal operations once the Berachain Foundation completes the fix and provides instructions to resume.

Resolved: The Bitcoin Testnet4 Blockbook service has been fully restored. Our backends have successfully resynced and all endpoints are now operational. We apologize for the disruption and thank you for your patience.

Investigating: We are currently experiencing issues with our Bitcoin Testnet4 Blockbook service. Our backend nodes have fallen behind, causing service disruptions. Our engineering team has identified the root cause and is actively working on a resolution. We will provide updates by 14:00PM UTC.

Resolved: The Bitcoin Testnet4 Blockbook service has been fully restored. Our backends have successfully resynced and all endpoints are now operational. We apologize for the disruption and thank you for your patience.

Investigating: We are currently experiencing issues with our Bitcoin Testnet4 Blockbook service. Our backend nodes have fallen behind, causing service disruptions. Our engineering team has identified the root cause and is actively working on a resolution. We will provide updates by 14:00PM UTC.

Resolved: The Bitcoin Testnet4 Blockbook service has been fully restored. Our backends have successfully resynced and all endpoints are now operational. We apologize for the disruption and thank you for your patience.

Investigating: We are currently experiencing issues with our Bitcoin Testnet4 Blockbook service. Our backend nodes have fallen behind, causing service disruptions. Our engineering team has identified the root cause and is actively working on a resolution. We will provide updates by 14:00PM UTC.

Resolved: The Bitcoin Testnet4 Blockbook service has been fully restored. Our backends have successfully resynced and all endpoints are now operational. We apologize for the disruption and thank you for your patience.

Investigating: We are currently experiencing issues with our Bitcoin Testnet4 Blockbook service. Our backend nodes have fallen behind, causing service disruptions. Our engineering team has identified the root cause and is actively working on a resolution. We will provide updates by 14:00PM UTC.

Resolved: The Bitcoin Testnet4 Blockbook service has been fully restored. Our backends have successfully resynced and all endpoints are now operational. We apologize for the disruption and thank you for your patience.

Investigating: We are currently experiencing issues with our Bitcoin Testnet4 Blockbook service. Our backend nodes have fallen behind, causing service disruptions. Our engineering team has identified the root cause and is actively working on a resolution. We will provide updates by 14:00PM UTC.

Resolved: This incident has been resolved.

Monitoring: The Celestia Mocha Network is producing blocks once again

Investigating: The network briefly resumed producing blocks but has stalled again at block 8,687,751 and our engineers are closely listening to updates from the foundation.

https://status.celestia.org/incidents/01K95G5PBBQGE5JHPCNAVFR5PM

Investigating: The network remains stalled, and our engineers are closely listening to updates from the foundation.

https://status.celestia.org/incidents/01K95G5PBBQGE5JHPCNAVFR5PM

Investigating: The Celestia Mocha Testnet appears to have stalled at block 8687672- The QuickNode team is working with the chain team and will update with more information once it is available.

We will update this status by 00:00 UTC

Resolved: This incident has been resolved.

Monitoring: Ethereum-Hoodi archive nodes have 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: We are currently observing degraded performance affecting Ethereum (eth_hoodi) archive nodes. Customers may experience elevated error rates or intermittent 503 responses when making archive calls.

A patch is being deployed. We will continue to monitor performance as the fix propagates.

Next update: Within 1 hour or as new information becomes available.

Resolved: This incident has been resolved.

Monitoring: Ethereum-Hoodi archive nodes have 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: We are currently observing degraded performance affecting Ethereum (eth_hoodi) archive nodes. Customers may experience elevated error rates or intermittent 503 responses when making archive calls.

A patch is being deployed. We will continue to monitor performance as the fix propagates.

Next update: Within 1 hour or as new information becomes available.

Resolved: This incident has been resolved.

Monitoring: Ethereum-Hoodi archive nodes have 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: We are currently observing degraded performance affecting Ethereum (eth_hoodi) archive nodes. Customers may experience elevated error rates or intermittent 503 responses when making archive calls.

A patch is being deployed. We will continue to monitor performance as the fix propagates.

Next update: Within 1 hour or as new information becomes available.

Resolved: This incident has been resolved.

Monitoring: Ethereum-Hoodi archive nodes have 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: We are currently observing degraded performance affecting Ethereum (eth_hoodi) archive nodes. Customers may experience elevated error rates or intermittent 503 responses when making archive calls.

A patch is being deployed. We will continue to monitor performance as the fix propagates.

Next update: Within 1 hour or as new information becomes available.

Resolved: This incident has been resolved.

Monitoring: Ethereum-Hoodi archive nodes have 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: We are currently observing degraded performance affecting Ethereum (eth_hoodi) archive nodes. Customers may experience elevated error rates or intermittent 503 responses when making archive calls.

A patch is being deployed. We will continue to monitor performance as the fix propagates.

Next update: Within 1 hour or as new information becomes available.