QuickNode Status

Resolved: This incident has been resolved.

Monitoring: Nodes have been restarted and the chain stall has been resolved. 503 errors are no longer observed. We are monitoring the service for continued stability as backfill requests normalize.

Investigating: Base Mainnet is experiencing a chain-wide stall. The Quicknode team is investigating and will update this page as more information becomes available.

For reference, please see the Base status page: https://status.base.org/incidents/5c4gm1wzbjs4

Resolved: B3 Mainnet block production has resumed and the network stall at block 60028954 has been resolved. This incident was related to a chain-wide stall on Base Mainnet. All systems are now operating normally.

Investigating: B3 Mainnet appears to have stalled at block 60028954 due to a chain-wide stall on Base Mainnet, which B3 depends on. The Quicknode team is investigating and will update this page as more information becomes available.

For Base Mainnet status, please refer to the Base status page: https://status.base.org/incidents/5c4gm1wzbjs4

Resolved: This incident has been resolved.

Monitoring: Nodes have been restarted and the chain stall has been resolved. 503 errors are no longer observed. We are monitoring the service for continued stability as backfill requests normalize.

Investigating: Base Mainnet is experiencing a chain-wide stall. The Quicknode team is investigating and will update this page as more information becomes available.

For reference, please see the Base status page: https://status.base.org/incidents/5c4gm1wzbjs4

Resolved: B3 Mainnet block production has resumed and the network stall at block 60028954 has been resolved. This incident was related to a chain-wide stall on Base Mainnet. All systems are now operating normally.

Investigating: B3 Mainnet appears to have stalled at block 60028954 due to a chain-wide stall on Base Mainnet, which B3 depends on. The Quicknode team is investigating and will update this page as more information becomes available.

For Base Mainnet status, please refer to the Base status page: https://status.base.org/incidents/5c4gm1wzbjs4

Resolved: This incident has been resolved.

Monitoring: Nodes have been restarted and the chain stall has been resolved. 503 errors are no longer observed. We are monitoring the service for continued stability as backfill requests normalize.

Investigating: Base Mainnet is experiencing a chain-wide stall. The Quicknode team is investigating and will update this page as more information becomes available.

For reference, please see the Base status page: https://status.base.org/incidents/5c4gm1wzbjs4

Resolved: B3 Mainnet block production has resumed and the network stall at block 60028954 has been resolved. This incident was related to a chain-wide stall on Base Mainnet. All systems are now operating normally.

Investigating: B3 Mainnet appears to have stalled at block 60028954 due to a chain-wide stall on Base Mainnet, which B3 depends on. The Quicknode team is investigating and will update this page as more information becomes available.

For Base Mainnet status, please refer to the Base status page: https://status.base.org/incidents/5c4gm1wzbjs4

Resolved: This incident has been resolved.

Monitoring: Nodes have been restarted and the chain stall has been resolved. 503 errors are no longer observed. We are monitoring the service for continued stability as backfill requests normalize.

Investigating: Base Mainnet is experiencing a chain-wide stall. The Quicknode team is investigating and will update this page as more information becomes available.

For reference, please see the Base status page: https://status.base.org/incidents/5c4gm1wzbjs4

Resolved: B3 Mainnet block production has resumed and the network stall at block 60028954 has been resolved. This incident was related to a chain-wide stall on Base Mainnet. All systems are now operating normally.

Investigating: B3 Mainnet appears to have stalled at block 60028954 due to a chain-wide stall on Base Mainnet, which B3 depends on. The Quicknode team is investigating and will update this page as more information becomes available.

For Base Mainnet status, please refer to the Base status page: https://status.base.org/incidents/5c4gm1wzbjs4

Resolved: This incident has been resolved.

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

Identified: The Base team is continuing to debug and have isolated a consensus problem that caused an invalid block to be sequenced. This prevented new blocks from being created following block 47806542. The Base team is working on a fix to resume block propagation to the network while further isolating the root cause of the problematic block.

