isitdownrightnow.app
  1. Home
  2. Services
  3. GitHub
GitHub github.com

Is GitHub down right now? Live status and outage tracker

No, GitHub is up.

No widespread outage detected. 1 user report in the last hour is within the normal range.

GitHub's own status page: www.githubstatus.com

Live Last spike Data refreshes every 5 minutes
Not working for you? Official status pageStatus page
User reports, last 24 hours, 15 minutes a segment: 96 flowing, 0 slow (elevated), 0 jammed (outage)

User reports, last 24 hours

79 reports in total, counted in 15-minute windows

In the last hour, 1 problem report came in for GitHub, against about 13 at this time on a usual day. Over the last 24 hours there were 79 reports. Worldwide, most recent reports were about website (70%) and app (26%). The last spike in reports was 26 h ago and lasted 51 min. These are user reports from the US, where most people report GitHub problems.

Around the world right now: normal in 71 other countries. Most reports in the last hour: Brazil 1 · India 1 · Canada 1. By country

In the past 24 hours, 79 user reports came in for GitHub. Counting only the 15-minute windows with a spike big enough to count as an outage, that comes to 100.00% uptime for the day. The busiest 15-minute window had 5 reports, about 20 hours ago. That stays below our outage threshold, so it doesn't count as downtime.
Reports, last hour
1
86% on the hour before
Uptime, 24 h
100.00%
No outage windows
Last outage
None
In the last 24 hours
Busiest 15 minutes
5
5 reports, 20 h ago
Last 24 hours

GitHub outages and problems

In the past 24 hours, 79 user reports came in for GitHub. Counting only the 15-minute windows with a spike big enough to count as an outage, that comes to 100.00% uptime for the day.

The busiest 15-minute window had 5 reports, about 20 hours ago. That stays below our outage threshold, so it doesn't count as downtime.

No problems detected in the last 24 hoursReports for GitHub stayed at their usual level the whole time.
Official status

What GitHub's status page says

Report categories

What people can report about GitHub

What went wrong

What people said was wrong in recent problem reports for GitHub worldwide.

  1. Website70%
  2. App26%
  3. Login4%

Share of 210 recent reports that said what was wrong, from every country listed below.

World map

GitHub reports around the world

In the last 24 hours, 2,527 problem reports about GitHub came in from 66 countries. Right now reports are at the usual level in every country.

  • Outage now
  • Problems now
  • Normal
Each dot is a group of recent reports, coloured by how its country is doing now; bigger dots, more reports.
CountryNowLast hour24 hours
The US numbers above Normal 4889
Brazil Normal 1291
India Normal 1117
Canada Normal 1101
Germany Normal 194
Poland Normal 194
France Normal 163
Ireland Normal 120
The UK Normal 0140
The Netherlands Normal 092
Ukraine Normal 045
Japan Normal 032

Each country's status compares its reports with the usual level there. 60 more countries had 549 reports in the last 24 hours. Map outlines: Natural Earth.

Last 30 days

GitHub problem spikes, last 30 days

Since 5 October, GitHub had 8 outage spikes and 7 periods of elevated reports. The longest lasted 1 h 55 min, on 30 October.

  • Sat 3 Oct: no data
  • Sun 4 Oct: no data
  • Mon 5 Oct: 19 reports
  • Tue 6 Oct: 21 reports
  • Wed 7 Oct: 105 reports (outage spike that day)
  • Thu 8 Oct: 16 reports
  • Fri 9 Oct: 19 reports
  • Sat 10 Oct: 20 reports
  • Sun 11 Oct: 18 reports
  • Mon 12 Oct: 22 reports
  • Tue 13 Oct: 50 reports
  • Wed 14 Oct: 16 reports
  • Thu 15 Oct: 13 reports
  • Fri 16 Oct: 7 reports
  • Sat 17 Oct: 4 reports
  • Sun 18 Oct: 2 reports
  • Mon 19 Oct: 27 reports (outage spike that day)
  • Tue 20 Oct: 18 reports
  • Wed 21 Oct: no data
  • Thu 22 Oct: 3 reports
  • Fri 23 Oct: 23 reports
  • Sat 24 Oct: 5 reports
  • Sun 25 Oct: 3 reports
  • Mon 26 Oct: 18 reports
  • Tue 27 Oct: 7 reports
  • Wed 28 Oct: 161 reports (outage spike that day)
  • Thu 29 Oct: 323 reports (elevated reports that day)
  • Fri 30 Oct: 1,293 reports (outage spike that day)
  • Sat 31 Oct: 79 reports
  • Sun 1 Nov: no data
  • Outage
    Fri 30 Oct, 20:55–21:45
    Lasted 51 min
    52peak reports
  • Outage
    Fri 30 Oct, 18:30–20:25
    Lasted 1 h 55 min
    252peak reports
  • Elevated reports
    Fri 30 Oct, 16:44–16:59
    Lasted 15 min
    18peak reports
  • Outage
    Fri 30 Oct, 15:10–16:28
    Lasted 1 h 18 min
    458peak reports
  • Elevated reports
    Thu 29 Oct, 23:48–00:08
    Lasted 21 min
    10peak reports
  • Elevated reports
    Thu 29 Oct, 15:38–16:04
    Lasted 26 min
    22peak reports
  • Elevated reports
    Wed 28 Oct, 21:32–21:57
    Lasted 25 min
    15peak reports
  • Elevated reports
    Wed 28 Oct, 20:29–20:52
    Lasted 23 min
    16peak reports

