Skip to content

Outage tracker / GitHub

Is GitHub down?

I'm having a problem

Operationalchecked moments ago

We reached GitHub from all 10 regions we check.

As of Oct 5, 2026, 8:15 PM UTC, GitHub answered RealUptime's probes in all 10 regions that returned a reading.

Functional endpoints verified

Last outage: 5 min on Sep 8, 2026 (API, from US-East and Canada).

GitHub reports an active incident: "Incident with Actions" (minor incident, since Oct 5, 2026, 7:11 PM UTC). That is their claim, not our measurement: our probes are currently reaching GitHub, and an incident they declare can affect parts of the service our checks do not exercise. We show both and never merge them.

our independent probeslive · checked Oct 5, 2026, 8:15 PM UTC
US-East368 msOperational
US-West480 msOperational
Europe290 msOperational
Asia-Pacific324 msOperational
US-Central528 msOperational
Canada244 msOperational
UK367 msOperational
Southeast Asia787 msOperational
Australia311 msOperational
South America748 msOperational
their status pagetheir claim, not our reading

GitHub reports: Minor incident (“Partially Degraded Service”)

from GitHub's own status page, checked Oct 5, 2026, 7:52 PM UTC

GitHub reports an active incident: Incident with Actions (minor incident, since Oct 5, 2026, 7:11 PM UTC)

GitHub's status page reports Partially Degraded Service. Our probes are currently reaching GitHub successfully with normal latency. RealUptime's independent checks are currently succeeding from all 10 regions. These observations can coexist: a partial error-rate degradation on their side does not have to affect every request. Our checks measure whether a single request succeeds, not the vendor's internal error rate, so this can happen when an issue affects only part of a service that our simple check does not exercise. We show what we measured, not what they report: differences can mean a partial or user-specific issue that a simple reachability check won't catch. Read both before you draw a conclusion.

GitHub's own component breakdown, as they publish it

  • Git OperationsOperational
  • WebhooksOperational
  • Visit www.githubstatus.com for more informationOperational
  • API RequestsOperational
  • IssuesOperational
  • Pull RequestsOperational
  • ActionsDegraded performance
  • 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

