Uptimy

Developer platforms

Is GitHub down?

Live GitHub status, measured independently. We probe 10 GitHub endpoints from monitoring regions on every continent and record every outage we detect.

GitHub is up

Our probes are reaching GitHub normally from every region we check from.

Checked every minute from 6 regions on every continent.

24h uptime
7d uptime
30d uptime
  • Website
    99.92% uptime, 30 days
    6 regions, 17 to 163 ms
    Checking
    p50
    54 ms
    Median response
    p95
    231 ms
    Slowest 5% of checks
    200 ms1000
    24 h ago12 h agonow
  • Git Operations
    100% uptime, 30 days
    6 regions, 151 to 323 ms
    Checking
    p50
    240 ms
    Median response
    p95
    456 ms
    Slowest 5% of checks
    500 ms2500
    24 h ago12 h agonow
  • API Requests
    99.67% uptime, 30 days
    6 regions, 200 to 389 ms
    Checking
    p50
    310 ms
    Median response
    p95
    413 ms
    Slowest 5% of checks
    500 ms2500
    24 h ago12 h agonow
  • Issues
    99.41% uptime, 30 days
    6 regions, 586 to 738 ms
    Checking
    p50
    671 ms
    Median response
    p95
    862 ms
    Slowest 5% of checks
    5000 ms25000
    24 h ago12 h agonow
  • Pull Requests
    99.42% uptime, 30 days
    6 regions, 570 to 737 ms
    Checking
    p50
    650 ms
    Median response
    p95
    828 ms
    Slowest 5% of checks
    5000 ms25000
    24 h ago12 h agonow
  • Packages
    100% uptime, 30 days
    6 regions, 145 to 325 ms
    Checking
    p50
    228 ms
    Median response
    p95
    367 ms
    Slowest 5% of checks
    500 ms2500
    24 h ago12 h agonow
  • Pages
    100% uptime, 30 days
    6 regions, 8 to 13 ms
    Checking
    p50
    10 ms
    Median response
    p95
    56 ms
    Slowest 5% of checks
    50 ms250
    24 h ago12 h agonow
  • Raw content
    100% uptime, 30 days
    6 regions, 9 to 14 ms
    Checking
    p50
    11 ms
    Median response
    p95
    157 ms
    Slowest 5% of checks
    50 ms250
    24 h ago12 h agonow
  • Official status feed
    99.99% uptime, 30 days
    5 regions, 217 to 528 ms
    Checking
    p50
    365 ms
    Median response
    p95
    510 ms
    Slowest 5% of checks
    500 ms2500
    24 h ago12 h agonow
  • DNS
    100% uptime, 30 days
    6 regions, 0 to 1 ms
    Checking
    p50
    1 ms
    Median response
    p95
    30 ms
    Slowest 5% of checks
    10 ms50
    24 h ago12 h agonow

Daily strip:99.5% or better99–99.5%95–99%below 95%no data yet

Get notified when GitHub goes down

Follow these 10 checks from your own workspace and get alerted through Slack, email, webhooks, or on-call the moment GitHub goes down. They don't count against your monitor quota. Free plan, no card required.

Notify me about GitHub

About GitHub outages

GitHub hosts source code, reviews, and CI for a very large share of software teams, so a GitHub outage rarely stays a GitHub problem. Pushes fail, pull requests will not merge, Actions runs queue for an hour, and deploy pipelines that pull from GitHub stall silently.

GitHub incidents are often partial: git operations work while Actions is degraded, or the website is fine while the API returns errors. We probe each surface separately, the website, Git over HTTPS, the REST API, Issues and Pull Requests, Packages on ghcr.io, Pages, and raw file downloads, plus GitHub's own status feed, so you can tell which part is affected.

What we check

Every row is a real monitor in Uptimy, running from each of our regions. A failure in some regions marks the row degraded; failures from every region mark it down and open an outage.

