Is LectServe API down?
Current status, daily uptime history and troubleshooting for the LectServe API (Calendar).
Possibly: LectServe's last check failed
Our latest daily check of LectServe (Oct 24, 2026, 12:25 UTC) failed: it answered HTTP 502. One failure can be a blip; the live check below tells you whether it's still failing.
Checking LectServe now…
Sending a request from our server.
LectServe API uptime history
- Uptime
- 2 checks so far
- Last check
- Oct 24, 2026, 12:25 UTC
- Response
- It answered HTTP 502
- Last up
- Not seen up yet
We check LectServe's listed URL (http://www.lectserve.com) once a day. History started when LectServe was first checked, so new entries show fewer than 30 days.
What does HTTP 502 mean? Read the 502 explainer.
LectServe API not working for you?
- 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, LectServe may not allow cross-origin requests. Call it from your server instead.
- LectServe is listed without HTTPS. Browsers block plain-HTTP requests from HTTPS pages (mixed content).
- 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
LectServe API status FAQ
Is LectServe API down right now?
Our latest daily check of LectServe (Oct 24, 2026, 12:25 UTC) failed: it answered HTTP 502. One failure can be a blip; the live check below tells you whether it's still failing. This page also runs a live check from our server when you open it, so you can see whether LectServe is responding at this moment.
How do you check whether LectServe API is up?
Once a day our checker requests LectServe's listed URL (http://www.lectserve.com) 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 LectServe API is down?
Free Calendar APIs that were up at their last check include caldays, CountdownsHQ, The Calendar. See the full list of LectServe alternatives for a comparison.
Why does LectServe API work for others but not for me?
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, LectServe may not allow cross-origin requests. Call it from your server instead. LectServe is listed without HTTPS. Browsers block plain-HTTP requests from HTTPS pages (mixed content).