caldays vs Footer Year Update

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms149131
P95 · ms675329
Authnonenone
CORSyesno
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 Footer Year Update: common questions

Which is more reliable, caldays or Footer Year Update?

Both are neck-and-neck — caldays and Footer Year Update each measure 100% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, caldays or Footer Year Update?

Footer Year Update has the lower median latency in our checks — caldays responds in 149 ms versus Footer Year Update at 131 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 caldays and Footer Year Update need an API key?

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

Can I call caldays and Footer Year Update from the browser?

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

Are caldays and Footer Year Update free for commercial use?

caldays has unclear commercial terms, and Footer Year Update 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.