Live / Quicknode / Incident
Quicknode: Cosmos Mainnet Outage - 503 Errors
Quicknode · quicknode.comMinor incidentResolved2026-10-28 18:23 UTC
Public — what happened
Summary
Quicknode reported a problem with its Cosmos Mainnet endpoints that began at 14:55 UTC on 2026-10-28, when users could get 503 errors while trying to connect. The company labeled it minor and said its team was working to restore service. At 15:24 UTC Quicknode said traffic had returned and the errors were no longer showing up, and it kept watching the service. The incident was marked resolved at 15:35 UTC, and the company did not state a cause in the text provided.
Affected
Cosmos - Mainnet
Timeline
- Started — 2026-10-28 14:55 UTC
- Investigating — 2026-10-28 14:55 UTC
- Monitoring — 2026-10-28 15:24 UTC
- Resolved — 2026-10-28 15:35 UTC · 40 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 45, 2026, our weekly internet health report.