Bacon Ipsum vs DummyJSON

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — no key requiredFree — no key
Rate limitUnpublished100 req/window · 99 remaining · resets 1783510243
In directory since2026-07-052026-07-05
operationalpartialdownno data

Bacon Ipsum vs DummyJSON: common questions

Which is more reliable, Bacon Ipsum or DummyJSON?

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

Do Bacon Ipsum and DummyJSON need an API key?

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

Can I call Bacon Ipsum and DummyJSON from the browser?

Yes — both Bacon Ipsum and DummyJSON send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

Are Bacon Ipsum and DummyJSON free for commercial use?

Bacon Ipsum has unclear commercial terms, and DummyJSON 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.