Hebrew Calendar vs Namedays Calendar

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

Uptime · 30d
Uptime · 90d100%91.2%
Uptime · 30d100%85.0%
P50 · ms533480
P95 · ms20162749
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublished60 req/window · 58 remaining
In directory since2026-07-052026-07-05
operationalpartialdownno data

Hebrew Calendar vs Namedays Calendar: common questions

Which is more reliable, Hebrew Calendar or Namedays Calendar?

On our scheduled checks, Hebrew Calendar leads on measured uptime — Hebrew Calendar at 100% versus Namedays Calendar at 91.2% 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, Hebrew Calendar or Namedays Calendar?

Namedays Calendar has the lower median latency in our checks — Hebrew Calendar responds in 533 ms versus Namedays Calendar at 480 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 Hebrew Calendar and Namedays Calendar need an API key?

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

Can I call Hebrew Calendar and Namedays Calendar from the browser?

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

Are Hebrew Calendar and Namedays Calendar free for commercial use?

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