← 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-12T13:30:22Z · checked every hour · OK-rate 24h: 17.1% · 7d: 33.3% · raw JSON · Atom feed of its down/recovered events

Failing streak began 2026-09-12T07:30:21Z (7 hours) · last successful check: 2026-09-12T07:30:12Z

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):

reqres.in status badge

<!-- 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)ResultTime
2026-09-12T13:30:27ZHTTP 429 rate-limits datacenter IPs (this checker, CI runners, cloud apps); residential browsers may still get through217 ms
2026-09-12T13:30:22ZHTTP 429 rate-limits datacenter IPs (this checker, CI runners, cloud apps); residential browsers may still get through417 ms
2026-09-12T12:30:22ZHTTP 429 rate-limits datacenter IPs (this checker, CI runners, cloud apps); residential browsers may still get through380 ms
2026-09-12T12:30:15ZHTTP 429 rate-limits datacenter IPs (this checker, CI runners, cloud apps); residential browsers may still get through384 ms
2026-09-12T11:30:21ZHTTP 429 rate-limits datacenter IPs (this checker, CI runners, cloud apps); residential browsers may still get through233 ms
2026-09-12T11:30:13ZHTTP 429 rate-limits datacenter IPs (this checker, CI runners, cloud apps); residential browsers may still get through977 ms
2026-09-12T10:30:21ZHTTP 429 rate-limits datacenter IPs (this checker, CI runners, cloud apps); residential browsers may still get through257 ms
2026-09-12T10:30:12ZHTTP 429 rate-limits datacenter IPs (this checker, CI runners, cloud apps); residential browsers may still get through378 ms
2026-09-12T09:30:21ZHTTP 429 rate-limits datacenter IPs (this checker, CI runners, cloud apps); residential browsers may still get through176 ms
2026-09-12T09:30:11ZHTTP 429 rate-limits datacenter IPs (this checker, CI runners, cloud apps); residential browsers may still get through438 ms
2026-09-12T08:30:21ZHTTP 429 rate-limits datacenter IPs (this checker, CI runners, cloud apps); residential browsers may still get through278 ms
2026-09-12T08:30:10ZHTTP 429 rate-limits datacenter IPs (this checker, CI runners, cloud apps); residential browsers may still get through448 ms
2026-09-12T07:30:21ZHTTP 429 rate-limits datacenter IPs (this checker, CI runners, cloud apps); residential browsers may still get through256 ms
2026-09-12T07:30:12ZOK 20031 ms
2026-09-12T06:30:23ZHTTP 429 rate-limits datacenter IPs (this checker, CI runners, cloud apps); residential browsers may still get through396 ms
2026-09-12T06:30:21ZHTTP 429 rate-limits datacenter IPs (this checker, CI runners, cloud apps); residential browsers may still get through306 ms
2026-09-12T05:30:24ZHTTP 429 rate-limits datacenter IPs (this checker, CI runners, cloud apps); residential browsers may still get through390 ms
2026-09-12T05:30:21ZHTTP 429 rate-limits datacenter IPs (this checker, CI runners, cloud apps); residential browsers may still get through177 ms
2026-09-12T04:30:21ZHTTP 429 rate-limits datacenter IPs (this checker, CI runners, cloud apps); residential browsers may still get through224 ms
2026-09-12T04:30:17ZHTTP 429 rate-limits datacenter IPs (this checker, CI runners, cloud apps); residential browsers may still get through383 ms
2026-09-12T03:30:21ZHTTP 429 rate-limits datacenter IPs (this checker, CI runners, cloud apps); residential browsers may still get through209 ms
2026-09-12T03:30:16ZHTTP 429 rate-limits datacenter IPs (this checker, CI runners, cloud apps); residential browsers may still get through408 ms
2026-09-12T02:30:21ZOK 20072 ms
2026-09-12T02:30:07ZOK 200426 ms
2026-09-12T01:30:21ZOK 20052 ms
2026-09-12T01:30:09ZOK 200393 ms
2026-09-12T00:30:21ZOK 20057 ms
2026-09-12T00:30:09ZOK 20022 ms
2026-09-11T23:30:40ZHTTP 429 rate-limits datacenter IPs (this checker, CI runners, cloud apps); residential browsers may still get through195 ms
2026-09-11T23:30:21ZHTTP 429 rate-limits datacenter IPs (this checker, CI runners, cloud apps); residential browsers may still get through178 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.