No, GitHub is up right now

Both signals agree: the official status feed and our own check.

Official status
All Systems Operational

From www.githubstatus.com, read 3 min ago.

Our check, from Germany
Answered in 34 ms

Request to github.com, 3 min ago. 259 of 288 checks in the last 24 hours succeeded, median 87 ms.

Is GitHub working for you?

One click, no account. It helps others see whether the problem is widespread.

We are still collecting reports. The numbers appear once 20 people have answered within 24 hours.

Response time, last 24 hours

measured from our server in Germany
0 ms5 s10 s12:0016:0020:0000:0004:0008:00
Time to first responseFailed check
One request every 5 minutes from a single location (Falkenstein, Germany). It shows how the answer time changes; it is not the speed you will see on your own connection.

Works for everyone else? Fix it on your side

  1. Check whether it is only this device. Open the service on your phone using mobile data instead of Wi-Fi. If it works there, the problem is your home network or this computer, not the service.
  2. Test from the command line. Check name resolution and the route, to see where the connection stops.
    nslookup github.com tracert github.com
  3. Check your tokens and rate limits. An expired token or a rate limit returns errors that look like an outage. Read the exact HTTP status code and message before assuming the service is down.
  4. Restart the router and the device. Unplug the router for 30 seconds, plug it back in, wait until it is online again, then restart the computer. This clears stuck connections and gives you a fresh route to the service.
  5. Flush the DNS cache. Windows may still remember an old address for the service. Open Command Prompt as administrator and run the command below, then try again.
    ipconfig /flushdns
  6. Turn off VPN and proxy for a moment. VPN exit servers are often rate-limited or blocked. Disconnect the VPN, and in Settings > Network & internet > Proxy make sure no manual proxy is set.
  7. Change the DNS server. If the name still does not resolve, switch DNS in Settings > Network & internet > your connection > DNS server assignment to a public resolver such as 1.1.1.1 or 8.8.8.8.
Guides that mention GitHub

Recent incidents

from the official feed, read 21 min ago
ResolvedStarted Oct 7, 17:17 UTCResolved Oct 7, 18:04 UTC

This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

ResolvedStarted Oct 7, 15:14 UTCResolved Oct 7, 16:25 UTC

This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

ResolvedStarted Oct 6, 19:57 UTCResolved Oct 6, 23:40 UTC

This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

ResolvedStarted Oct 5, 23:47 UTCResolved Oct 6, 01:32 UTC

This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

ResolvedStarted Oct 5, 19:11 UTCResolved Oct 5, 22:49 UTC

On October 5, 2026, between 18:48 and 22:49 UTC, GitHub Actions and Hosted Runners experienced degraded performance. Over the full incident, 14.3% of workflow runs using GitHub-hosted runners and 26.5% of individual GitHub-hosted jobs did not start within five minutes. During the roughly 90-minute period of highest im…

ResolvedStarted Oct 1, 14:47 UTCResolved Oct 1, 17:56 UTC

This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

ResolvedStarted Oct 1, 13:37 UTCResolved Oct 1, 13:57 UTC

On October 1, 2026, between 13:04 UTC and 13:34 UTC, users experienced two periods of slow page loads and intermittent request failures on GitHub.com. On average, the error rate was 0.52% and peaked at 6.13%. An unusually high volume of incoming traffic placed additional load on our traffic-handling infrastructure, de…

ResolvedStarted Oct 1, 11:34 UTCResolved Oct 1, 02:00 UTC

On October 1, around 02:00 UTC, an isolated infrastructure failure caused GitHub Actions to lose execution state for a small number of existing workflow runs. Affected runs may remain stuck, fail deployment approvals, or return errors when cancelled. Service connectivity has recovered, but the lost state cannot be res…

Questions and experiences

Ask about this page: members and our editors answer. Reading is open; writing needs a free account.

0 comments

…

4,322 members already hereThey read, write, comment and vote. 0 verified · 31 joined this year

Cookies

We use essential cookies to run the platform. Analytics and marketing cookies are only turned on once you consent — you can change your choice at any time.