Guides

# Testing slow and failing networks

Make a read slow or fail on purpose, to check your app copes.

Add these to any read URL to see what your app does when the network or hotcfg misbehaves. Responses with them are never cached.

| Parameter | Values | Effect |
| --- | --- | --- |
| `delay` | milliseconds (`800`) or a duration (`2s`), at most 10 s | Hold the response this long. |
| `chaos` | 0–100 | Fail with `500` this percentage of the time. |
| `status` | 400–599 | Always answer with this error status. |

terminal

```
curl "https://api.hotcfg.run/v1/acme/mobile-flags?delay=3s"     # longer than the 2 s timeout
curl "https://api.hotcfg.run/v1/acme/mobile-flags?status=503"
```

Point a debug build at one of these URLs and check that the app starts with the last good config, or its defaults.

At most 4 delayed reads run at once per IP address; past that, `429 delay_limited`.

Last updated 5 November 2026
