Vendor record
GitHub
Checked
Front door check counts and GitHub’s own incident posts. Use them to investigate a dependency; neither confirms what happened in your app.
Front door checks
We send a request to a documented GitHub endpoint and count the checks that got the answer it is documented to give.
Front door reachable in 2,841 of 2,841 checks with a clear answer, last 30 days, checked every 15 minutes from a single CheckUpstream location.
38 more checks gave no clear answer and are not counted.
- Endpoint checked
- api.github.com
- Scope
- apiNo vendor region
- First check in this window
- Latest clear answer
Checks 15 minutes apart cannot see disruptions shorter than that. A check that reached the front door does not show that every GitHub product, region or your app worked.
How we count front door checksShorter disruptions
Our checks are 15 minutes apart, so they miss disruptions shorter than that. Datadog runs a separate outage tracker that may show disruptions our checks cannot see.
Independent outage detection for GitHub: Datadog’s Updog(opens in a new tab)CheckUpstream is not affiliated with Datadog.
GitHub says
Incident posts from GitHub’s status page, with its titles, impact levels and times. They say what GitHub chose to post, not what reached your app.
A closed record shows when our record closed. Some older records closed when a post left the status page, without a resolution post from the vendor.
146
incidents GitHub posted, last 1 year
Median recorded duration: 1h 32m. From 146 incidents with vendor-supplied starts and recorded closure times.
Most recent records · all dates
CCA Automations are delayed when starting an Automation
MinorGitHub’s postStarted, per GitHub
Closed in our record(29m)
Incident with Actions, Pull Requests and Issues
MinorGitHub’s postStarted, per GitHub
Closed in our record(8h 3m)
Incident with Git Operations, Issues, Actions and Pull Requests
CriticalGitHub’s postStarted, per GitHub
Closed in our record(53m)
Incident with Git Operations, Pull Requests and Actions
CriticalGitHub’s postStarted, per GitHub
Closed in our record(1h 15m)
Several services are degraded
CriticalGitHub’s postStarted, per GitHub
Closed in our record(3h 52m)
15 older records
Disruption with some GitHub services
MajorGitHub’s postStarted, per GitHub
Closed in our record(1h 52m)
Incident with Actions
CriticalGitHub’s postStarted, per GitHub
Closed in our record(3h 38m)
Actions Job Delays
MinorGitHub’s postStarted, per GitHub
Closed in our record(3h 12m)
Elevated request latency
MinorGitHub’s postStarted, per GitHub
Closed in our record(22m)
Copilot Code Review is unable to complete reviews
CriticalGitHub’s postStarted, per GitHub
Closed in our record(53m)
Disruption with billing information updates
MinorGitHub’s postStarted, per GitHub
Closed in our record(3h 58m)
Incident across several services
MinorGitHub’s postStarted, per GitHub
Closed in our record(18h 49m)
Incident with Pull Requests
MinorGitHub’s postStarted, per GitHub
Closed in our record(1h 11m)
Elevated rate of errors for OpenAI models provided by Copilot
MinorGitHub’s postStarted, per GitHub
Closed in our record(51m)
Degradation with Gemini 3.8 Flash
MajorGitHub’s postStarted, per GitHub
Closed in our record(10h 29m)
Disruption with some GitHub services
MinorGitHub’s postStarted, per GitHub
Closed in our record(58m)
Disruption with some GitHub services
MinorGitHub’s postStarted, per GitHub
Closed in our record(1h 32m)
Actions Larger Runner Jobs for some customers may be slow to start
MinorGitHub’s postStarted, per GitHub
Closed in our record(59m)
Incident with several GitHub Services
CriticalGitHub’s postStarted, per GitHub
Closed in our record(1h 34m)
Degradation in repos contents API
MinorGitHub’s postStarted, per GitHub
Closed in our record(28m)
Your code, your dependencies
See which of your code paths call GitHub
Connect GitHub or GitLab to find where your public or private repository uses GitHub. Review each match and your alert settings.
Free to start. No credit card.
Use this record on your site
Add GitHub status to your page.
Choose the format your page supports, then copy the code. Badges show the recorded vendor status; they do not establish impact on your app.
Frequently Asked Questions
Is GitHub currently down?
GitHub's latest recorded status is Operational. Check the timestamp and linked source at the top of this page. A vendor status report does not establish whether your application was affected.
When did GitHub last have an outage?
The most recent closed incident record began earlier today and spans 29 minutes. The vendor reported degraded performance. Closure may reflect a disappeared post or an expired tracking period; it does not confirm vendor or application recovery. Check the dated history and source links.
Does CheckUpstream publish an uptime percentage for GitHub?
No. CheckUpstream checks GitHub’s front door every 15 minutes and publishes how many checks reached it over the last 30 days, with the endpoint checked. Checks 15 minutes apart cannot see disruptions shorter than that. A percentage would claim more than the checks can show.
How do I monitor GitHub in production?
Create your account, connect GitHub or GitLab and choose a public or private repository. Review the vendor matches and your alert settings. Available notification channels and history depend on your plan.
How does CheckUpstream track GitHub?
This record separates vendor-reported incidents from independent checks. Sources and coverage vary by vendor: review the linked source, check time and measurement scope. Neither kind of evidence establishes SLA credit eligibility.