Is Checkiday - National Holiday API down?
Current status, daily uptime history and troubleshooting for the Checkiday - National Holiday API (Calendar).
No, Checkiday - National Holiday is up
Checkiday - National Holiday answered our last daily check (Oct 24, 2026, 12:25 UTC) in 1152 ms with HTTP 200.
Checking Checkiday - National Holiday now…
Sending a request from our server.
Checkiday - National Holiday API uptime history
- Uptime
- 2 checks so far
- Last check
- Oct 24, 2026, 12:25 UTC
- Response
- 1152 ms · HTTP 200
- Last up
- Now
We check Checkiday - National Holiday's listed URL (https://apilayer.com/marketplace/checkiday-api) once a day. History started when Checkiday - National Holiday was first checked, so new entries show fewer than 30 days.
Checkiday - National Holiday API not working for you?
- Checkiday - National Holiday needs an API key. A 401 or 403 usually means a missing, expired or mis-sent credential: check whether it belongs in a header or the query string.
- A 429 response means you're being rate-limited. Slow down, cache responses, and respect any Retry-After header.
- If calls fail only in the browser with a CORS error, Checkiday - National Holiday may not allow cross-origin requests. Call it from your server instead.
- If it works from one network but not another, check firewalls, VPNs and regional blocks.
- Check the provider's documentation, status page or social accounts for planned maintenance or a changed endpoint.
Calendar APIs up at their last check
- 1
caldays API
Online · 867 msPublic holidays for 195+ countries.
- No API key needed
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS - 2
CountdownsHQ API
Online · 623 msDates and timezone-correct countdowns for 150+ holidays and observances in 18 countries.
- No API key needed
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS - 3
The Calendar API
Online · 643 msPublic holidays for US states and 30 countries plus sports and finance calendars as static JSON.
- No API key needed
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS - 4
UK Bank Holidays API
Online · 62 msBank holidays in England and Wales, Scotland and Northern Ireland.
- No API key needed
- Fast: 62 ms response
- Returns JSON at its URL
- HTTPS
No authHTTPSCORS ? - 5
India Public Holidays API
Online · 459 msOfficial Indian public holidays for the Central government and 36 states/UTs.
- No API key needed
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS
Compare all Checkiday - National Holiday alternatives · APIs down right now
Checkiday - National Holiday API status FAQ
Is Checkiday - National Holiday API down right now?
Checkiday - National Holiday answered our last daily check (Oct 24, 2026, 12:25 UTC) in 1152 ms with HTTP 200. This page also runs a live check from our server when you open it, so you can see whether Checkiday - National Holiday is responding at this moment.
How do you check whether Checkiday - National Holiday API is up?
Once a day our checker requests Checkiday - National Holiday's listed URL (https://apilayer.com/marketplace/checkiday-api) and records whether it answers within 15 seconds. Answers like 401 (needs a key), 403 (blocks bots) or 429 (rate-limited) count as up, because the server responded. The listed URL is often the documentation page, so an API endpoint can occasionally fail while its docs stay up.
What can I use if Checkiday - National Holiday API is down?
Free Calendar APIs that were up at their last check include caldays, CountdownsHQ, The Calendar. See the full list of Checkiday - National Holiday alternatives for a comparison.
Why does Checkiday - National Holiday API work for others but not for me?
Checkiday - National Holiday needs an API key. A 401 or 403 usually means a missing, expired or mis-sent credential: check whether it belongs in a header or the query string. A 429 response means you're being rate-limited. Slow down, cache responses, and respect any Retry-After header. If calls fail only in the browser with a CORS error, Checkiday - National Holiday may not allow cross-origin requests. Call it from your server instead.