CheckTargetExpectsInterval
Website
github.com itself is unreachable or erroring. Browsing repositories and reviewing pull requests is affected.
httpgithub.comHTTP 2001 min
Git Operations
The Git smart-HTTP handshake fails. git clone, fetch, and push over HTTPS are broken.
httpgithub.com/octocat/Hello-World.git/info/refsHTTP 2001 min
API Requests
A real REST API call fails. CLI tools, integrations, Dependabot, and anything using the API break.
httpapi.github.com/repos/octocat/Hello-WorldHTTP 2005 min
Issues
Issue pages are not loading.
httpgithub.com/octocat/Hello-World/issuesHTTP 2002 min
Pull Requests
Pull request pages are not loading. Code review is blocked.
httpgithub.com/octocat/Hello-World/pullsHTTP 2002 min
Packages
The GitHub Container Registry is not answering its normal authentication challenge. docker pull from ghcr.io fails.
httpghcr.io/v2/HTTP 4011 min
Pages
GitHub Pages hosting is unreachable. Project and documentation sites hosted on Pages are down.
httppages.github.comHTTP 2002 min
Raw content
raw.githubusercontent.com is failing. Install scripts, CI, and tools that fetch files directly break.
httpraw.githubusercontent.com/octocat/Hello-World/master/READMEHTTP 2001 min
Official status feed
GitHub's Statuspage-hosted status feed is unreachable. Rare, but it means you cannot rely on the official page either.
httpwww.githubstatus.com/api/v2/status.jsonHTTP 2005 min
DNS
github.com is not resolving. Every GitHub service is unreachable by name.
dnsgithub.comA record resolves1 min

For component-level detail and incident write-ups from the vendor, see GitHub's official status page.

Embed a live GitHub badge

A status badge for your README, wiki, or runbook that updates every minute from these probes and links back to this page. Pick the whole service or a single check.

Preview

GitHub status

Markdown

[![GitHub status](https://www.upti.my/status/github/badge.svg)](https://www.upti.my/status/github?utm_source=badge)

HTML

<a href="https://www.upti.my/status/github?utm_source=badge"><img src="https://www.upti.my/status/github/badge.svg" alt="GitHub status"></a>

Recent GitHub outages we detected

An outage is recorded when a probe fails from every monitoring region and closed when it recovers. Partial and single-region problems show as degraded above but are not listed here.

GitHub is up. Is your GitHub integration?

The incidents that actually hurt are usually not global outages. They are the parts of your own system that depend on GitHub and fail quietly. Here is what teams that rely on GitHub monitor on their side.

Scheduled Actions workflows that quietly stop

GitHub disables scheduled workflows in inactive repositories after 60 days and delays cron triggers under load. A heartbeat on each scheduled workflow tells you when a run did not happen, whatever the cause.

Heartbeat monitoring for scheduled jobs

Deploys that pull from GitHub

If your deploy pipeline clones from GitHub, a GitHub outage becomes a deploy outage. Monitor the deploy result, not only the trigger.

Why started does not mean finished

Webhooks from GitHub into your systems

Push and PR webhooks are retried only briefly. If your receiver relies on them, watch for the gap when they stop arriving.

Webhook monitoring

GitHub status: frequently asked questions

Partially. GitHub runs Actions, git operations, the API, Packages, and Pages as separate systems and they degrade independently. Our API and website probes can both be green while Actions queues are backed up, which is why we also link GitHub's official component-level status.

api.github.com allows 60 unauthenticated requests per hour per IP address, and that budget is shared with anyone else behind the same address. A one-minute probe would sit at the limit and produce false alarms, so we check less often from each region.

Look at the per-region results above. If our probes fail from every region, GitHub has a real outage and it will appear in the outage list. If they succeed everywhere, the problem is most likely on your side: your network, DNS resolver, a browser extension, a corporate proxy, or your own integration. If only some regions fail, GitHub may have a regional incident that does not affect you.

Every probe runs at least every five minutes from each monitoring region, and most run every minute. This page refreshes its data every minute. Uptime figures are calculated from all checks across all regions.

Official status is updated by people after an incident is confirmed and often lags the first failures by many minutes; our probes react within a minute or two. In the other direction, we only see public endpoints, so an internal incident may not show on our probes. Use both.

Yes. Use "Notify me about GitHub" above: your Uptimy workspace follows these exact checks, free plan included, and every outage opens an incident there and routes alerts to Slack, email, webhooks, or on-call. Nothing is duplicated and it doesn't use your monitor quota. Better still, also monitor your own dependency on GitHub: the API route, webhook receiver, or scheduled job that calls it, so you learn about the failure that actually affects your users.

Related

Uptimy is not affiliated with GitHub. GitHub and related marks are the property of their respective owners and are used here only to identify the service being measured. Results reflect the reachability of public endpoints from our monitoring regions and may differ from the vendor's own reporting.

23:00 Β· goodnight

All systems operational

Stop wondering if production is okay.

Tonight, if something breaks, you will know first β€” with the context to fix it and a status page that keeps customers informed. And if nothing breaks, you get to sleep.

Free plan available Β· No credit card required Β· Cancel anytime