Is GitHub API Requests Down?

This page shows the live GitHub API Requests status so you can confirm in seconds if GitHub API Requests is down.

Get GitHub API Requests outage alerts in

GitHub API Requests current status

Updated

GitHub API Requests is operational

IsDown pulls data from the official status page every few minutes and collects user-reported GitHub API Requests issues.
Refresh the page to see the latest updates.

GitHub API Requests user-reported issues in the last 24 hours

This chart displays the number of user-reported GitHub API Requests problems 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.

IsDown Logo Third-party monitoring

Stop Juggling Dozens of Status Pages – Monitor Them All in One Place

Monitoring 4000+ third-party services in real-time
Get custom alerts via Slack, Teams, Datadog, etc.
Create public or private status pages
Start Free Trial
14-day free trial · No credit card required
Trusted by thousands of teams

GitHub API Requests outage history

IsDown has tracked 51 incidents for GitHub API Requests since started monitoring GitHub downtimes in April 2020. We are also collecting data from 4000+ services, and normalize the data to give you a clear picture of the impact of the outage.

Sign up and check all outage history

Latest user comments about GitHub API Requests issues

  • P

    Paul

    api.github.com/repos is a 404

  • M

    Moises

    Cant reach api.github.com from Brazil. 20.201.28.148 getting timeout

GitHub API Requests outages in the last 30 days

Number of Incidents

2 issues

Last incident

11 days ago

IsDown Logo Seamless Integrations

Get GitHub outage alerts and updates in your favorite tools

Receive vendor outage notifications where your team already works. Compatible with Slack, Microsoft Teams, PagerDuty, Datadog, Better Stack, Rootly, Incident.io, Statuspage.io, and more.
Never miss an outage
Easy setup · No coding required
Works with your existing stack

Having problems with GitHub API Requests? What can you do?

  1. First, stay calm.

    • We know it's stressful when GitHub API Requests is down, but running around is not going to fix it.
    • Remember that it's normal for services to go down sometimes. It can be for a number of reasons, from maintenance to unexpected issues.
  2. Make a quick evaluation of the impact of the GitHub API Requests outage

    • Try to evaluate the impact of the outage on your business. Is it impacting a majority of your users or just a few?
    • Did GitHub API Requests already acknowledge the issue? And published a status update? (You can find it in the top of the page or in GitHub API Requests status page)
    • If not, understand if other users are also experiencing issues. You can also check this information on the top of the page.
  3. Communicate with your team and users quickly

    • If GitHub API Requests is having problems and impacting your business, it's important to keep your team and users informed.
    • Share this page with your team, so you can start incident response procedures. No need for everyone to go around searching for information. Create a post or a specific channel in your internal communication tools (Slack, Teams, Google Chat, etc.) so you can aggregate all the information in one place.
    • If you have a status page, create a status update to inform your users about the issue. This way they know what's going on and you can avoid a flow of support requests overburding your team.
  4. Understand the root cause

    • After the first communication, let's move on to the next step. Do a more thorough investigation to understand the root cause of the issue and impact.
    • Reach out to the service provider to understand if they are aware of the issue and if they are already working on it. You can reach them in their support channels, or their social media channels if they have any.
  5. Is there any mitigation for the issue?

    • Understand if there are workarounds or mitigations for the issue. Can you use a different provider? Is the switch easy to do? Talk with your team to understand the best course of action.
    • Need to wait on the service provider to fix the issue? Understand if there is a timeline for the fix. Adapt your communication with your team and users to the situation. It's very important to keep everyone informed.
  6. Did GitHub API Requests recover?

    • Continue to monitor the situation. A lot of times, the service can see a brief recovery and declare the issue as resolved, but it can come back. Keep monitor for some time to make sure it's really resolved.
  7. Post-incident analysis

    • Once the issue is resolved, it's important to do a post-incident analysis. Understand what went wrong and if it's possible or needed to do something to prevent it from happening again.
    • Sometimes if it's a critical dependency, you might need to have a backup plan in place to avoid a similar issue.
    • Vendors usually publish post-mortem analysis reports, so keep an eye on their social media channels and website for more information.
  8. Prepare for the next incident, because it will happen again

    • Start monitoring your dependencies. Sign up to IsDown and aggregate all your dependencies status in one place.
    • Nowadays, it's very common to have a lot of dependencies, and keeping an eye on them is not an easy task. IsDown can help you with that, by aggregating and monitoring all dependencies status and alerting you if they are having issues. Create status pages to communicate with your team and users.
    • For a complete overview of GitHub’s status across all services, including repositories, API requests, and workflows, visit the GitHub Status Page on IsDown

Want to be informed about GitHub status changes?

IsDown offers an easy way to monitor GitHub with maximum flexibility

Major Outages Notifications

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.

Minor Outages 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.

Outage Details

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.

Maintenance Feed

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.

Component Filtering

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.

Early Outage Indicators

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.

Frequently Asked Questions

How can I check the current status of GitHub API Requests?

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.

How can I verify if a failed check run is related to an API issue?

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.

How does an API outage impact commit statuses and status checks?

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.

What should I do if my API requests are taking too long to process?

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.

How long does GitHub retain API request data after an outage?

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.

Can I manually retry API requests after a GitHub outage?

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.

Is GitHub API Requests slow today?

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.

How are GitHub API Requests outages detected?

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.

When was the last GitHub API Requests outage?

GitHub API Requests last outage was on April 28, 2025 with the title "Incident with Git Operations, API Requests and Issues"

GitHub not working for you? How do I know if GitHub is down?

  • Check on the top of the page if there are any reported problems by other users.
  • Find their support at their official website.
  • Find their support contact at their official status page.

How IsDown compares to DownDetector?

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.

Never again lose time looking in the wrong place

14-day free trial · No credit card required · No code required