Is Yes No API down?
Current status, daily uptime history and troubleshooting for the Yes No API (Test Data).
No, Yes No is up
Yes No answered our last daily check (Oct 24, 2026, 12:25 UTC) in 923 ms with HTTP 200.
Checking Yes No now…
Sending a request from our server.
Yes No API uptime history
- Uptime
- 2 checks so far
- Last check
- Oct 24, 2026, 12:25 UTC
- Response
- 923 ms · HTTP 200
- Last up
- Now
We check Yes No's listed URL (https://yesno.wtf/api) once a day. History started when Yes No was first checked, so new entries show fewer than 30 days.
Yes No API not working for you?
- A 429 response means you're being rate-limited. Slow down, cache responses, and respect any Retry-After header.
- If calls fail only in the browser with a CORS error, Yes No may not allow cross-origin requests. Call it from your server instead.
- 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
Yes No API status FAQ
Is Yes No API down right now?
Yes No answered our last daily check (Oct 24, 2026, 12:25 UTC) in 923 ms with HTTP 200. This page also runs a live check from our server when you open it, so you can see whether Yes No is responding at this moment.
How do you check whether Yes No API is up?
Once a day our checker requests Yes No's listed URL (https://yesno.wtf/api) 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 Yes No API is down?
Free Test Data APIs that were up at their last check include AddressMock, DummyJSON, flaky. See the full list of Yes No alternatives for a comparison.
Why does Yes No API work for others but not for me?
A 429 response means you're being rate-limited. Slow down, cache responses, and respect any Retry-After header. If calls fail only in the browser with a CORS error, Yes No may not allow cross-origin requests. Call it from your server instead. If it works from one network but not another, check firewalls, VPNs and regional blocks.