Is GitHub down?
Operationalchecked moments ago
We reached GitHub from all 10 regions we check.
As of Sep 23, 2026, 9:07 AM UTC, GitHub answered RealUptime's probes in all 10 regions that returned a reading.
Last outage: 21h 44m on Sep 21, 2026 (web surface, from South America).
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
Is it GitHub, or is it you?
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: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
- APIprimaryUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
What we measured, and what people reported
- North AmericaOperationalUS-East, US-West, US-Central, Canada
- US-EastOperationallatency: 316msstatus code: 200checked: Sep 23, 2026, 9:07 AM 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-WestOperationallatency: 228msstatus code: 200checked: Sep 23, 2026, 9:07 AM 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-CentralOperationallatency: 432msstatus code: 200checked: Sep 23, 2026, 9:04 AM 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.
- CanadaOperationallatency: 488msstatus code: 200checked: Sep 23, 2026, 9:04 AM 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 AmericaOperationallatency: 271msstatus code: 200checked: Sep 23, 2026, 9:05 AM 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.
- EuropeOperationalEurope, UK
- EuropeOperationallatency: 354msstatus code: 200checked: Sep 23, 2026, 9:06 AM 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.
- UKOperationallatency: 218msstatus code: 200checked: Sep 23, 2026, 9:06 AM 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 PacificOperationalAsia-Pacific, Southeast Asia, Australia
- Asia-PacificOperationallatency: 270msstatus code: 200checked: Sep 23, 2026, 9:07 AM 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 AsiaOperationallatency: 755msstatus code: 200checked: Sep 23, 2026, 9:07 AM 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.
- AustraliaOperationallatency: 602msstatus code: 200checked: Sep 23, 2026, 9:06 AM 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 have not received any reports for GitHub yet, which is not evidence that nothing is wrong.
Recent outages
measured 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 measurements and GitHub's own claim at the time, side by side.
Full availability history for GitHub: 90-day availability by region, month-by-month uptime, and every incident 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 serversTell me when this goes down
Get told when we measure this
We will tell you when our probes stop reaching GitHub, and again when they can reach it again. That is our own measurement from ten regions, not GitHub's status page. No account, no card.
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 measured by RealUptime"></a>The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.
What GitHub's SLA implies, from our measurement
Below your target
We measured 7h 8m of downtime for GitHub over the last 30 days, which is 99.0078% uptime by our reading. A 99.9% target allows 43 minutes over that period.
That is 6h 25m more than the target allows. The figure above is the pro-rata share of one month's fee for the time we could not reach it. Your contract probably uses a tiered credit schedule instead, and we have not read it, so treat this as one common way to reason about a credit rather than the amount they owe.
Separately, we measured 44h 15m where only one of our regions was affected. It is excluded above because most SLAs would not credit it, and it is the kind of outage a single-vantage monitor never sees at all.
This is computed from our own probe measurements, not from GitHub's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.