shipapis
StarSubmit an APISubmit API

GitHub Project Issues vs ReqRes

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

APIGitHub Project IssuesHEALTHY90ReqResHEALTHY98
Uptime · 30d
Uptime · 90d99.02%100%
Uptime · 30d98.3%100%
P50 · ms478256
P95 · ms4310582
Authnonenone
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

GitHub Project Issues vs ReqRes: common questions

Which is more reliable, GitHub Project Issues or ReqRes?

On our scheduled checks, ReqRes leads on measured uptime — GitHub Project Issues at 99.02% versus ReqRes at 100% 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, GitHub Project Issues or ReqRes?

ReqRes has the lower median latency in our checks — GitHub Project Issues responds in 478 ms versus ReqRes at 256 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 GitHub Project Issues and ReqRes need an API key?

Neither needs a paid key — GitHub Project Issues is callable with no signup, and ReqRes is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call GitHub Project Issues and ReqRes from the browser?

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

Are GitHub Project Issues and ReqRes free for commercial use?

GitHub Project Issues has unclear commercial terms, and ReqRes 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.