Live / Quicknode / Incident
Quicknode: World Chain Mainnet – Intermittent 503 errors
Quicknode · quicknode.comMinor incidentResolved2026-10-08 18:35 UTC
Public — what happened
Summary
Quicknode reported that some requests to its World Chain Mainnet service were sporadically failing with 503 errors, starting at 12:17 UTC on 2026-10-05, and it rated the problem as minor. The company said the failures came from a fault in the node client software running on a portion of its backend nodes, and that it was working with the World Chain team on the problem. By 13:32 UTC the same day, Quicknode said the World Chain team had confirmed the underlying cause and was preparing an updated client release, which Quicknode planned to roll out across its nodes. The incident was marked resolved on 2026-10-08 at 18:35.
Affected
World Chain - Mainnet
Timeline
- Started — 2026-10-05 12:17 UTC
- Investigating — 2026-10-05 12:17 UTC
- Identified — 2026-10-05 13:32 UTC
- Resolved — 2026-10-08 18:35 UTC · 3 days 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.