Is LurkAPI down?
Current status, daily uptime history and troubleshooting for the LurkAPI (Social).
No, LurkAPI is up
LurkAPI answered our last daily check (Nov 15, 2026, 13:58 UTC) in 1829 ms with HTTP 200.
Checking LurkAPI now…
Sending a request from our server.
LurkAPI uptime history
- Uptime
- 100% of 4 checks
- Last check
- Nov 15, 2026, 13:58 UTC
- Response
- 1829 ms · HTTP 200
- Last up
- Now
We check LurkAPI's listed URL (https://lurkapi.com/docs) once a day. History started when LurkAPI was first checked, so new entries show fewer than 30 days.
LurkAPI not working for you?
- LurkAPI 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 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.
Social APIs up at their last check
- 1
4chan API
Online · 359 msSimple image-based bulletin board dedicated to a variety of topics.
- No API key needed
- 100% uptime (30 days)
- Fast: 359 ms response
- Callable from the browser (CORS)
No authHTTPSCORS - 2
disdex API
Online · 1064 msSearch public Discord servers by name, language, guild tag and size, with member history.
- No API key needed
- 100% uptime (30 days)
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS - 3
Lanyard API
Online · 420 msRetrieve your presence on Discord through an HTTP REST API or WebSocket.
- No API key needed
- 100% uptime (30 days)
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS - 4
HackerNews API
Online · 384 msSocial news for CS and entrepreneurship.
- No API key needed
- 100% uptime (30 days)
- Fast: 384 ms response
- HTTPS
No authHTTPSCORS ? - 5
Bluesky API
Online · 3754 msDecentralized social networking via the AT protocol.
- No API key needed
- 100% uptime (30 days)
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS
LurkAPI status FAQ
Is LurkAPI down right now?
LurkAPI answered our last daily check (Nov 15, 2026, 13:58 UTC) in 1829 ms with HTTP 200. This page also runs a live check from our server when you open it, so you can see whether LurkAPI is responding at this moment.
How do you check whether LurkAPI is up?
Once a day our checker requests LurkAPI's listed URL (https://lurkapi.com/docs) 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.
How reliable is LurkAPI?
LurkAPI answered 100% of our last 4 daily checks. Above 99% is excellent for a free API; below 95% means you should cache responses and keep a fallback ready.
What can I use if LurkAPI is down?
Free Social APIs that were up at their last check include 4chan, disdex, Lanyard. See the full list of LurkAPI alternatives for a comparison.
Why does LurkAPI work for others but not for me?
LurkAPI 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 it works from one network but not another, check firewalls, VPNs and regional blocks.