Live / Quicknode / Incident
Quicknode: Injective Mainnet – Nodes Out of Sync Ahead of Scheduled Upgrade
Quicknode · quicknode.comMinor incidentResolved2026-11-11 13:04 UTC
Public — what happened
Summary
Quicknode reported a minor incident in which its Injective mainnet nodes fell behind the latest state of the blockchain, so customers' endpoints might return out-of-date data. The company said this began at 11:20 UTC on November 11, shortly before a scheduled Injective network upgrade planned for 12:00 to 14:00 UTC. By 11:37 UTC Quicknode said a fix had been applied and the nodes were catching up, though responses could still be slightly delayed until they finished syncing. The incident is now marked resolved as of 13:04 UTC.
Affected
Injective - Mainnet
Timeline
- Started — 2026-11-11 11:20 UTC
- Investigating — 2026-11-11 11:20 UTC
- Monitoring — 2026-11-11 11:37 UTC
- Resolved — 2026-11-11 13:04 UTC · 1h 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 47, 2026, our weekly internet health report.