Is ReqRes (reqres.in) down right now?

Q: Is ReqRes (reqres.in) down right now?

Effectively yes for script/tutorial use — ReqRes (reqres.in) answered our last plain GET with HTTP 429 (rate-limits datacenter IPs (this checker, CI runners, cloud apps); residential browsers may still get through) (checked 2026-09-11T20:30:45Z). We check reqres.in with a plain keyless GET every hour; 24h OK-rate: 16.7%.

← all 71 tracked mock & placeholder APIs

Is ReqRes (reqres.in) down?

FAILING right now — answering HTTP 429 to plain requests: rate-limits datacenter IPs (this checker, CI runners, cloud apps); residential browsers may still get through.

Last checked 2026-09-11T20:30:45Z · checked every hour · OK-rate 24h: 16.7% · 7d: 37.8% · raw JSON · Atom feed of its down/recovered events

Failing streak began 2026-09-11T06:30:45Z (14 hours) · last successful check: 2026-09-11T05:31:08Z

Context: Keeps changing: required an x-api-key for part of 2026 (keyless curls 401'd), now keyless again but every response carries an injected _meta upsell object, writes are faked, and datacenter IPs (like this checker's) get 429-rate-limited.

What we check: GET https://reqres.in/api/users?page=1 — a plain, keyless request from Cloudflare's network with an honest bot UA, exactly what a tutorial curl or an <img> tag experiences. OK = HTTP 2xx/3xx within 8s. No retries, no cookies, no API keys.

Need a fake-data REST API that answers?

If reqres.in is failing (or you're tired of finding out mid-demo), Mockbird gives you a seeded fake-data REST API that answers right now — and unlike the classics, writes actually persist — free, no signup:

curl https://mockbird.mockbird.workers.dev/m/demo/products/1

Read the honest ReqRes (reqres.in) migration guide → (it also says when ReqRes (reqres.in) is the better tool) or create your own mock API in one click.

README badge

Does your project's test suite or tutorial depend on reqres.in? Embed a live status badge — it re-renders from our latest check (cached 5 min):

<!-- Markdown -->
[![reqres.in status](https://mockbird.mockbird.workers.dev/status/reqres/badge.svg)](https://mockbird.mockbird.workers.dev/status/reqres)

<!-- HTML -->
<a href="https://mockbird.mockbird.workers.dev/status/reqres"><img src="https://mockbird.mockbird.workers.dev/status/reqres/badge.svg" alt="reqres.in status"></a>

Green = answering plain GETs, red = network-dead, amber = answering but with an error status. Every tracked service has one; there's also a summary badge for all 71.

Get pinged when it goes down

Subscribe any webhook URL — no account needed. One message when reqres.in goes down, one when it recovers (debounced: two consecutive hourly checks must agree, so a single blip never fires). Slack and Discord incoming-webhook URLs get a formatted message; anything else gets an HMAC-signed JSON POST.

Or from a terminal / CI script:

curl -X POST https://mockbird.mockbird.workers.dev/api/status/watch \
  -H "content-type: application/json" \
  -d '{"service": "reqres", "url": "https://hooks.slack.com/services/T000/B000/XXXX"}'

Use "service": "*" to watch all 71 tracked services at once. The response includes an unsubscribe curl; 5 consecutive failed deliveries auto-unsubscribe. No webhook? Omit "url" to get a pollable subscription instead — GET the returned poll URL anytime for the transitions since your last poll. Full API details →

The same checker can watch your own URL: POST /api/status/monitor {"url": "https://api.example.com/health", "notify": "<webhook>"} — every 30 minutes, alert on down + recovery, free, no account. Monitor API →

Recent checks

Checked at (UTC)	Result	Time
2026-09-11T20:30:45Z	HTTP 429 rate-limits datacenter IPs (this checker, CI runners, cloud apps); residential browsers may still get through	375 ms
2026-09-11T20:30:21Z	HTTP 429 rate-limits datacenter IPs (this checker, CI runners, cloud apps); residential browsers may still get through	136 ms
2026-09-11T19:30:43Z	HTTP 429 rate-limits datacenter IPs (this checker, CI runners, cloud apps); residential browsers may still get through	367 ms
2026-09-11T19:30:21Z	HTTP 429 rate-limits datacenter IPs (this checker, CI runners, cloud apps); residential browsers may still get through	149 ms
2026-09-11T18:30:10Z	HTTP 429 rate-limits datacenter IPs (this checker, CI runners, cloud apps); residential browsers may still get through	387 ms
2026-09-11T17:30:22Z	HTTP 429 rate-limits datacenter IPs (this checker, CI runners, cloud apps); residential browsers may still get through	397 ms
2026-09-11T16:30:17Z	HTTP 429 rate-limits datacenter IPs (this checker, CI runners, cloud apps); residential browsers may still get through	407 ms
2026-09-11T13:30:54Z	HTTP 429 rate-limits datacenter IPs (this checker, CI runners, cloud apps); residential browsers may still get through	215 ms
2026-09-11T12:30:45Z	HTTP 429 rate-limits datacenter IPs (this checker, CI runners, cloud apps); residential browsers may still get through	244 ms
2026-09-11T11:30:45Z	HTTP 429 rate-limits datacenter IPs (this checker, CI runners, cloud apps); residential browsers may still get through	292 ms
2026-09-11T10:30:45Z	HTTP 429 rate-limits datacenter IPs (this checker, CI runners, cloud apps); residential browsers may still get through	225 ms
2026-09-11T09:30:45Z	HTTP 429 rate-limits datacenter IPs (this checker, CI runners, cloud apps); residential browsers may still get through	269 ms
2026-09-11T08:30:45Z	HTTP 429 rate-limits datacenter IPs (this checker, CI runners, cloud apps); residential browsers may still get through	266 ms
2026-09-11T07:30:45Z	HTTP 429 rate-limits datacenter IPs (this checker, CI runners, cloud apps); residential browsers may still get through	236 ms
2026-09-11T06:30:45Z	HTTP 429 rate-limits datacenter IPs (this checker, CI runners, cloud apps); residential browsers may still get through	266 ms
2026-09-11T05:31:08Z	OK 200	16 ms
2026-09-11T04:31:07Z	HTTP 429 rate-limits datacenter IPs (this checker, CI runners, cloud apps); residential browsers may still get through	63 ms
2026-09-11T03:31:03Z	OK 200	18 ms
2026-09-11T02:31:07Z	HTTP 429 rate-limits datacenter IPs (this checker, CI runners, cloud apps); residential browsers may still get through	67 ms
2026-09-11T01:31:04Z	OK 200	18 ms
2026-09-11T00:31:07Z	OK 200	16 ms
2026-09-10T23:31:03Z	HTTP 429 rate-limits datacenter IPs (this checker, CI runners, cloud apps); residential browsers may still get through	52 ms
2026-09-10T22:31:05Z	HTTP 429 rate-limits datacenter IPs (this checker, CI runners, cloud apps); residential browsers may still get through	51 ms
2026-09-10T21:31:05Z	HTTP 429 rate-limits datacenter IPs (this checker, CI runners, cloud apps); residential browsers may still get through	68 ms
2026-09-10T20:30:23Z	HTTP 429 rate-limits datacenter IPs (this checker, CI runners, cloud apps); residential browsers may still get through	369 ms
2026-09-10T19:30:23Z	HTTP 429 rate-limits datacenter IPs (this checker, CI runners, cloud apps); residential browsers may still get through	566 ms

Bias disclosure: this page is run by Mockbird, a free hosted mock-API service. The status data is real and logged verbatim (pull it yourself), and the linked guides say when the incumbent wins.