Is GitHub ReadMe Stats API down?
Current status, daily uptime history and troubleshooting for the GitHub ReadMe Stats API (Open Source Projects).
No, GitHub ReadMe Stats is up
GitHub ReadMe Stats answered our last daily check (Oct 24, 2026, 12:25 UTC) in 729 ms with HTTP 200.
Checking GitHub ReadMe Stats now…
Sending a request from our server.
GitHub ReadMe Stats API uptime history
- Uptime
- 2 checks so far
- Last check
- Oct 24, 2026, 12:25 UTC
- Response
- 729 ms · HTTP 200
- Last up
- Now
We check GitHub ReadMe Stats's listed URL (https://github.com/anuraghazra/github-readme-stats) once a day. History started when GitHub ReadMe Stats was first checked, so new entries show fewer than 30 days.
GitHub ReadMe Stats 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 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.
Open Source Projects APIs up at their last check
- 1
GitHub Contribution Chart Generator API
Online · 657 msCreate an image of your GitHub contributions.
- No API key needed
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS - 2
Metabase API
Online · 650 msAn open source Business Intelligence server to share data and analytics inside your company.
- No API key needed
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS - 3
Evil Insult Generator API
Online · 1098 msEvil Insults. A free open source projects API by Evil Insult Generator.
- No API key needed
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS - 4
Neuronto ARD Registry API
Online · 766 msSearch index of MCP servers, agents and APIs, with the tools each server actually exposes.
- No API key needed
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS - 5
Drupal.org API
Online · 77 msDrupal.org. A free open source projects API by drupal.org.
- No API key needed
- Fast: 77 ms response
- HTTPS
No authHTTPSCORS ?
Compare all GitHub ReadMe Stats alternatives · APIs down right now
GitHub ReadMe Stats API status FAQ
Is GitHub ReadMe Stats API down right now?
GitHub ReadMe Stats answered our last daily check (Oct 24, 2026, 12:25 UTC) in 729 ms with HTTP 200. This page also runs a live check from our server when you open it, so you can see whether GitHub ReadMe Stats is responding at this moment.
How do you check whether GitHub ReadMe Stats API is up?
Once a day our checker requests GitHub ReadMe Stats's listed URL (https://github.com/anuraghazra/github-readme-stats) 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 GitHub ReadMe Stats API is down?
Free Open Source Projects APIs that were up at their last check include GitHub Contribution Chart Generator, Metabase, Evil Insult Generator. See the full list of GitHub ReadMe Stats alternatives for a comparison.
Why does GitHub ReadMe Stats 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 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.