Is GitHub Down? Check current status

Check if GitHub is down, official outages, user-reported issues, and outages map.

Current GitHub status

GitHub is working normally

Updated from GitHub official status page

Having problems with GitHub?

GitHub service health. Issues reported in the last 24 hours

Working Normally
Possible Incident
Confirmed Outage

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. Sign up for free to see more GitHub status data.

Recent GitHub Outages and Downtime History

IsDown has tracked 732 incidents since started monitoring GitHub status in April 2020. We collect data from 4522+ services, and normalize the data to give you a clear picture of the impact of the outage.

Date Incident Duration
Oct 14, 2025
02:26 PM EDT
Minor
We are currently investigating this issue.
34 minutes
Oct 14, 2025
10:05 AM EDT
Minor
We are investigating reports of degraded performance for Copilot
about 2 hours
Oct 09, 2025
10:45 AM EDT
Major
We are investigating reports of degraded availability for Webhooks
about 2 hours
Oct 09, 2025
09:52 AM EDT
Minor
We are currently investigating this issue.
7 minutes
Oct 07, 2025
03:48 PM EDT
Minor
We are currently investigating this issue.
about 4 hours
Oct 07, 2025
01:03 PM EDT
Not Confirmed by GitHub
Possible Outage Indicated by User Reports
about 1 hour
Oct 02, 2025
10:41 PM EDT
Minor
We are investigating reports of degraded performance for Copilot
about 1 hour
Oct 01, 2025
12:43 PM EDT
Minor
We are investigating reports of degraded performance for Copilot
1 day
Oct 01, 2025
03:59 AM EDT
Minor
We are currently investigating this issue.
about 9 hours
Sep 29, 2025
02:39 PM EDT
Minor
We are currently investigating this issue.
35 minutes
Sign up to check more outage history
The Status Page Aggregator Built for IT Teams

One place to monitor all your cloud vendors. Get instant alerts when an outage is detected.

Try IsDown risk-free 14-day free trial · No credit card required

