Live GitHub API Requests status. See if GitHub API Requests is down, view recent outages, and get real-time alerts when problems start.
GitHub API Requests is operational
IsDown pulls data from GitHub's status page every few minutes and collects user-reported issues. Refresh the page to see if there are any updates.
This chart displays the number of user-reported issues over the past 24 hours, grouped into 20-minute intervals. It's normal to see occasional reports, which may be due to individual user issues rather than a broader problem. We only consider an issue widespread if there are multiple reports within a short timeframe.
IsDown has tracked 54 incidents for GitHub API Requests since started monitoring GitHub status in April 2020. We collect data from 4200+ services, and normalize the data to give you a clear picture of the impact of the outage.
3 days ago · lasted about 2 hours
We are investigating reports of degraded performance for API Requests and Git Operations
3 days ago · lasted about 3 hours
We are investigating reports of degraded performance for API Requests and Git Operations
6 days ago · lasted 15 minutes
We are currently investigating this issue.
We've tracked and collected 54 incidents for GitHub API Requests since started monitoring GitHub status
Join companies like Adobe, Coursera, and Glassdoor that use IsDown to monitor their vendors.
Paul
api.github.com/repos is a 404
Moises
Cant reach api.github.com from Brazil. 20.201.28.148 getting timeout
Be the first to know when GitHub and other third-party services go down
Services commonly monitored together with GitHub
You can check the GitHub API Requests status page on IsDown to monitor any ongoing outages or disruptions. Additionally, you can visit the official GitHub status page to verify if API-related issues have been reported. If your API requests are failing, review your REST API endpoints, check your commit statuses, and inspect recent check runs for failures.
If a check run fails unexpectedly, check if the REST API endpoints for check are responsive. API-related outages can prevent GitHub Actions from executing properly, affect status checks, or delay commit statuses from updating. You can also use the REST API to interact with the logs and investigate the failure.
If GitHub API Requests are down, commit statuses and status checks may not update in real time. This can delay check runs and requested actions, causing unexpected failures in check suites. Developers can monitor API health through the GitHub REST API documentation or use the API endpoints for commit statuses to track updates.
If your API requests are delayed, it could be due to REST API endpoint congestion, high system load, or an ongoing GitHub issue. Monitor the results to fetch from GitHub's response headers and optimize your queries by targeting specific lines of code rather than requesting an entire repository.
GitHub follows retention of checks policies, meaning API logs, commit statuses, and check runs may be archived after a certain period. If you need to retrieve past request logs, you can access them through the REST API to manage checks, the checks tab in the GitHub UI, or the REST API endpoints for commit.
Yes, if an API outage has affected your requests, you can retry them manually once the service is restored. Developers can use the REST API to manage checks, reprocess failed check suites, or trigger a check run endpoint to resume workflows. If needed, you can also create a check run to validate a pending process.
Currently there's no report of GitHub API Requests being slow. Check on the top of the page if there are any reported problems by other users.
IsDown monitors the GitHub API Requests official status page every few minutes. We also get reports from users like you. If there are enough reports about an outage, we'll show it on the top of the page.
GitHub API Requests last outage was on May 26, 2025 with the title "We're experiencing errors"
IsDown and DownDetector help users determine if a service is having problems. The big difference is that IsDown is a status page aggregator. IsDown monitors a service's official status page to give our customers a more reliable source of information. The integration allows us to provide more details about the outage, like incident title, description, updates, and the parts of the affected service. Additionally, users can create internal status pages and set up notifications for all their third-party services.
IsDown offers an easy way to monitor GitHub with maximum flexibility
IsDown monitors API Requests for major outages. A major outage is when API Requests experiences a critical issue that severely affects one or more services/regions. When GitHub marks an incident as a major outage, IsDown updates its internal status, the customer status page and dashboard. Depending on the customer settings, IsDown will also send notifications.
IsDown monitors GitHub status page for minor outages. A minor outage is when API Requests experiences a small issue affecting a small percentage of its customer's applications. An example is the performance degradation of an application. When a minor outage occurs, IsDown updates its internal status and shares that information on the customer status page. Depending on the customer settings, IsDown will also send notifications.
IsDown collects all information from the outages published in GitHub status page to provide the most accurate information. If available, we gather the title, description, time of the outage, status, and outage updates. Another important piece of information is the affected services/regions which we use to filter the notifications that impact your business.
GitHub publishes scheduled maintenance events on their status page. IsDown collects all the information for each event and creates a feed that people can follow to ensure they are not surprised by unexpected downtime or problems. We also send the feed in our weekly report, alerting the next maintenances that will take place.
IsDown monitors GitHub and all their 11 components that can be affected by an outage. IsDown allows you to filter the notifications and status page alerts based on the components you care about. For example, you can choose which components or regions affect your business and filter out all other outages. This way you avoid alert fatigue in your team.
GitHub and other vendors don’t always report outages on time. Our crowdsourced status platform helps you stay ahead of outages. Users report issues and outages, sharing details on what problems they are facing. We use that info to provide early signs of outages. This way, even without an official update, you can stay ahead of possible problems.
14-day free trial · No credit card required · No code required
Slack
Teams
Datadog
PagerDuty
