Gateway
Limits and troubleshooting
How the gateway behaves at your quota, its fail-open guarantees, and what each error means.
Quota never blocks traffic
Reaching your plan's monthly request limit does not stop the gateway from proxying. At the limit, every request still reaches your server and returns the correct response. Only monitoring fidelity is reduced: capture is sampled rather than fully stored. There is no setting that blocks proxying for billing reasons.
Fail-open
The gateway is fail-open by design. If Spanly capture, ingest, or the config service is degraded, your traffic keeps flowing to your server. You may see a gap in captured telemetry during the incident, but your users are not affected.
Common responses
| Status | Meaning | What to do |
|---|---|---|
| 404 unknown gateway host | The hostname does not map to a gateway | Check the endpoint URL and that the gateway exists |
| 503 | The gateway is disabled | Re-enable it on the Gateway tab |
| 502 | The gateway could not reach your server | Check your server is up; the upstream status card shows this too |
| 504 | Your server did not respond in time | Raise the upstream timeout, or check your server's latency |
| 429 | Rate limited by the gateway | The client exceeded your configured rate limit; it should honor Retry-After |
| 413 | Request body too large | The body exceeded your size cap |
| 403 | Blocked by IP rules | The client's IP is outside your allow list or in your block list |
| 401 | A gateway client key is required or invalid | Send a valid Authorization: Bearer spanlygw_... |
For data handling, retention, and region guarantees, see the security and data handling page.