caldays vs Hebrew Calendar

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 — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

caldays vs Hebrew Calendar: common questions

Which is more reliable, caldays or Hebrew Calendar?

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

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

Can I call caldays and Hebrew Calendar from the browser?

Yes — both caldays and Hebrew Calendar 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 caldays and Hebrew Calendar free for commercial use?

caldays has unclear commercial terms, and Hebrew Calendar 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.