Live / Quicknode / Incident
Quicknode: Injective Mainnet – Block Height Stall
Quicknode · quicknode.comMinor incidentResolved2026-10-07 13:24 UTC
Public — what happened
Summary
Quicknode reported that its Injective Mainnet nodes stopped moving forward at block 186,223,485 starting at 08:39 UTC on 2026-10-07, meaning requests could come back with outdated information. The company said the Injective Foundation acknowledged the problem and planned to release upgrade instructions, which Quicknode intended to apply to its nodes. By 10:18 UTC, Quicknode said the network was producing blocks again and requests were returning up-to-date data. The incident was marked resolved at 13:24 after a period of monitoring.
Affected
Injective - Mainnet
Timeline
- Started — 2026-10-07 08:39 UTC
- Investigating — 2026-10-07 08:39 UTC
- Identified — 2026-10-07 08:51 UTC
- Monitoring — 2026-10-07 10:18 UTC
- Resolved — 2026-10-07 13:24 UTC · 4h 45m after it started
With SquidGrid — where it starts on the route
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 seeCustomers 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 42, 2026, our weekly internet health report.