Space for ads
Checked every 5 minutes · How we measure this
As of 20:15 EST on 13 Nov 2026, github.com responded to our check in 262 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 degraded performance
DownBits detected degraded performance on GitHub between 14 Nov 2026, 01:50 – 03:05 IST, lasting ongoing. Detected across 15 consecutive automated checks of github.com.
Detected by DownBits probe
GitHub degraded performance
DownBits detected degraded performance on GitHub between 13 Nov 2026, 21:25 – 23:05 IST, lasting ongoing. Detected across 20 consecutive automated checks of github.com.
Detected by DownBits probe
Copilot experiencing degraded model availability for some GPT models
The upstream provider has made mitigations and we are seeing the affected models begin to recover.
Confirmed on the vendor status page
Incident with Pull Requests
We continue to monitor the stability of merge requests.
Confirmed on the vendor status page
GitHub degraded performance
DownBits detected degraded performance on GitHub between 13 Nov 2026, 00:30 – 01:00 IST, lasting ongoing. Detected across 6 consecutive automated checks of github.com.
Detected by DownBits probe
Disruption with Email Delivery
We’re monitoring an email disruption related to an upstream provider degradation. Users whose email is hosted by the affected provider may experience delays in message delivery. Email service for users on other providers is currently operating normally. We’ll share updates as we learn more.
Confirmed on the vendor status page
Incident with Webhooks API
The degradation affecting Webhooks has been mitigated. We are monitoring to ensure stability.
Confirmed on the vendor status page
GitHub outage
DownBits detected an outage on GitHub between 12 Nov 2026, 02:25 – 02:45 IST, lasting ongoing. Detected across 4 consecutive automated checks of github.com.
Detected by DownBits probe
Impact across multiple GitHub products including Actions, Pages, and Copilot products.
We’re seeing recovery across all services and continuing to monitor. The backlog of Actions jobs are being processed. We’ll update when we see full recovery.
Confirmed on the vendor status page
GitHub outage
DownBits detected an outage on GitHub between 10 Nov 2026, 21:50 – 23:35 IST, lasting ongoing. Detected across 21 consecutive automated checks of github.com.
Detected by DownBits probe
Incident with Git Operations and Pull Requests
We continue to investigate elevated response times for Git operations and pull requests. Actions workflows are recovering. Pull request processing has shown some improvement, but users continue to experience delays and failures. We’re monitoring the impact and working to restore normal service.
Confirmed on the vendor status page
GitHub degraded performance
DownBits detected degraded performance on GitHub between 10 Nov 2026, 04:55 – 05:25 IST, lasting ongoing. Detected across 6 consecutive automated checks of github.com.
Detected by DownBits probe
GitHub outage
DownBits detected an outage on GitHub between 9 Nov 2026, 23:50 – 00:20 IST, lasting ongoing. Detected across 6 consecutive automated checks of github.com.
Detected by DownBits probe
Degraded availability for GPT-5.3 Codex and GPT-5.6 models in Copilot
The issue affecting GPT-5.3 Codex, GPT-5.6 Luna, and GPT-5.6 Sol in Copilot products and IDE surfaces has been mitigated. We are monitoring the service to ensure stability.
Confirmed on the vendor status page
Incident with Actions and Checks API
The degradation affecting Actions, Pages and Webhooks has been mitigated. We are monitoring to ensure stability.
Confirmed on the vendor status page
GitHub is responding normally. Our last automated check of github.com completed 7 minutes ago and succeeded in 262 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.60% over 7 days, 99.61% over 30 days. We recorded 59 incidents in the last 30 days.
GitHub has averaged 316 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 14 November 2026 at 01:50 IST and lasted 1 hr 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