For more information, please refer to the Base status page: https://status.base.org/incidents/5c4gm1wzbjs4

Identified: The Base Team has identified the issue with a problematic block interfering with subsequent block building. Their team is working on several threads to remediate. We will provide further updates as the situation develops.

For more information, please refer to the Base status page: https://status.base.org/incidents/5c4gm1wzbjs4

Investigating: Base Mainnet block production is currently unhealthy during the activation of the Beryl Upgrade.

For more information, please refer to the Base status page: https://status.base.org/incidents/5c4gm1wzbjs4

Resolved: This incident has been resolved.

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

Identified: The Base team is continuing to debug and have isolated a consensus problem that caused an invalid block to be sequenced. This prevented new blocks from being created following block 47806542. The Base team is working on a fix to resume block propagation to the network while further isolating the root cause of the problematic block.

For more information, please refer to the Base status page: https://status.base.org/incidents/5c4gm1wzbjs4

Identified: The Base Team has identified the issue with a problematic block interfering with subsequent block building. Their team is working on several threads to remediate. We will provide further updates as the situation develops.

For more information, please refer to the Base status page: https://status.base.org/incidents/5c4gm1wzbjs4

Investigating: Base Mainnet block production is currently unhealthy during the activation of the Beryl Upgrade.

For more information, please refer to the Base status page: https://status.base.org/incidents/5c4gm1wzbjs4

Resolved: This incident has been resolved.

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

Identified: The Base team is continuing to debug and have isolated a consensus problem that caused an invalid block to be sequenced. This prevented new blocks from being created following block 47806542. The Base team is working on a fix to resume block propagation to the network while further isolating the root cause of the problematic block.

For more information, please refer to the Base status page: https://status.base.org/incidents/5c4gm1wzbjs4

Identified: The Base Team has identified the issue with a problematic block interfering with subsequent block building. Their team is working on several threads to remediate. We will provide further updates as the situation develops.

For more information, please refer to the Base status page: https://status.base.org/incidents/5c4gm1wzbjs4

Investigating: Base Mainnet block production is currently unhealthy during the activation of the Beryl Upgrade.

For more information, please refer to the Base status page: https://status.base.org/incidents/5c4gm1wzbjs4

Resolved: This incident has been resolved.

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

Identified: The Base team is continuing to debug and have isolated a consensus problem that caused an invalid block to be sequenced. This prevented new blocks from being created following block 47806542. The Base team is working on a fix to resume block propagation to the network while further isolating the root cause of the problematic block.

For more information, please refer to the Base status page: https://status.base.org/incidents/5c4gm1wzbjs4

Identified: The Base Team has identified the issue with a problematic block interfering with subsequent block building. Their team is working on several threads to remediate. We will provide further updates as the situation develops.

For more information, please refer to the Base status page: https://status.base.org/incidents/5c4gm1wzbjs4

Investigating: Base Mainnet block production is currently unhealthy during the activation of the Beryl Upgrade.

For more information, please refer to the Base status page: https://status.base.org/incidents/5c4gm1wzbjs4

Resolved: This incident has been resolved.

Identified: The underlying issue has been identified, and a mitigation is in place. Some nodes have recovered, and 503s have been mitigated. Quicknode teams are continuing to work to recover full capacity and monitor performance to ensure stability.

Investigating: The Quicknode team is investigating the degraded performance of Ethereum mainnet archived nodes.

Customers may experience increased error rates, including 503 responses, when querying archive data.

We will update this page as we acquire new information.

Resolved: This incident has been resolved.

Identified: The underlying issue has been identified, and a mitigation is in place. Some nodes have recovered, and 503s have been mitigated. Quicknode teams are continuing to work to recover full capacity and monitor performance to ensure stability.

Investigating: The Quicknode team is investigating the degraded performance of Ethereum mainnet archived nodes.

Customers may experience increased error rates, including 503 responses, when querying archive data.

We will update this page as we acquire new information.