US-East
624msp95 · latest
1s500ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 466ms2026-09-07 UTC: p95 496ms2026-09-08 UTC: p95 514ms2026-09-09 UTC: p95 483ms2026-09-10 UTC: p95 533ms2026-09-11 UTC: p95 466ms2026-09-12 UTC: p95 510ms2026-09-13 UTC: p95 442ms2026-09-14 UTC: p95 474ms2026-09-15 UTC: p95 497ms2026-09-16 UTC: p95 527ms2026-09-17 UTC: p95 538ms2026-09-18 UTC: p95 480ms2026-09-19 UTC: p95 465ms2026-09-20 UTC: p95 447ms2026-09-21 UTC: p95 473ms2026-09-22 UTC: p95 542ms2026-09-23 UTC: p95 516ms2026-09-24 UTC: p95 573ms2026-09-25 UTC: p95 461ms2026-09-26 UTC: p95 439ms2026-09-27 UTC: p95 452ms2026-09-28 UTC: p95 463ms2026-09-29 UTC: p95 490ms2026-09-30 UTC: p95 496ms2026-10-01 UTC: p95 484ms2026-10-02 UTC: p95 344ms2026-10-03 UTC: p95 329ms2026-10-04 UTC: p95 373ms2026-10-05 UTC: p95 624ms
Sep 6Sep 20Oct 5
US-West
475msp95 · latest
1s500ms0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 494ms2026-09-07 UTC: p95 618ms2026-09-08 UTC: p95 518ms2026-09-09 UTC: p95 427ms2026-09-10 UTC: p95 365ms2026-09-11 UTC: p95 458ms2026-09-12 UTC: p95 353ms2026-09-13 UTC: p95 527ms2026-09-14 UTC: p95 378ms2026-09-15 UTC: p95 567ms2026-09-16 UTC: p95 469ms2026-09-17 UTC: p95 440ms2026-09-18 UTC: p95 449ms2026-09-19 UTC: p95 422ms2026-09-20 UTC: p95 454ms2026-09-21 UTC: p95 661ms2026-09-22 UTC: p95 703ms2026-09-23 UTC: p95 548ms2026-09-24 UTC: p95 467ms2026-09-25 UTC: p95 521ms2026-09-26 UTC: p95 491ms2026-09-27 UTC: p95 479ms2026-09-28 UTC: p95 494ms2026-09-29 UTC: p95 534ms2026-09-30 UTC: p95 424ms2026-10-01 UTC: p95 536ms2026-10-02 UTC: p95 380ms2026-10-03 UTC: p95 346ms2026-10-04 UTC: p95 380ms2026-10-05 UTC: p95 475ms
Sep 6Sep 20Oct 5
Europe
452msp95 · latest
500ms250ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 500ms. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 351ms2026-09-07 UTC: p95 319ms2026-09-08 UTC: p95 386ms2026-09-09 UTC: p95 422ms2026-09-10 UTC: p95 424ms2026-09-11 UTC: p95 439ms2026-09-12 UTC: p95 418ms2026-09-13 UTC: p95 397ms2026-09-14 UTC: p95 332ms2026-09-15 UTC: p95 423ms2026-09-16 UTC: p95 334ms2026-09-17 UTC: p95 325ms2026-09-18 UTC: p95 324ms2026-09-19 UTC: p95 311ms2026-09-20 UTC: p95 329ms2026-09-21 UTC: p95 423ms2026-09-22 UTC: p95 448ms2026-09-23 UTC: p95 476ms2026-09-24 UTC: p95 409ms2026-09-25 UTC: p95 348ms2026-09-26 UTC: p95 340ms2026-09-27 UTC: p95 348ms2026-09-28 UTC: p95 454ms2026-09-29 UTC: p95 349ms2026-09-30 UTC: p95 430ms2026-10-01 UTC: p95 444ms2026-10-02 UTC: p95 447ms2026-10-03 UTC: p95 431ms2026-10-04 UTC: p95 352ms2026-10-05 UTC: p95 452ms
Sep 6Sep 20Oct 5
Asia-Pacific
867msp95 · latest
1s500ms0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 703ms2026-09-07 UTC: p95 617ms2026-09-08 UTC: p95 664ms2026-09-09 UTC: p95 759ms2026-09-10 UTC: p95 589ms2026-09-11 UTC: p95 551ms2026-09-12 UTC: p95 613ms2026-09-13 UTC: p95 642ms2026-09-14 UTC: p95 563ms2026-09-15 UTC: p95 567ms2026-09-16 UTC: p95 625ms2026-09-17 UTC: p95 653ms2026-09-18 UTC: p95 638ms2026-09-19 UTC: p95 600ms2026-09-20 UTC: p95 649ms2026-09-21 UTC: p95 635ms2026-09-22 UTC: p95 746ms2026-09-23 UTC: p95 718ms2026-09-24 UTC: p95 733ms2026-09-25 UTC: p95 575ms2026-09-26 UTC: p95 641ms2026-09-27 UTC: p95 594ms2026-09-28 UTC: p95 590ms2026-09-29 UTC: p95 622ms2026-09-30 UTC: p95 614ms2026-10-01 UTC: p95 551ms2026-10-02 UTC: p95 532ms2026-10-03 UTC: p95 562ms2026-10-04 UTC: p95 512ms2026-10-05 UTC: p95 867ms
Sep 6Sep 20Oct 5
US-Central
589msp95 · latest
1s500ms0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 789ms2026-09-07 UTC: p95 742ms2026-09-08 UTC: p95 755ms2026-09-09 UTC: p95 840ms2026-09-10 UTC: p95 710ms2026-09-11 UTC: p95 736ms2026-09-12 UTC: p95 799ms2026-09-13 UTC: p95 686ms2026-09-14 UTC: p95 609ms2026-09-15 UTC: p95 706ms2026-09-16 UTC: p95 565ms2026-09-17 UTC: p95 519ms2026-09-18 UTC: p95 533ms2026-09-19 UTC: p95 560ms2026-09-20 UTC: p95 587ms2026-09-21 UTC: p95 618ms2026-09-22 UTC: p95 694ms2026-09-23 UTC: p95 775ms2026-09-24 UTC: p95 666ms2026-09-25 UTC: p95 614ms2026-09-26 UTC: p95 610ms2026-09-27 UTC: p95 584ms2026-09-28 UTC: p95 630ms2026-09-29 UTC: p95 506ms2026-09-30 UTC: p95 783ms2026-10-01 UTC: p95 568ms2026-10-02 UTC: p95 596ms2026-10-03 UTC: p95 635ms2026-10-04 UTC: p95 485ms2026-10-05 UTC: p95 589ms
Sep 6Sep 20Oct 5
Canada
610msp95 · latest
1s500ms0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 573ms2026-09-07 UTC: p95 690ms2026-09-08 UTC: p95 641ms2026-09-09 UTC: p95 675ms2026-09-10 UTC: p95 678ms2026-09-11 UTC: p95 602ms2026-09-12 UTC: p95 570ms2026-09-13 UTC: p95 732ms2026-09-14 UTC: p95 478ms2026-09-15 UTC: p95 706ms2026-09-16 UTC: p95 603ms2026-09-17 UTC: p95 629ms2026-09-18 UTC: p95 605ms2026-09-19 UTC: p95 615ms2026-09-20 UTC: p95 638ms2026-09-21 UTC: p95 512ms2026-09-22 UTC: p95 644ms2026-09-23 UTC: p95 727ms2026-09-24 UTC: p95 772ms2026-09-25 UTC: p95 578ms2026-09-26 UTC: p95 637ms2026-09-27 UTC: p95 526ms2026-09-28 UTC: p95 551ms2026-09-29 UTC: p95 662ms2026-09-30 UTC: p95 846ms2026-10-01 UTC: p95 520ms2026-10-02 UTC: p95 421ms2026-10-03 UTC: p95 446ms2026-10-04 UTC: p95 436ms2026-10-05 UTC: p95 610ms
Sep 6Sep 20Oct 5
UK
482msp95 · latest
1s500ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 464ms2026-09-07 UTC: p95 482ms2026-09-08 UTC: p95 433ms2026-09-09 UTC: p95 424ms2026-09-10 UTC: p95 394ms2026-09-11 UTC: p95 433ms2026-09-12 UTC: p95 391ms2026-09-13 UTC: p95 418ms2026-09-14 UTC: p95 408ms2026-09-15 UTC: p95 393ms2026-09-16 UTC: p95 380ms2026-09-17 UTC: p95 387ms2026-09-18 UTC: p95 358ms2026-09-19 UTC: p95 356ms2026-09-20 UTC: p95 359ms2026-09-21 UTC: p95 458ms2026-09-22 UTC: p95 490ms2026-09-23 UTC: p95 453ms2026-09-24 UTC: p95 566ms2026-09-25 UTC: p95 466ms2026-09-26 UTC: p95 393ms2026-09-27 UTC: p95 345ms2026-09-28 UTC: p95 423ms2026-09-29 UTC: p95 492ms2026-09-30 UTC: p95 444ms2026-10-01 UTC: p95 484ms2026-10-02 UTC: p95 397ms2026-10-03 UTC: p95 413ms2026-10-04 UTC: p95 440ms2026-10-05 UTC: p95 482ms
Sep 6Sep 20Oct 5
Southeast Asia
1.1sp95 · latest
2s1s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 869ms2026-09-07 UTC: p95 867ms2026-09-08 UTC: p95 826ms2026-09-09 UTC: p95 758ms2026-09-10 UTC: p95 774ms2026-09-11 UTC: p95 981ms2026-09-12 UTC: p95 949ms2026-09-13 UTC: p95 744ms2026-09-14 UTC: p95 866ms2026-09-15 UTC: p95 940ms2026-09-16 UTC: p95 1.1s2026-09-17 UTC: p95 1.0s2026-09-18 UTC: p95 1.0s2026-09-19 UTC: p95 805ms2026-09-20 UTC: p95 824ms2026-09-21 UTC: p95 997ms2026-09-22 UTC: p95 992ms2026-09-23 UTC: p95 1.3s2026-09-24 UTC: p95 1.3s2026-09-25 UTC: p95 1.1s2026-09-26 UTC: p95 853ms2026-09-27 UTC: p95 895ms2026-09-28 UTC: p95 928ms2026-09-29 UTC: p95 1.0s2026-09-30 UTC: p95 1.2s2026-10-01 UTC: p95 1.1s2026-10-02 UTC: p95 938ms2026-10-03 UTC: p95 1.2s2026-10-04 UTC: p95 779ms2026-10-05 UTC: p95 1.1s
Sep 6Sep 20Oct 5
Australia
788msp95 · latest
2s1s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 804ms2026-09-07 UTC: p95 1.0s2026-09-08 UTC: p95 907ms2026-09-09 UTC: p95 958ms2026-09-10 UTC: p95 1.1s2026-09-11 UTC: p95 896ms2026-09-12 UTC: p95 814ms2026-09-13 UTC: p95 756ms2026-09-14 UTC: p95 949ms2026-09-15 UTC: p95 809ms2026-09-16 UTC: p95 1.0s2026-09-17 UTC: p95 889ms2026-09-18 UTC: p95 877ms2026-09-19 UTC: p95 632ms2026-09-20 UTC: p95 806ms2026-09-21 UTC: p95 941ms2026-09-22 UTC: p95 1.3s2026-09-23 UTC: p95 1.1s2026-09-24 UTC: p95 1.2s2026-09-25 UTC: p95 804ms2026-09-26 UTC: p95 1.0s2026-09-27 UTC: p95 809ms2026-09-28 UTC: p95 785ms2026-09-29 UTC: p95 800ms2026-09-30 UTC: p95 959ms2026-10-01 UTC: p95 705ms2026-10-02 UTC: p95 1.1s2026-10-03 UTC: p95 927ms2026-10-04 UTC: p95 570ms2026-10-05 UTC: p95 788ms
Sep 6Sep 20Oct 5
South America
856msp95 · latest
2s1s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 745ms2026-09-07 UTC: p95 786ms2026-09-08 UTC: p95 830ms2026-09-09 UTC: p95 831ms2026-09-10 UTC: p95 869ms2026-09-11 UTC: p95 828ms2026-09-12 UTC: p95 869ms2026-09-13 UTC: p95 670ms2026-09-14 UTC: p95 707ms2026-09-15 UTC: p95 848ms2026-09-16 UTC: p95 818ms2026-09-17 UTC: p95 933ms2026-09-18 UTC: p95 799ms2026-09-19 UTC: p95 1.1s2026-09-20 UTC: p95 961ms2026-09-21 UTC: p95 817ms2026-09-22 UTC: p95 835ms2026-09-23 UTC: p95 838ms2026-09-24 UTC: p95 763ms2026-09-25 UTC: p95 632ms2026-09-26 UTC: p95 638ms2026-09-27 UTC: p95 591ms2026-09-28 UTC: p95 730ms2026-09-29 UTC: p95 907ms2026-09-30 UTC: p95 896ms2026-10-01 UTC: p95 742ms2026-10-02 UTC: p95 583ms2026-10-03 UTC: p95 908ms2026-10-04 UTC: p95 651ms2026-10-05 UTC: p95 856ms
Sep 6Sep 20Oct 5

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

