Space for ads
Checked every 5 minutes · How we measure this
As of 23:50 EDT on 21 Sep 2026, github.com responded to our check in 167 ms, with 98.24% availability over the last 24 hours.
Checked every 5 minutes · last checked 9 minutes ago
The line is response time measured from our probe to github.com, which rises when the service slows down. Shaded red marks intervals where checks actually failed. It excludes your own connection and browser rendering.
Reported by GitHub on its own status page. Verify on their status page.
Performance of git clones, pulls, pushes, and associated operations
Real time HTTP callbacks of user-generated and system events
Requests for GitHub APIs
Requests for Issues on GitHub.com
Requests for Pull Requests on GitHub.com
Workflows, Compute and Orchestration for GitHub Actions
API requests and webhook delivery for GitHub Packages
Frontend application and API servers for Pages builds
Orchestration and Compute for GitHub Codespaces
0 problem reports
GitHub degraded performance
DownBits detected degraded performance on GitHub between 21 Sep 2026, 03:50 – 04:05 IST, lasting ongoing. Detected across 3 consecutive automated checks of github.com.
Detected by DownBits probe
Incident with Pull Requests
A git fileserver issue caused a brief delay in creating some merge commits - we've isolated the underlying server and already observed recovery.
Confirmed on the vendor status page
Elevated rate of errors for OpenAI models provided by Copilot
We are experiencing degraded availability for GPT-5.6 Luna, GPT-5.6 Terra, GPT-5.6 Sol, GPT-6 Astra, GPT-5.3-Codex in Copilot products and IDE surfaces. This is due to an issue with an upstream model provider. The provider is working to mitigate the problem and we are monitoring recovery. We recommend choosing another model or selecting 'Auto' to continue using Copilot.
Confirmed on the vendor status page
GitHub degraded performance
DownBits detected degraded performance on GitHub between 16 Sep 2026, 13:00 – 17:25 IST, lasting ongoing. Detected across 53 consecutive automated checks of github.com.
Detected by DownBits probe
Degradation with Gemini 3.8 Flash
The degradation affecting Copilot AI Model Providers has been mitigated. We are monitoring to ensure stability.
Confirmed on the vendor status page
Disruption with some GitHub services
The degradation has been mitigated. We are monitoring to ensure stability.
Confirmed on the vendor status page
GitHub degraded performance
DownBits detected degraded performance on GitHub between 15 Sep 2026, 16:00 – 16:55 IST, lasting ongoing. Detected across 11 consecutive automated checks of github.com.
Detected by DownBits probe
Disruption with some GitHub services
We continue to monitor intermittent errors affecting Claude Fable 5.1 in some Copilot products and integrated development environments. Customer-facing metrics have recovered, and we are awaiting confirmation from our upstream provider that the issue will not recur. Customers can select another model or Auto in the meantime.
Confirmed on the vendor status page
Actions Larger Runner Jobs for some customers may be slow to start
The degradation has been mitigated. We are monitoring to ensure stability.
Confirmed on the vendor status page
GitHub outage
DownBits detected an outage on GitHub between 13 Sep 2026, 14:55 – 16:25 IST, lasting ongoing. Detected across 18 consecutive automated checks of github.com.
Detected by DownBits probe
Incident with several GitHub Services
Pull Requests is experiencing degraded performance. We are continuing to investigate.
Confirmed on the vendor status page
GitHub is responding normally. Our last automated check of github.com completed 9 minutes ago and succeeded in 167 ms. Over the past 24 hours the service answered 98.24% of our checks.
Measured from our automated checks, GitHub has been available 98.24% over 24 hours, 99.45% over 7 days, 99.42% over 30 days. We recorded 11 incidents in the last 30 days.
GitHub has averaged 334 ms across our successful checks in the past 24 hours, which is normal for a service of this kind. Response time is measured from our probe to github.com and does not include rendering time in your browser.
The most recent incident DownBits recorded for GitHub began on 21 September 2026 at 03:50 IST and lasted 15 min. It was logged as degraded performance. Detected by DownBits probe.
Our probe is reaching github.com normally right now, so the problem is more likely to be local to you than a full outage. Use the report button on this page to add your own signal — when several people report the same problem within a short window, it appears on the chart above.
A working marketing site does not mean a working API. Call the API host directly — curl -s -o /dev/null -w "%{http_code}" https://github.com/ — and check the vendor status page linked above for component-level detail, since one component can fail while the rest stay green.
HTTP 429 and 529 mean you are being throttled, not that the service is down. Inspect the response headers for a retry-after value and back off exponentially rather than retrying immediately.
A 401 or 403 is an authentication problem on your side. Rotated keys, an expired billing method, or a revoked token all present as sudden total failure.
Open any other site. If nothing loads, the issue is your network rather than GitHub. On Windows run ping github.com and nslookup github.com in Command Prompt; on macOS or Linux use Terminal. A DNS failure and a server failure look identical in a browser but are very different problems.
Load github.com in a private or incognito window. If it works there, clear cookies and site data for github.com in your normal browser rather than clearing everything.
Switch from Wi-Fi to mobile data, or vice versa. Regional ISP routing problems are common and often affect one carrier while others are unaffected.
We link the vendor status page so you can check our reading against theirs.
No comments received
