Space for ads
Checked every 5 minutes · How we measure this
As of 03:40 EDT on 8 Oct 2026, github.com responded to our check in 229 ms, with 100.00% availability over the last 24 hours.
Checked every 5 minutes · last checked 7 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 outage
DownBits detected an outage on GitHub between 7 Oct 2026, 20:55 – 21:30 IST, lasting ongoing. Detected across 7 consecutive automated checks of github.com.
Detected by DownBits probe
Incident with Git Operations, Issues, Actions and Pull Requests
All systems have recovered. We have applied mitigations and do not anticipate another recurrence.
Confirmed on the vendor status page
Incident with Git Operations, Pull Requests and Actions
Git Operations, Pull Requests and Actions are fully recovered and stable. The root cause has been identified and mitigations are being applied to prevent a reoccurrence.
Confirmed on the vendor status page
GitHub degraded performance
DownBits detected degraded performance on GitHub between 7 Oct 2026, 01:35 – 01:50 IST, lasting ongoing. Detected across 3 consecutive automated checks of github.com.
Detected by DownBits probe
Several services are degraded
We are deploying a mitigation and plan to resume migrations shortly thereafter
Confirmed on the vendor status page
GitHub outage
DownBits detected an outage on GitHub between 6 Oct 2026, 00:50 – 04:20 IST, lasting ongoing. Detected across 42 consecutive automated checks of github.com.
Detected by DownBits probe
Disruption with some GitHub services
Users may experience issues accessing organization and enterprise billing and licensing pages. We are deploying a mitigation and monitoring for recovery.
Confirmed on the vendor status page
Incident with Actions
Pages is operating normally.
Confirmed on the vendor status page
GitHub degraded performance
DownBits detected degraded performance on GitHub between 1 Oct 2026, 21:00 – 23:35 IST, lasting ongoing. Detected across 31 consecutive automated checks of github.com.
Detected by DownBits probe
GitHub degraded performance
DownBits detected degraded performance on GitHub between 1 Oct 2026, 20:25 – 20:50 IST, lasting ongoing. Detected across 5 consecutive automated checks of github.com.
Detected by DownBits probe
Actions Job Delays
GitHub Actions experienced degraded performance for some hosted runners due to throttling within an upstream Azure dependency. Service capacity has recovered, and we are continuing to monitor while working with Azure on the underlying condition.
Confirmed on the vendor status page
Elevated request latency
The degradation has been mitigated. We are monitoring to ensure stability.
Confirmed on the vendor status page
Copilot Code Review is unable to complete reviews
Revert of the impacted change is in flight, expect full recovery once the deployment is done.
Confirmed on the vendor status page
Disruption with billing information updates
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 23 Sep 2026, 15:50 – 16:35 IST, lasting ongoing. Detected across 9 consecutive automated checks of github.com.
Detected by DownBits probe
GitHub is responding normally. Our last automated check of github.com completed 7 minutes ago and succeeded in 229 ms. Over the past 24 hours the service answered 100.00% of our checks.
Measured from our automated checks, GitHub has been available 100.00% over 24 hours, 99.55% over 7 days, 99.53% over 30 days. We recorded 27 incidents in the last 30 days.
GitHub has averaged 267 ms across our successful checks in the past 24 hours, which is fast — comfortably within what a healthy service should return. 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 7 October 2026 at 20:55 IST and lasted 35 min. It was logged as outage. 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