User comments about problems with GitHub

  • Repository access denied.

  • Repository access denied.

  • Repository access denied.

  • Actions not running.

  • Repository access denied.

  • Mike - Very slow connecting to github codespaces in West Europen region. Code modules will not run when eventually connected..

    Codespaces
  • Push/pull failures.

  • Copilot response failure.

  • Michael - Codespace is stuck at ShuttingDown for the past hour, and every attempt to export fails. PS C:\Users\michaeljo> gh codespace list organic-goggles-q79x465vrxvgc47v5 organic goggles office-fuel/1JSBridgeRepo codespace_midgard_fullclone ShuttingDown.

  • Josh - Reason: Server error: 500.

    Copilot
  • Guy - no conversations load and you can not select a model to use.

    Copilot
  • Gabriel - not able to login in vscode.

    Copilot
  • Bendik - Sorry, your request failed. Please try again. Request id: c06351fd-c2ba-4c10-8995-6917cbfe016f Reason: Server error: 500 Sorry, your request failed. Please try again. Request id: 41735d3d-bc63-444e-bb66-27242261af74 Reason: token expired or invalid: 403.

    Copilot
  • Ricardo - GitHub API rate limit exceeded. Please wait and try again..

    Copilot
  • Thom - unable to access github copilot in visual studio 22.

    Copilot
  • Victor - Github Copilot extension for VSCode stopped working. Every time I send a new chat request it tells me that there's an error with the request due to invalid token..

    Copilot
  • Anthony - Sorry, your request failed. Please try again. Request id: a32d868c-7f5b-45e5-9ab1-6f12c216b2b0 Reason: token expired or invalid: 403.

    Copilot
  • Manish - Sorry, your request failed. Please try again. Request id: 2529862d-d24e-4783-9386-80eaff9cbead Reason: token expired or invalid: 403.

    Copilot
  • Polde - Sorry, your request failed. Please try again. Request id: Reason: token expired or invalid: 403.

    Copilot
  • Vinicius - Sorry, your request failed. Please try again. Reason: token expired or invalid: 403.

    Copilot
  • Miguel - Sorry, your request failed. Please try again. Reason: Token expired or invalid: 403.

    Copilot
  • Kyle - Sorry, your request failed. Please try again. Request id: e7078385-9d81-4451-9e63-f74da4761561 Reason: token expired or invalid: 403.

    Copilot
  • Mary - Sorry, your request failed. Please try again. Request id: [redacted] Reason: token expired or invalid: 403.

    Copilot
  • chris - Getting 403 error in github copiliot.

    Copilot
  • lucas - Errors due to token issues.

    Copilot
  • Ryan - I get this across all models Sorry, your request failed. Please try again. Request id: ### Reason: token expired or invalid: 403.

    Copilot
  • Bilbo - Sorry, your request failed. Please try again. Request id: Reason: token expired or invalid: 403.

    Copilot
  • Yaroslav - Getting a generic error in a Jetbrains IDE.

    Copilot
  • Jeff - token expired or invalid: 403.

    Copilot
  • Peter - GitHub API rate limit exceeded. Please wait and try again..

    Copilot
  • Giray - Sorry, your request failed. Please try again. Request id: xxx Reason: token expired or invalid: 403.

    Copilot
  • Tanvish - Sorry, your request failed. Please try again. Request id: xxxxx Reason: token expired or invalid: 403.

    Copilot
  • Philip - CoPilot is not responding. (Conversation sidebar is flashing gray) .

    Copilot
  • Son - Copilot functionaliy does not work in VSCode.

    Copilot
  • Mark - Copilot chat in intellij is blank screen.

    Copilot
  • Niels - Tasks couldn’t be loaded Try again or, if the problem persists, contact support. GitHub status.

    Copilot
  • Ezequiel - Request Failed: 400 {"error":{"message":"tools.0.custom.input_schema: JSON schema is invalid. It must match JSON Schema draft 2020-12 (https://json-schema.org/draft/2020-12). Learn more about tool use at https://docs.anthropic.com/en/docs/tool-use.","code":"invalid_request_body"}}.

    Copilot
  • Igor - Can't submit CR feedback in GitHub PR as well as submit it to the file. "Error I'm sorry but there was an error. Please try again." .

    Copilot
  • Colin - An error occurred while processing your request, please try again later.

    Copilot
  • Aryan - It is timing out and telling me to try again and hanging in vs code.

    Copilot
  • Alex - Agent mode does not work, getting "an error has occurered".

    Copilot
  • Rich - API rate limit exceeded for user ID 678094 (but not even using it).

    Copilot
  • Aysel - GitHub Copilot It is not working.

    Copilot
  • Anonymous - "Sorry, no response was returned.".

    Copilot
  • Robert - Can't login to the site or use Copilot in VS Code..

  • AJ - service not working with VSCode.

    Copilot
  • Neo - https://github.com/settings/copilot/features site and copilot extension for VS Code is down..

    Copilot
  • Henrique - The Copilot page is returning an error, and Visual Studio Code displays the following message: “Please contact your enterprise admin to enable your managed account for Copilot Business.”.

    Copilot
  • Juan - It's not working in VS Code. Copilot settings page in GitHub redirects to error page..

    Copilot
  • JKlein - Not launching in VSCode and Support page is down.

    Copilot
  • ADam - Copilto down, says to contact support..

    Copilot
  • erik - says contact support. Cannot access my copilot page.

    Copilot
  • Paul - No Copilot subscription found. WTF?.

    Copilot
  • Anon - logged off copilot, can't log back in.

    Copilot
  • Axel - Cant access the tool neither the copilot page on github.com.

    Copilot
  • Nicolas - 500 error on any copilot query.

    Copilot
  • Ed - GitHub Copilot does not work. Says I need to contact support..

    Copilot
  • Pavel - Copilot failed to get a response. Please try again..

  • vvenaya - cannot log into copilot inside visual studio 2022.

    Copilot
  • max - not responding, says 'contact support'.

    Copilot

GitHub status page - All services & components

Active Health Checks

IsDown actively monitors the health of GitHub and several major components.

Main Site
Last checked: 1 minute ago
OK
Gists
Last checked: 1 minute ago
OK
LFS Objects, Actions Artifacts, Avatars
Last checked: 1 minute ago
OK
ZIP/TAR archive downloads
Last checked: 1 minute ago
OK
REST API
Last checked: 1 minute ago
OK
Raw file delivery
Last checked: 5 minutes ago
OK
GraphQL
Last checked: 1 minute ago
OK
IsDown Logo

The Status Page Aggregator Built for IT Teams

Unified vendor dashboard

4522+ third-party services available to monitor