Get an email when we see GitHub go down, and when it is back

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.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when a measured outage opens, one when it closes, and a one-click unsubscribe in every one. We do not send anything else to this address.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What we measured, and what people reported

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 368msstatus code: 200checked: Oct 5, 2026, 8:14 PM UTC
      0 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-West
      Operationallatency: 480msstatus code: 200checked: Oct 5, 2026, 8:14 PM UTC
      0 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-Central
      Operationallatency: 528msstatus code: 200checked: Oct 5, 2026, 8:11 PM UTC
      0 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.
    • Canada
      Operationallatency: 244msstatus code: 200checked: Oct 5, 2026, 8:12 PM UTC
      0 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 America
    Operationallatency: 748msstatus code: 200checked: Oct 5, 2026, 8:11 PM UTC
    0 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.
  • Europe
    OperationalEurope, UK
    • Europe
      Operationallatency: 290msstatus code: 200checked: Oct 5, 2026, 8:13 PM UTC
      0 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.
    • UK
      Operationallatency: 367msstatus code: 200checked: Oct 5, 2026, 8:15 PM UTC
      0 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 Pacific
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 324msstatus code: 200checked: Oct 5, 2026, 8:14 PM UTC
      0 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 Asia
      Operationallatency: 787msstatus code: 200checked: Oct 5, 2026, 8:11 PM UTC
      0 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.
    • Australia
      Operationallatency: 311msstatus code: 200checked: Oct 5, 2026, 8:12 PM UTC
      0 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 outages

