Bacon Ipsum vs YADG

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

Uptime · 30d
Uptime · 90d99.02%2.9%
Uptime · 30d100%0.0%
P50 · ms3591308
P95 · ms13281359
AuthnoneapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — no key requiredFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Bacon Ipsum vs YADG: common questions

Which is more reliable, Bacon Ipsum or YADG?

On our scheduled checks, Bacon Ipsum leads on measured uptime — Bacon Ipsum at 99.02% versus YADG at 2.9% 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, Bacon Ipsum or YADG?

Bacon Ipsum has the lower median latency in our checks — Bacon Ipsum responds in 359 ms versus YADG at 1308 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 Bacon Ipsum and YADG need an API key?

Bacon Ipsum needs no key, while YADG requires a free API key. If you want to start calling without signup, reach for Bacon Ipsum first.

Can I call Bacon Ipsum and YADG from the browser?

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

Are Bacon Ipsum and YADG free for commercial use?

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