Bluesky vs Namedays 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 — public AppView, no keyFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Bluesky vs Namedays Calendar: common questions

Which is more reliable, Bluesky or Namedays Calendar?

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

Neither needs a paid key — Bluesky 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 Bluesky and Namedays Calendar from the browser?

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

Bluesky 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.