DummyJSON vs GitHub Project Issues

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

Uptime · 30d
Uptime · 90d99.02%99.02%
Uptime · 30d100%98.3%
P50 · ms32478
P95 · ms11134310
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — no keyFree — limits not published
Rate limit100 req/window · 99 remaining · resets 1783510243Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

DummyJSON vs GitHub Project Issues: common questions

Which is more reliable, DummyJSON or GitHub Project Issues?

Both are neck-and-neck — DummyJSON and GitHub Project Issues each measure 99.02% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, DummyJSON or GitHub Project Issues?

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

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

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

Only DummyJSON is browser-friendly — it returns CORS headers over HTTPS. GitHub Project Issues needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are DummyJSON and GitHub Project Issues free for commercial use?

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