7 earlier spikes in this period.

By country

Each square is one day in the countries with the most reports: red when reports stayed at outage level for half an hour or more, amber when they stayed above the usual level for an hour or more, grey otherwise.

  • The US2,005
  • Brazil484
  • The UK408
  • India265
  • Canada220
  • France215
  • Germany199
  • Poland191

Country history starts on 28 October 2026. Days run from midnight to midnight, Central European time.

A spike is a sharp rise in problem reports from users, kept exactly as this page showed it at the time. This history starts on 5 October 2026. Monthly reports for all services

Troubleshooting

How to fix GitHub not working

GitHub is up on our end, so if it won't work for you, the problem is most likely on your side. Work through these in order:

Your browser tries to reach github.com over your own connection, right now. Nothing is sent to us or stored.

  1. Check GitHub's status page

    Open https://www.githubstatus.com before you change anything on your machine. If an incident is listed, wait and retry later; a local fix will not help. If the page shows normal operation, move to your browser and network.

  2. Try a private browser window

    Load github.com in a private or incognito window. If it works there but fails in your normal window, clear cookies and site data for github.com, then disable extensions one by one. This separates a browser profile problem from a network problem.

  3. Refresh your Git credentials

    For HTTPS remotes, delete the saved github.com entry from Keychain Access on macOS or Credential Manager on Windows. Run git fetch in a repo; Git will prompt for your username and a personal access token. If push or pull still fails, run git remote -v and check that the URL matches the repo you intend to use.

  4. Test SSH access and remote URL

    If you use SSH, run ssh -T [email protected]. A message that says you authenticated successfully means the key works; Permission denied (publickey) means your key is not loaded or not added to your account. Check loaded keys with ssh-add -l and add the right key with ssh-add ~/.ssh/id_ed25519; if the remote uses HTTPS, change it to [email protected]:OWNER/REPO.git.

Error messages

Common GitHub error messages

What each message means and what to try. The wording can differ a little between app versions.

  • Incorrect username or password.

    Means
    GitHub rejected those credentials.
    Fix
    Check your typing and caps lock, then try again. If the message persists, reset your password.

While GitHub is down: what to use instead

  • Keep committing locally Git keeps the full history on your machine, so you can commit and branch offline and push the whole batch once pushes stop timing out.
  • Command line instead of the website When github.com shows the unicorn error page or pull requests won't load, plain git pull and git push often still work, because the status page tracks Git operations separately from the web interface.
  • GitLab or Bitbucket mirror If you already keep a mirror remote on one of them, push there and point teammates or your deploy script at that copy until the main repo comes back.
  • Run checks on your own machine If Actions jobs sit queued, run the tests and build locally before you merge.
Your device

Fix GitHub on Windows, Mac, Android and iPhone

GitHub on Windows

Fix
If the GitHub website won't load, clear your browser cache or try a different browser. For connection issues with GitHub Desktop or command-line Git, verify your credentials in the Windows Credential Manager.
Check
Check the official GitHub Status page in your browser to see if there is a known outage. You can also use the Command Prompt to test if your network can reach GitHub's servers.
Command Prompt
ping github.comTest whether GitHub's servers reply
nslookup github.comCheck that GitHub's DNS resolves
tracert github.comTrace where the connection drops
ipconfig /flushdnsClear the DNS cache, then reload

GitHub on Mac

Fix
Resolve GitHub connection errors by updating your Git credentials in the macOS Keychain Access. If the GitHub website is unresponsive, clear your Safari or Chrome browser cache and disable active VPNs.
Check
Verify if GitHub is down by visiting the GitHub Status dashboard or checking the Network utility to see if GitHub's servers respond. You can also test your SSH connection to GitHub in the Terminal.
Terminal
ping -c 4 github.comTest whether GitHub's servers reply
nslookup github.comCheck that GitHub's DNS resolves
traceroute github.comTrace where the connection drops
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponderFlush the macOS DNS cache, then reload

