Is GitHub down?
Vendor reports no incidentWhat GitHub reports
GitHub reports no incident on its status page.
As of the last successful poll, 2026-11-05 13:53 UTC.
Our regional reading
This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.
Checks passingchecked moments ago
Our checks of GitHub pass from all 10 regions we check.
As of Nov 5, 2026, 2:02 PM UTC, RealUptime's checks of GitHub passed in all 10 regions that returned a reading.
GitHub reports: All systems operational (“All Systems Operational”)
GitHub's own component breakdown, as they publish it
- Git OperationsOperational
- WebhooksOperational
- Visit www.githubstatus.com for more informationOperational
- API RequestsOperational
- IssuesOperational
- Pull RequestsOperational
- ActionsOperational
- PackagesOperational
- PagesOperational
- CopilotOperational
- CodespacesOperational
- Copilot AI Model ProvidersOperational
These are GitHub's components, named and scored by GitHub. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.
This is GitHub's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.
GitHub response time, by region
Check your own site while you wait on GitHub
Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not GitHub. It cannot diagnose GitHub's own systems.
What we measured, function by function
GitHub answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the api row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.
- WebUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
- APIprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
- Git operationsUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
- IssuesUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
- PackagesUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
- PagesUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
- Raw contentUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
Email me when GitHub reports an incident on its status page, and again when it reports it resolved.
Get an email when GitHub reports an incident
Email me when GitHub reports an incident on its status page, and again when it reports it resolved. No account, no card.
What our checks show, and what people reported
- North AmericaChecks passingUS-East, US-West, US-Central, Canada
- US-EastChecks passinglatency: 543msstatus code: 200checked: Nov 5, 2026, 2:00 PM UTC0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach GitHub normally. We do not have enough reports from US-East to say anything about what people there are seeing.
- US-WestChecks passinglatency: 822msstatus code: 200checked: Nov 5, 2026, 2:01 PM UTC0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach GitHub normally. We do not have enough reports from US-West to say anything about what people there are seeing.
- US-CentralChecks passinglatency: 1141msstatus code: 200checked: Nov 5, 2026, 2:01 PM UTC0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach GitHub normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
- CanadaChecks passinglatency: 331msstatus code: 200checked: Nov 5, 2026, 2:02 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach GitHub normally. We do not have enough reports from Canada to say anything about what people there are seeing.
- South AmericaChecks passinglatency: 377msstatus code: 200checked: Nov 5, 2026, 2:01 PM UTC0 people in the last 5 minutesNot enough reports to sayOur South America probes reach GitHub normally. We do not have enough reports from South America to say anything about what people there are seeing.
- EuropeChecks passingEurope, UK
- EuropeChecks passinglatency: 626msstatus code: 200checked: Nov 5, 2026, 2:01 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach GitHub normally. We do not have enough reports from Europe to say anything about what people there are seeing.
- UKChecks passinglatency: 350msstatus code: 200checked: Nov 5, 2026, 2:02 PM UTC0 people in the last 5 minutesNot enough reports to sayOur UK probes reach GitHub normally. We do not have enough reports from UK to say anything about what people there are seeing.
- Asia PacificChecks passingAsia-Pacific, Southeast Asia, Australia
- Asia-PacificChecks passinglatency: 747msstatus code: 200checked: Nov 5, 2026, 2:02 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach GitHub normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
- Southeast AsiaChecks passinglatency: 1098msstatus code: 200checked: Nov 5, 2026, 2:00 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach GitHub normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
- AustraliaChecks passinglatency: 413msstatus code: 200checked: Nov 5, 2026, 2:02 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach GitHub normally. We do not have enough reports from Australia to say anything about what people there are seeing.
Somewhere else or not sure: 0 people in the last 5 minutes
These are unverified reports from people using GitHub, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We started counting reports for GitHub on October 4, 2026.
Recent probe events
check entries are our own probes' readings; declared entries are the vendor's. How this check works
We have been measuring GitHub since August 8, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.
Need this in writing? Generate an SLA evidence report for GitHub covering any window you pick, with our check readings and GitHub's own claim at the time, side by side.
Full check history for GitHub: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.
Monitor your own site the same way
This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.
Start monitoring your own serversRun a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter
Put this badge in your README
Live, from this page's own readings.[](https://realuptime.io/outages/github)<a href="https://realuptime.io/outages/github"><img src="https://realuptime.io/outages/github/badge.svg?days=30" alt="GitHub uptime by RealUptime's checks" height="20"></a>Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.
To cite this page: RealUptime, "Is GitHub down?", https://realuptime.io/outages/github. The readings change with every check, so give the date you read them.
What we check
What our check can and cannot see
A pass means a public route of the service's API answered our request normally. We do not check what it returned, so it does not show that the data is right, that sign-in works or that the rest of the product works.
Host checked: api.github.com