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

GitHub not working for you?

GitHub service health. Issues reported in the last 24 hours

Check 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.

Working Normally
Possible Incident
Confirmed Outage
GitHub Outage Map

View GitHub Reports Map

Track GitHub on your status page

  • Monitor external dependencies in one status page
  • Track status changes in real-time
  • Keep your team or customers informed
  • Create private or public status pages

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

GitHub recent outages and downtime history

IsDown has tracked 741 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. It will show official GitHub outages and also issues that we're started by a spike in crowdsource reports.

Date Incident Duration
Oct 27, 2025
12:25 PM EDT
Minor
Disruption with viewing some repository pages from large organizations
We are currently investigating this issue.
about 1 hour
Oct 24, 2025
05:31 AM EDT
Minor
git operations over ssh seeing increased latency on github.com
We are currently investigating this issue.
40 minutes
Oct 23, 2025
12:33 PM EDT
Minor
Incident with Actions - Larger hosted runners
We are investigating reports of degraded performance for Actions
about 4 hours
Oct 22, 2025
10:29 AM EDT
Minor
Incident with API Requests
We are investigating reports of degraded performance for API Requests
about 1 hour
Oct 21, 2025
12:00 PM EDT
Minor
Disruption with some GitHub services
We are currently investigating this issue.
about 2 hours
Oct 21, 2025
05:12 AM EDT
Minor
Incident with Actions
We are investigating reports of degraded performance for Actions
about 3 hours
Oct 20, 2025
10:46 AM EDT
Minor
Disruption with Grok Code Fast 1 in Copilot
We are investigating reports of degraded performance for Copilot
about 2 hours
Oct 20, 2025
04:56 AM EDT
Major
Codespaces creation failling
We are investigating reports of degraded availability for Codespaces
about 2 hours
Oct 17, 2025
09:11 AM EDT
Major
Disruption with push notifications
We are currently investigating this issue.
about 1 hour
Oct 14, 2025
02:26 PM EDT
Minor
Disruption with some GitHub services
We are currently investigating this issue.
34 minutes
Sign up to check more outage history

Looking to track GitHub outages?

  • Monitor external dependencies in one status page
  • Track status changes in real-time
  • Keep your team or customers informed
  • Create private or public status pages

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

User comments about GitHub status

See what users are saying about GitHub issues that impacted them and how they are affected by the outage. You can see if other users are experiencing the same issues and if there are any workarounds or solutions.

  • Both pull and push are taking a very long time and doing nothing (stuck).

  • Not able to push to Github.com.

  • 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

Active Health Checks

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

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

Users who monitor GitHub status also monitor these services

Users are monitoring tens of services with IsDown. Here are some that are monitored together with GitHub. With IsDown you can get a bird's eye view of all your dependencies and how they are performing.

AWS

AWS

OK
Google Cloud

Google Cloud

OK
Google Workspace

Google Workspace

OK
Cloudflare

Cloudflare

MINOR
Microsoft Azure

Microsoft Azure

OK
Slack

Slack

OK
Datadog US1

Datadog US1

OK
Zoom

Zoom

MAINTENANCE
Figma

Figma

OK
Microsoft 365

Microsoft 365

OK
Adobe

Adobe

MINOR
HubSpot

HubSpot

OK
Aircall

Aircall

OK
Stripe

Stripe

OK
Airtable

Airtable

OK
View all services Start Monitoring Your Dependencies
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%

Start Monitoring Today
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 website.
Check their status page.

159 incidents in 2025

How to monitor the status of GitHub and all your dependencies?

IsDown is a status page aggregator that monitors if GitHub and all your dependencies are experiencing issues. We combine the status of all the services you dependent and provide a clear view of all your vendors health in one place. We not only monitor official information but also crowdsourced reports. That means that even when GitHub, per example, doesn't report an outage, you will still be notified if other users are experiencing issues.

How IsDown monitors GitHub?

IsDown monitors GitHub health in almost real-time

Every few minutes we go to the status page of GitHub (and 4,522+ other services) and check if they are experiencing issues. We collect the status and outage information of GitHub's 11 components. Also, we not only monitor official sources but also user reports. Sometimes or a lot of times vendors take some time to report an incident, so by monitoring user reports we're able to alert you early.

The moment an issue is detected in GitHub, IsDown sends an alert and updates your status page

Not only you will get notified, but IsDown offers notification filters, so you can choose which issues you want to be notified about. This way you avoid getting all the incidents from GitHub and other services.

One status page to monitor all your external dependencies

What you get when monitoring GitHub with IsDown

Track GitHub incidents and downtimes by severity

IsDown checks GitHub official status page for major/minor outages or downtimes. A major outage is when GitHub experiences a critical issue that severely affects one or more services/regions. A minor incident 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. The moment we detect a GitHub outage, we send you an alert and update your dashboard and status page.

Get alerted as soon as users reports problems with GitHub

GitHub and other vendors don't always report outages on time. IsDown collects user reports to provide early detection of outages. This way, even without an official status update, you can stay ahead of possible problems.

All the details of GitHub outages and downtimes

IsDown collects all information from the outages published in GitHub status page to provide the context of the outage. 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.

Prepare for upcoming GitHub maintenance events

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.

Only get alerted on the GitHub outages that impact your business

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.

One platform to monitor all your external dependencies

Our tool was build to be the best way to monitor all your external dependencies in one place. IsDown not only will help you monitor GitHub but also 4,522 other services. Your team and customers will have a clear view of all your dependencies and their status, making it easier to identify and resolve issues.

Monitor GitHub and all your external dependencies in real-time

Add all your dependencies to your dashboard. IsDown will monitor them in real-time and send you alerts when there is an issue. You can also create a status page for a bird-eye view and share it with your team.

Start Monitoring for Free
Monitor GitHub and all your external dependencies in real-time

Get notified imediatelly when there's an issue with GitHub or other services

Not only you will get notified, but IsDown offers notification filters, so you can choose which issues you want to be notified about. This way you avoid getting all the incidents from GitHub and other services.

Start Monitoring for Free
Get notified imediatelly when there's an issue with GitHub or other services

Send outage information from GitHub and other services to your tools

IsDown integrates with 20+ tools. Connect the status of GitHub and 4,522 other vendors to your tools to receive vendor outage alerts exactly where your team needs them.

Start Monitoring for Free
Send outage information from GitHub and other services to your tools

Share GitHub status in your status page

Create a status page that can easily be access by your team and customers. You can make it public or private, and customize it to your needs. This will be your first line of communication when there's the question 'Is GitHub down?'

Start Monitoring for Free
Share GitHub status in your status page

GitHub Downdetector vs IsDown

While Downdetector relies on user-submitted reports to detect GitHub outages, IsDown monitors GitHub's status page for verified, detailed incident information. Here's why official monitoring provides better reliability for your business:

Features
Downdetector
Official GitHub status page monitoring with real-time incident details.
Monitor 4,522+ services including GitHub in a single dashboard.
Instant GitHub outage alerts sent to Slack, Teams, PagerDuty, and more.
Combined monitoring of GitHub official status and user-reported issues.
Maintenance feed for GitHub
Granular alerts filtering by GitHub components and regions.
Start Monitoring GitHub with IsDown

14-day free trial • No credit card required

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 27, 2025 with the title "Disruption with viewing some repository pages from large organizations"

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.

Ready to monitor GitHub and all your external dependencies?

Start Monitoring in 5 minutes

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