Live / Gateway / Incident
Gateway: Increased error responses
Gateway · transactiongateway.comMajor incidentResolved2026-10-21 04:22 UTC
Public — what happened
Summary
Gateway reported a major incident titled "Increased error responses," in which it saw a rise in HTTP 503 errors, a type of message meaning a service was unavailable. The company said requests were affected between 22:16 and 22:36 CDT, and its engineers were monitoring the situation. The incident was logged as starting at 04:04 UTC on 2026-10-21 and marked resolved at 04:22. Gateway did not say in its text what caused the errors.
Affected
Transaction API, Control Panel, Query API
Timeline
- Started — 2026-10-21 04:04 UTC
- Monitoring — 2026-10-21 04:04 UTC
- Resolved — 2026-10-21 04:22 UTC · 17 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 Gateway 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 Gateway: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Gateway report →
More from Gateway
Covered in The Squid’s Ink, Week 44, 2026, our weekly internet health report.