Live / Quicknode / Incident
Quicknode: Near Mainnet - Degraded Performance
Quicknode · quicknode.comMinor incidentResolved2026-10-08 17:17 UTC
Public — what happened
Summary
Quicknode reported a minor incident on its Near Mainnet service starting at 16:45 UTC on 2026-10-08, saying it was looking into a rise in errors returned by its API. By 17:17 UTC the company said things had settled down and it was keeping watch to make sure the service stayed steady. Quicknode did not name a cause, and the incident had not been marked resolved.
Affected
NEAR - Mainnet
Timeline
- Started — 2026-10-08 16:45 UTC
- Investigating — 2026-10-08 16:45 UTC
- Monitoring — 2026-10-08 17:17 UTC
- Resolved — 2026-10-08 17:17 UTC · 32 min 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.