Live  /  Quicknode  /  Incident

Quicknode: Stacks Mainnet Stuck at Block 9,395,980

Quicknode · quicknode.comMinor incidentResolved2026-11-02 21:30 UTC
Public — what happened

Summary

Quicknode said its Stacks Mainnet endpoints stopped advancing at block 9,395,980 starting around 13:48 UTC on 2026-11-02, which could give users out-of-date responses from the RPC service. The company opened its investigation at 15:18 UTC and reported at 16:44 UTC that it had identified the root cause and was working to restore the connection. By 18:04 UTC it said blocks were catching up and it was monitoring for full recovery, and it marked the incident resolved at 21:30 UTC.

Affected

Stacks - Mainnet

As listed on Quicknode’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Quicknode against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Quicknode: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Quicknode report →

More from Quicknode

Covered in The Squid’s Ink, Week 46, 2026, our weekly internet health report.

The full archive is on the Quicknode status & history page.

Related: Quicknode status & history. SquidGrid is not affiliated with Quicknode.