GitHub on Android

Fix
Clear the GitHub app cache in your Android settings and check the Google Play Store for any available updates. If the GitHub app still won't load, try logging in through a mobile web browser.
Check
Check if the GitHub app displays connection errors, or open your mobile browser to visit the GitHub Status page. You can also check the Google Play Store reviews to see if other Android users are reporting issues.

GitHub on iPhone and iPad

Fix
Update the GitHub app from the App Store and toggle your Wi-Fi or cellular connection to reset the network. If GitHub still fails to load, reinstall the app or access the site using Safari.
Check
Visit the official GitHub Status page on Safari to check for platform-wide outages. You can also check if the GitHub app shows a persistent loading spinner or connection error message.
Ranked by peak

Biggest GitHub problems so far

  1. 1
    OutageLasted 1 h 18 min
    458reports in 15 min
  2. 2
    OutageLasted 1 h 55 min
    252reports in 15 min
  3. 3
    OutageLasted 33 min
    61reports in 15 min

Ranked by the most problem reports in one 15-minute window. Our archive started on 5 October 2026, so earlier problems are not counted. Times are Central European time.

Same time

Problems at the same time as GitHub

Since 5 October, 14 of GitHub's 15 spikes in problem reports overlapped a spike at another service.

When several services get problem reports at once, something they share, such as a cloud host or a network, can be the real cause. Matching times alone do not prove it.

Most often at the same time

How many of GitHub's spikes overlapped one of theirs.

During the latest spike

GitHub: Fri 30 Oct, 20:55 to 21:45

42 more services. Red dot: outage. Amber dot: elevated reports.

A spike is a sharp rise in problem reports from users, as the live pages showed it. Times are Central European time.

Busiest times

When people report GitHub problems

The busiest hour for reports about GitHub is 18:00 to 19:00 Central European time, and the busiest day is Thursday.

By hour of the day

  • 00:00 to 01:00: 1.4 reports on an average day
  • 01:00 to 02:00: 1.3 reports on an average day
  • 02:00 to 03:00: 1 report on an average day
  • 03:00 to 04:00: 0.95 reports on an average day
  • 04:00 to 05:00: 0.93 reports on an average day
  • 05:00 to 06:00: 0.42 reports on an average day
  • 06:00 to 07:00: 0.25 reports on an average day
  • 07:00 to 08:00: 0.44 reports on an average day
  • 08:00 to 09:00: 1.2 reports on an average day
  • 09:00 to 10:00: 0.58 reports on an average day
  • 10:00 to 11:00: 0.8 reports on an average day
  • 11:00 to 12:00: 1.2 reports on an average day
  • 12:00 to 13:00: 1 report on an average day
  • 13:00 to 14:00: 1.6 reports on an average day
  • 14:00 to 15:00: 1.9 reports on an average day
  • 15:00 to 16:00: 2.3 reports on an average day
  • 16:00 to 17:00: 3 reports on an average day
  • 17:00 to 18:00: 5 reports on an average day
  • 18:00 to 19:00: 7.2 reports on an average day
  • 19:00 to 20:00: 3.3 reports on an average day
  • 20:00 to 21:00: 2.2 reports on an average day
  • 21:00 to 22:00: 3.4 reports on an average day
  • 22:00 to 23:00: 3.4 reports on an average day
  • 23:00 to 00:00: 2.6 reports on an average day

By day of the week

  • Monday: 21 reports on an average Monday
  • Tuesday: 24 reports on an average Tuesday
  • Wednesday: 59 reports on an average Wednesday
  • Thursday: 107 reports on an average Thursday
  • Friday: 92 reports on an average Friday
  • Saturday: 27 reports on an average Saturday
  • Sunday: 7.5 reports on an average Sunday

Each bar is the average number of user reports in that hour, or on that day of the week, from 24 days of reports since 5 October 2026. The busiest bar is highlighted. Spikes in reports are left out, so one outage does not set the pattern.

About

What happens when GitHub goes down

GitHub is a code hosting and collaboration platform where developers store repositories, review changes, manage issues, and run automated workflows; teams, students, and open source maintainers depend on it for daily work. An outage can stop your pushes, pull requests, code review, and CI jobs.

When the service has trouble, the first sign often shows up in git operations: pushes and pulls fail, clones hang, authentication errors appear, and large file uploads stall. Web actions break next, so issues won't load, pull requests stall, code review comments may not post, and notifications lag. Actions and Packages can fail on their own, leaving workflows queued or package downloads unavailable. Problems can hit one region or a single component, so check the official status page before you assume a full outage.