Early Outage Detection

Alerts 30+ minutes before official updates

Stop the Support Flood

Cut "is it down?" tickets by 80%

14-day free trial • No credit card required

GitHub is a web-based version control and collaboration platform for software developers, offering tools like issue tracking, pull requests, and actions for CI/CD.

Monitoring GitHub since April 2020

Tracking 11 GitHub services and regions

Need help? Try here:
Support at official website.
Check their official status page.

150 incidents in 2025

Frequently Asked Questions

How can I resolve issues when GitHub is down?

When GitHub is down, start by checking the official status page and IsDown's monitoring. If PRs, repository access, or deployment processes are affected, try using alternative workflows. If it's a network or connectivity issue, verify whether it's on GitHub's end or a local problem by testing a different network or clearing the DNS cache.

Keeping track of GitHub status updates helps in understanding the outage. In cases of widespread disruptions, teams can mitigate the impact by delaying non-critical tasks or working offline until service is restored.

How does IsDown notify users about GitHub outages?

IsDown provides real-time alerts when GitHub experiences disruptions. Users can set up notifications via Slack, PagerDuty, or email to stay informed. Whether it's a network problem, database failure, or deployment delay, IsDown keeps users updated. Tracking GitHub status checks ensures teams are aware of potential service interruptions before they escalate.

Can GitHub outages impact development workflows?

Yes, when GitHub experiences an outage, it can significantly disrupt software development workflows. Developers may be unable to push code, merge pull requests (PRs), or access repositories. This can delay releases, hinder collaboration, and affect automation pipelines, particularly in DevOps and CI/CD environments where GitHub is integrated with build and deployment processes.

What are common causes of GitHub outages?

GitHub outages can be caused by infrastructure failures, database issues, network congestion, or planned/unplanned system maintenance. Problems with query performance, API rate limits, or repository indexing may slow down searches and repository access. To determine whether an issue is widespread or isolated, developers should check GitHub's official status page and third-party monitoring platforms like IsDown for real-time outage reports.

How can teams mitigate the impact of GitHub downtime?

To reduce the impact of GitHub downtime, teams should implement contingency workflows. This may include maintaining local repositories for offline work, setting up alternative version control systems (e.g., GitLab, Bitbucket), or using mirrored repositories. For CI/CD pipelines, integrating multiple service providers can ensure redundancy. Regularly monitoring GitHub status updates allows teams to react proactively and adjust workflows as needed.

Is GitHub down today or just slow?

Currently there's no report of GitHub being slow. Check on the top of the page if there are any reported problems by other users.

How are GitHub outages detected?

IsDown monitors the GitHub 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.

Is GitHub having an outage right now?

GitHub last outage was on October 14, 2025 with the title "Disruption with some GitHub services"

How to check if GitHub is down?

Why use IsDown to monitor GitHub instead of the official status page?

Because IsDown is a status page aggregator, which means that we aggregate the status of multiple cloud services. You can monitor GitHub and all the services that impact your business. Get a dashboard with the health of all services and status updates. Set up notifications via Slack, Datadog, PagerDuty, and more, when a service you monitor has issues or when maintenances are scheduled.

How IsDown compares to DownDetector when monitoring GitHub?

IsDown and DownDetector help users determine if GitHub 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 instead of just relying on reports from users. The integration allows us to provide more details about GitHub's Outages, 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.

How IsDown works?

  1. IsDown monitors official status pages

    We check the status of the services you're monitoring every few minutes. We aggregate the status and outage information and normalize it. We also collect crowdsourced information to provide early warning signs.

  2. We notify you when there is an outage

    We send you an alert whenever we detect a new incident or an update on the status of the services you're monitoring. You can customize the alerts to your needs to avoid alert fatigue.

  3. Dedicated dashboard and integrations

    Aggregate all the status information in a straightforward dashboard or internal status page. You can also send the information and alerts to your team's communication/monitoring/incident management tools, such as Slack, Datadog, Microsoft Teams, PagerDuty, and more.

Want to be informed about GitHub status changes?

IsDown offers an easy way to monitor GitHub with maximum flexibility

Major Outages Notifications

IsDown monitors GitHub for major outages. A major outage is when GitHub 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 GitHub 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 Detection

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.

Latest Articles from our Blog

See all the blog articles

Never again lose time looking in the wrong place

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