hub · terms of use
Terms of use
What this service is for, what it isn't for, and what happens if you abuse it.
This is a free, public chaos-engineering scratchpad. There is no signup, no account, no contract, no SLA. Use of the service is at your own risk.
What it’s for
- Testing how your HTTP client, integration tests, or downstream tooling handles real-world adversity — latency, malformed payloads, broken CORS, lying retry headers, status code variety, etc.
- Demonstrating failure modes in a workshop, blog post, or talk.
- Quick smoke tests in CI, well within the rate limit.
- Building a client against the well-formed counterpart at not.catastrophic.io, then flipping the hostname to test how it handles things going wrong.
What it’s not for
- Load testing. Sixty requests per minute per IP is the ceiling. Don’t use this site to benchmark anything.
- Staging a denial-of-service attack against another target. Routing legitimate-looking traffic through these endpoints to confuse a downstream is not a supported use case.
- Production dependencies. Don’t make this site load-bearing for anything that matters. It can change, move, or go away at any time.
- Scraping or mirroring. The catalog and OpenAPI spec are published for human reference, not bulk consumption.
- Anything illegal in your jurisdiction or the operator’s (United States).
What is enforced
- A rate limit of 60 requests per minute per IP, applied at the edge.
- Discretionary blocking of IPs, ASNs, or user agents that abuse the service. There is no appeal process.
- Endpoint behavior, paths, and the catalog itself can change without notice. The OpenAPI spec is the contract; nothing else is.
No warranty
The service is provided as-is, without warranty of any kind, express or implied. The operator is not liable for any loss, damage, or downstream consequence arising from use of these endpoints — including but not limited to: a misbehaving response causing your client to misbehave (that is, after all, the point).
Changes
These terms can change. The version in effect is the one published here at the time of your request. Continued use after a change constitutes acceptance of the new terms.
Last updated: 2026-05-15.