shipapis
StarSubmit an APISubmit API

24 Pull Requests vs DownStatus

Same instrument, two spec sheets — measured, not claimed.

API24 Pull RequestsHEALTHY90DownStatusDYING73
Uptime · 30d
Uptime · 90d100%60.8%
Uptime · 30d100%33.3%
P50 · ms678589
P95 · ms27851295
Authnonenone
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — no API key (per docs)
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

24 Pull Requests vs DownStatus: common questions

Which is more reliable, 24 Pull Requests or DownStatus?

On our scheduled checks, 24 Pull Requests leads on measured uptime — 24 Pull Requests at 100% versus DownStatus at 60.8% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Which is faster, 24 Pull Requests or DownStatus?

DownStatus has the lower median latency in our checks — 24 Pull Requests responds in 678 ms versus DownStatus at 589 ms (P50). Tail latency (P95) is in the table above; for most workloads the median is the number that shapes how the API feels.

Do 24 Pull Requests and DownStatus need an API key?

Neither needs a paid key — 24 Pull Requests is callable with no signup, and DownStatus is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call 24 Pull Requests and DownStatus from the browser?

Neither sends browser-friendly CORS headers reliably, so call 24 Pull Requests and DownStatus from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

Are 24 Pull Requests and DownStatus free for commercial use?

24 Pull Requests has unclear commercial terms, and DownStatus has unclear commercial terms. We track service terms and the data license as separate fields — see the Commercial use and Data license rows above, and confirm both before shipping either in a paid product.