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 63 ms

Request to github.com, 3 min ago. 288 of 288 checks in the last 24 hours succeeded, median 36 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 ms150 ms300 ms20:0000:0004:0008:0012:0016: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 26 min ago
ResolvedStarted Oct 15, 18:31 UTCResolved Oct 15, 18:56 UTC

We suspected that CCA Automations were experiencing delays when users start an Automation, but further investigation found that there was no delay or impact to CCA Automations.

ResolvedStarted Oct 14, 00:12 UTCResolved Oct 13, 20:30 UTC

On October 13, around 20:42 UTC, an infrastructure failure caused GitHub Actions to have delays showing logs for workflow runs. No logs were lost and the issue has now been resolved and log processing has caught up. The actual workflows producing the logs were not impacted and ran normally and no run delays or check d…

ResolvedStarted Oct 12, 12:21 UTCResolved Oct 12, 20:16 UTC

On October 12th 2026 11:51 UTC GitHub experienced elevated 500 responses across several application pages. This caused failures on Issues and Pull Requests as well as Projects and Actions. Customers also experienced delayed notifications in their web inbox and via email. The immediate impact to Issues, Pull Requests,…

ResolvedStarted Oct 7, 17:17 UTCResolved Oct 7, 18:04 UTC

On October 7, 2026, from 16:52 to 17:01 UTC, GitHub experienced a recurrence of the write-operation outage from earlier that day. Both outages shared the same root cause. Please refer to the combined summary covering both incidents, their impact, and our prevention measures: https://www.githubstatus.com/incidents/djlm…

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

On October 7, 2026, GitHub had two outages of write operations with the same cause, totaling about 19 minutes. The first ran from 15:06 to 15:16 UTC (about 10 minutes) and the second from 16:52 to 17:01 UTC (about 9 minutes). In both windows, actions that save or change data failed across Git operations, pull requests…

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

On October 6, 2026, from 19:44 to 19:50 UTC, GitHub experienced a service outage with elevated error rates peaking at 1.30% of all requests, totaling approximately 1.16 million failed requests. This impacted 12 services across GitHub, including Pull Requests, Webhooks, Repos, OAuth, Git over SSH, Codespaces, and Gists…

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

On October 5, 2026, between 23:05 UTC and 00:11 UTC on October 6, some users experienced slow page loads, timeouts, and errors when accessing organization and enterprise billing, licensing, and settings pages. On average, the error rate was 1.9% and peaked at 13.8% of requests to the service that powers these pages. T…

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…

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