Incident with Actionsdeclared on their status page2026-10-05
Actions Job Delays, 3h 9mdeclared on their status page2026-10-01
Elevated request latency, 20mdeclared on their status page2026-10-01
[Retroactive] Actions workflow run failures after deployment gate approvals, 1mdeclared on their status page2026-10-01
Copilot Code Review is unable to complete reviews, 52mdeclared on their status page2026-09-28
Disruption with billing information updates, 3h 50mdeclared on their status page2026-09-24
Incident across several services, 18h 44mdeclared on their status page2026-09-23
Incident with Pull Requests, 1h 9mdeclared on their status page2026-09-20

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 servers

Put this badge in your README

GitHub uptime measured by RealUptimeLive, from this page's own readings.
[![GitHub uptime measured by RealUptime](https://realuptime.io/outages/github/badge.svg?days=30)](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

At or above your target

We measured 4 minutes of downtime for GitHub over the last 30 days, which is 99.9892% uptime by our reading. A 99.9% target allows 43 minutes over that period.

By our measurement there is no shortfall to claim for this period.

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.

What we check

primaryfunctional: live API
https://api.github.com/repos/octocat/hello-world
secondary
https://www.githubstatus.com/
secondaryfunctional: live API
https://api.github.com/user
RealUptime is not affiliated with GitHub; the name identifies what we measured, and nothing here speaks for GitHub's own team. We send a single web request to GitHub from 10 regions on our own schedule and time the response. We do not see inside GitHub's systems, do not use an account or real transaction, and are not the same signal GitHub's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for GitHub is a real functional API call (marked “functional” above), not just a landing page, so a clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Read the full methodology.