Servers and network

GitHub IP address, servers and network

IPv4 address
140.82.121.4
IPv6
Not offered
Network
AS36459 · GitHub, Inc., registered in the United States
DNS hosted by
Amazon Route 53
HTTPS certificate
Issued by Sectigo Limited, valid until 28 Jan 2027 (88 days)
HTTP/3
Not advertised
Our check
Answered in 293 ms

Checked from our server in Frankfurt, Germany, 12 h ago, for github.com. Visitors elsewhere may see different addresses.

Checked from 11 places around the world

All 11 locations got an answer from github.com. Fastest from Tokyo (23 ms), slowest from Madrid (193 ms). The answers came through 2 networks: GitHub, Inc. (AS36459) and Microsoft Corporation (AS8075).

LocationResultTimeAddress reached
FrankfurtGermanyUp27 ms140.82.121.3GitHub, Inc.
ViennaAustriaUp99 ms20.250.119.67Microsoft Corporation
MilanItalyUp62 ms140.82.121.4GitHub, Inc.
ParisFranceUp115 ms20.250.119.67Microsoft Corporation
AmsterdamNetherlandsUp54 ms140.82.121.3GitHub, Inc.
MadridSpainUp193 ms20.250.119.67Microsoft Corporation
WarsawPolandUp175 ms20.250.119.67Microsoft Corporation
Los AngelesUSAUp63 ms172.182.252.133Microsoft Corporation
São PauloBrazilUp28 ms4.228.31.150Microsoft Corporation
SingaporeSingaporeUp30 ms20.205.243.166Microsoft Corporation
TokyoJapanUp23 ms20.27.177.113Microsoft Corporation

Checked with check-host.net from its servers in these cities 9 h ago, for github.com. Time is how long each server took to load the page.

Questions

GitHub FAQ

Is GitHub down right now?
The status at the top of this page shows whether problem reports for GitHub are above their usual level, counted in 15-minute windows over the last 24 hours. If the official status page is linked above, check it for a confirmed incident. To tell whether the problem is only on your side, open the site in a private window, try another browser, switch from Wi-Fi to cellular data, and test from a different network; if it loads there, your browser, an extension, a cached session, or your local connection is the likely cause.

Why does my git push fail with 'Authentication failed'?
A failed push often means your saved credentials or SSH key no longer match what GitHub expects. Remove the old entry for the service in your Git credential helper or SSH agent, then sign in again with a personal access token or an updated key. With two-factor authentication, a password alone will not work for HTTPS pushes.

Why is GitHub Actions stuck in queued or failing without logs?
A job that sits in queued usually means runners are busy or a workflow condition blocks it. Check the workflow run page for a skipped job or setup error, then open the Actions settings for the repository to confirm runner availability and billing status. If the run fails before logs appear, a syntax error in the workflow YAML or a missing secret can stop it early.

Why does GitHub Pages show a blank page or page not found after a deploy?
A blank page after deploy usually means a wrong publish directory or a missing index file. Open the Pages settings for the repository to confirm the source branch and folder, then check the deployment log for a failed build. If the site works at the project URL but not the custom domain, fix the DNS records or the CNAME file.

Why can't I sign in to GitHub with my passkey or two-factor code?
A passkey or two-factor code can fail when your device clock is off or the browser does not support the credential. Try signing in with a recovery code or a security key on another device, and check that you selected the right account. If the app shows a timeout, reset your system time to automatic and try again.
For your site

Put the GitHub status badge on your site

Paste one of these into a web page, a blog post or a README. The badge shows the same status as this page, based on user problem reports. Browsers can keep a copy for up to 4 hours. It links back here.

GitHub status badge, as it looks now

HTML
<a href="https://isitdownrightnow.app/services/github/"><img src="https://isitdownrightnow.app/badge/github.svg" alt="GitHub status" height="20"></a>
Markdown, for README files
[![GitHub status](https://isitdownrightnow.app/badge/github.svg)](https://isitdownrightnow.app/services/github/)

The badge is a plain image: no scripts, no cookies. People who see it on your page load it from our server.

How we track GitHub

The status on this page comes from user-submitted problem reports for GitHub, counted in 15-minute windows over the last 24 hours. Each window is compared with the normal level for GitHub, so a few complaints on a quiet day don't trigger anything, but a sudden jump well above normal does.

When reports climb well above normal, the status here changes to partial outage or major outage and the chart moves with it. This is separate from GitHub's official status page: user reports tend to show a problem early, while the official page confirms the cause. If the two disagree, check both.

Elsewhere

Check other services

See all 500+ services

Problems elsewhere right now

Strips: user reports, last 6 hours, 15 minutes a segment.