Is FakeJSON API down?
Current status, daily uptime history and troubleshooting for the FakeJSON API (Test Data).
Possibly: FakeJSON's last check failed
Our latest daily check of FakeJSON (Oct 24, 2026, 12:25 UTC) failed: its TLS certificate chain is incomplete. One failure can be a blip; the live check below tells you whether it's still failing.
Checking FakeJSON now…
Sending a request from our server.
FakeJSON API uptime history
- Uptime
- 2 checks so far
- Last check
- Oct 24, 2026, 12:25 UTC
- Response
- Its TLS certificate chain is incomplete
- Last up
- Not seen up yet
We check FakeJSON's listed URL (https://fakejson.com) once a day. History started when FakeJSON was first checked, so new entries show fewer than 30 days.
FakeJSON API not working for you?
- FakeJSON needs an API key. A 401 or 403 usually means a missing, expired or mis-sent credential: check whether it belongs in a header or the query string.
- A 429 response means you're being rate-limited. Slow down, cache responses, and respect any Retry-After header.
- If it works from one network but not another, check firewalls, VPNs and regional blocks.
- Check the provider's documentation, status page or social accounts for planned maintenance or a changed endpoint.
Test Data APIs up at their last check
- 1
AddressMock API
Online · 784 msRandom US, Hong Kong and Cape Verde addresses with matched city, state and ZIP.
- No API key needed
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS - 2
DummyJSON API
Online · 789 msFake REST API with products, users, posts, comments, todos and more.
- No API key needed
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS - 3
flaky API
Online · 1050 msFake REST API with chaos controls: force any status code, add latency, or a failure rate.
- No API key needed
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS - 4
loremfile API
Online · 924 msHotlinkable CC0 sample files in 78 formats, each with a SHA-256 in a JSON manifest.
- No API key needed
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS - 5
Supercrontab Mock Endpoints API
Online · 822 msMock endpoints in 8 formats, each returning any of 14 HTTP status codes.
- No API key needed
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS
FakeJSON API status FAQ
Is FakeJSON API down right now?
Our latest daily check of FakeJSON (Oct 24, 2026, 12:25 UTC) failed: its TLS certificate chain is incomplete. One failure can be a blip; the live check below tells you whether it's still failing. This page also runs a live check from our server when you open it, so you can see whether FakeJSON is responding at this moment.
How do you check whether FakeJSON API is up?
Once a day our checker requests FakeJSON's listed URL (https://fakejson.com) and records whether it answers within 15 seconds. Answers like 401 (needs a key), 403 (blocks bots) or 429 (rate-limited) count as up, because the server responded. The listed URL is often the documentation page, so an API endpoint can occasionally fail while its docs stay up.
What can I use if FakeJSON API is down?
Free Test Data APIs that were up at their last check include AddressMock, DummyJSON, flaky. See the full list of FakeJSON alternatives for a comparison.
Why does FakeJSON API work for others but not for me?
FakeJSON needs an API key. A 401 or 403 usually means a missing, expired or mis-sent credential: check whether it belongs in a header or the query string. A 429 response means you're being rate-limited. Slow down, cache responses, and respect any Retry-After header. If it works from one network but not another, check firewalls, VPNs and regional blocks.