Coffee vs Squiggle

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
Authnonenone
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — no API keyFree — no key
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Coffee vs Squiggle: common questions

Which is more reliable, Coffee or Squiggle?

On our scheduled checks, Squiggle leads on measured uptime — Coffee at —% versus Squiggle 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 Coffee and Squiggle need an API key?

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

Can I call Coffee and Squiggle from the browser?

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

Are Coffee and Squiggle free for commercial use?

Coffee has unclear commercial terms, and Squiggle 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.