GitHub status
Is GitHub down? This is GitHub’s current status, its components and its recent incidents, read from GitHub’s official status page and refreshed every 2 minutes.
All Systems Operational
As reported by GitHub’s status page, read Nov 15, 2026, 08:05 UTC.
Components
| Component | Status |
|---|---|
| Git Operations | Operational |
| Webhooks | Operational |
| Visit www.githubstatus.com for more information | Operational |
| API Requests | Operational |
| Issues | Operational |
| Pull Requests | Operational |
| Actions | Operational |
| Packages | Operational |
| Pages | Operational |
| Copilot | Operational |
| Codespaces | Operational |
| Copilot AI Model Providers | Operational |
What a degraded performance status means, and how much downtime an SLA allows: the uptime calculator.
Recent GitHub incidents
- Copilot experiencing degraded model availability for some GPT models · Nov 13, 2026, 20:13 UTC · resolved, minor impact, lasted 1 h 14 min
Between 19:05 and 21:27 UTC on November 13, 2026, GitHub Copilot experienced degradation affecting GPT-6.1 Terra, GPT-5.6 Sol, and GPT-6 Luna models. Users encountered elevated error rates when using these models.<br /><br />The degradation was caused by an issue with an…
- Incident with Pull Requests · Nov 13, 2026, 15:47 UTC · resolved, major impact, lasted 2 h 42 min
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.
- Disruption with Email Delivery · Nov 12, 2026, 19:36 UTC · resolved, minor impact, lasted 2 h 7 min
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.
- Incident with Webhooks API · Nov 12, 2026, 18:43 UTC · resolved, minor impact, lasted 51 min
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.
- Impact across multiple GitHub products including Actions, Pages, and Copilot products. · Nov 11, 2026, 20:48 UTC · resolved, critical impact, lasted 33 min
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.
- Incident with Webhooks · Nov 11, 2026, 20:22 UTC · resolved, minor impact, lasted 4 min
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.
- Incident with Git Operations and Pull Requests · Nov 10, 2026, 16:10 UTC · resolved, critical impact, lasted 1 h 44 min
On November 10, 2026, from approximately 15:00 UTC to 17:55 UTC, GitHub experienced degraded performance affecting repository pages, pull requests, and GitHub Actions. Customers may have seen slow or failed page loads and delays processing pull request updates and merges. Some…
- Degraded availability for GPT-5.3 Codex and GPT-5.6 models in Copilot · Nov 9, 2026, 23:16 UTC · resolved, major impact, lasted 49 min
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.
- Incident with Actions and Checks API · Nov 9, 2026, 18:12 UTC · resolved, critical impact, lasted 47 min
On November 9, 2026, between 18:07 and 18:59 UTC, GitHub Actions experienced degraded performance. During this time, some customers saw workflow runs fail to start, update or report status correctly. An average of 28% of workflow runs were affected, peaking at 65% during the…
- Incident with Webhooks and Actions · Nov 9, 2026, 10:00 UTC · resolved, major impact, lasted 1 h 50 min
On November 9, 2026, from 09:23 to 11:40 UTC, one of our job queue clusters was degraded, delaying webhook deliveries, Actions workflow runs, and Dependabot and dependency graph updates. Until mitigation at 10:37 UTC, an average of 26% of webhook deliveries were delayed, peaking…
- Increased timeouts due to surge in anonymous users · Nov 9, 2026, 05:59 UTC · resolved, minor impact, lasted 3 h 11 min
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.
- Increase in timeouts for some unauthenticated users · Nov 8, 2026, 10:36 UTC · resolved, minor impact, lasted 1 h 57 min
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.
- Degraded performance for multiple GitHub services · Nov 5, 2026, 23:36 UTC · resolved, minor impact, lasted 45 min
On November 5, 2026, between 23:21 and approximately 23:26 UTC, several GitHub services experienced elevated errors, including Git operations, Issues, Actions, authentication, and API requests. Customers may have encountered failed requests and Git pushes, and some Actions…
- Incident with Actions · Nov 5, 2026, 16:50 UTC · resolved, minor impact, lasted 52 min
Between 16:39 and 16:57 UTC on November 5, 2026, some customers experienced failures starting workflow runs in GitHub Actions and Checks, and some in-progress runs failed. At peak, about 3% of workflow runs failed to queue, and roughly 0.21% of in-progress runs failed.<br /><br…
- Incident with Actions · Nov 4, 2026, 17:40 UTC · resolved, major impact, lasted 36 min
Please refer to the combined summary in this related incident: https://www.githubstatus.com/incidents/xr3myzj7ms51
Source: GitHub, GitHub’s public status page, read Nov 15, 2026, 08:05 UTC. Uptimely is not affiliated with GitHub; incident text is GitHub’s own.
Is it down for you, or for everyone?
A status page shows what the vendor has confirmed, which often lags what users see. Run a live check of github.com to see whether it answers right now.
Get alerted when GitHub has an incident
Uptimely’s External Status Page monitor watches GitHub’s status page and alerts your team by email, SMS, phone call, Slack, Discord or browser push when it reports a problem, next to the monitors for your own services.
Status of similar services
- Bitbucket status
- npm status
- Docker status
- Twilio status
- Datadog status
- Sentry status
- Supabase status
- PlanetScale status
- MongoDB Atlas status
- Elastic Cloud status
- Snowflake status
- Grafana Cloud status
- CircleCI status
- Mailgun status
- Resend status
- Clerk status
- Segment status
- Cloudinary status
Is GitHub down right now?
The status at the top of this page is GitHub's own, read from its public status page every couple of minutes. It shows what GitHub's team has confirmed. For an independent check of whether github.com answers right now, use the live check on the is-it-down page.
Where is GitHub's official status page?
GitHub publishes its status at https://www.githubstatus.com. This page shows the same data with the recent incident history in one place, and links each incident to GitHub's own write-up.
Why does GitHub not work for me when its status says operational?
A status page lists the incidents a vendor has confirmed, and confirmation takes time: problems often reach users minutes before they reach the status page, and some partial or regional problems never appear on it. Your own network, account or region can also be the cause.
How can I get alerted when GitHub has an incident?
Add an External Status Page monitor in Uptimely pointed at https://www.githubstatus.com. It reads the page on a schedule and alerts your team by email, SMS, phone call, Slack, Discord or browser push when GitHub reports a problem, beside the monitors for your own services.
Verified by the Uptimely team.