Arbeitnow vs Church Calendar

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

Uptime · 30d
Uptime · 90d93.1%100%
Uptime · 30d90.0%100%
P50 · ms303848
P95 · ms41621997
Authnonenone
CORSyesyes
HTTPSyesno
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — no key requiredFree — limits not published
Rate limit5 req/window · 4 remainingUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Arbeitnow vs Church Calendar: common questions

Which is more reliable, Arbeitnow or Church Calendar?

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

Arbeitnow has the lower median latency in our checks — Arbeitnow responds in 303 ms versus Church Calendar at 848 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 Arbeitnow and Church Calendar need an API key?

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

Can I call Arbeitnow and Church Calendar from the browser?

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

Are Arbeitnow and Church Calendar free for commercial use?

Arbeitnow has unclear commercial terms, and Church 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.