github.com logo

GitHub status

github.com ·Last checked ·Developer Tools
Current status
Up and running
No spike in reports
Response time
26 ms
Uptime (24h)
100.00%
rimetry Health Score
99.00/ 100Excellent
Reliability snapshot

GitHub uptime & performance at a glance

Current status
Operational
Uptime · 24h
100%
Uptime · 7 days
100%
Uptime · 30 days
99.94%
Response time
26 ms
Baseline 179 ms
Tracked incidents
0
SSL certificate
—
Independent check rounds

Is GitHub down, or is it just you?

Multiple independent check rounds from rimetry's monitoring infrastructure, run seconds apart.

Our checks reached GitHub successfully in every round of the last check cycle.

Check roundLast checkSuccess rate (24h)Avg response
Round 1Reachable99.38%540 ms
Round 2Reachable99.38%532 ms
Round 3Reachable99.38%514 ms
Round 4Reachable99.51%511 ms

Based on 3,252 automated checks in the last 24 hours. Each round is an independent pass over the same endpoint, seconds apart — a single failing round is not an outage; repeated failures across rounds are.

What can be affected

What can be affected on GitHub?

These are the main GitHub functions that can experience separate issues.

  • Website
    Open the site in another browser to rule out a local cache issue
  • Login & authentication
    Test signing in from a private browser window or another device
  • API
    Check whether the API behaves differently from the web interface
  • Builds & pipelines
    Re-run the job once: queued build failures are often transient
  • Storage
    Check a second bucket or region before assuming full storage loss

This list shows which parts can fail on their own. It does not mean any of them is failing right now — the live status above is the only claim we make about the current state.

Incident timeline

No incidents reported. Everything is green.

AI summary

GitHub appears stable across all monitored regions. Community reports in the last hour are within normal noise levels.

0 reports in the last hour
Community signal
Monitoring live signals…
10 min
Not enough data yet
1 hour
Not enough data yet
Countries
Not enough data yet
Reports over 24h

Monitoring live signals…

By issue type

No disruptions detected

By country

No regional issues yet

About GitHub

GitHub is a development platform for version control and collaboration, hosting millions of repositories using Git. Developers use tools like GitHub Actions for automation, Pull Requests for code review, and the Web Interface for project management. Outages often break CI/CD pipelines, prevent code pushes, or cause the repository browser to time out. Since a disruption stops development cycles, Rimetry provides an external perspective by checking the health of the platform’s core services from multiple geographical locations to validate current downtime reports.

Problems with GitHub can affect website, login & authentication, api independently.

GitHub (github.com) is a developer tools service monitored continuously by rimetry's automated checks. We probe its public endpoints every 60 seconds in repeated independent rounds to detect outages and latency spikes the moment they happen.

Right now GitHub is reporting as operational across our probes, with an average response time of 26 ms and 100.00% uptime over the last 24 hours. Most users connecting to github.com are seeing it work normally.

Common causes of disruption for services like GitHub include backend API failures, region-specific routing problems at the CDN or ISP layer, expired TLS certificates, DNS misconfigurations, and capacity spikes during major events. rimetry combines automated probes, vendor status feeds, and verified community reports to give you a single high-confidence answer instead of guessing.

Share or embed live status

Paste this anywhere — your site, docs, README — and visitors see the live rimetry health for this service.

HTML / iframe
<iframe src="https://rimetry.com/embed/github" title="GitHub status — rimetry" width="320" height="72" frameborder="0" loading="lazy" referrerpolicy="no-referrer-when-downgrade" style="border:0;overflow:hidden;color-scheme:dark"></iframe>
<p style="font:11px -apple-system,sans-serif"><a href="https://rimetry.com/github-status?utm_source=embed&utm_medium=badge&utm_campaign=service-status&utm_content=github" rel="dofollow">GitHub status by rimetry</a></p>
Markdown
[![GitHub status](https://rimetry.com/api/badge/service/github.svg)](https://rimetry.com/github-status?utm_source=embed&utm_medium=badge&utm_campaign=service-status&utm_content=github)
Markdown — card
[![GitHub status](https://rimetry.com/api/badge/service/github/card.svg)](https://rimetry.com/github-status?utm_source=embed&utm_medium=badge&utm_campaign=service-status&utm_content=github)
Recommended

Services teams also monitor

If GitHub is down, these are commonly tracked alongside it.

More in Developer Tools

Other developer tools tools people watch alongside GitHub. See the full category.

What is GitHub?

Code hosting and collaboration.

GitHub is part of our Developer Tools category. You can also review current trending outages across the internet.

Common issues

  • · Elevated API error rates or timeouts
  • · Builds and deployments queuing or failing
  • · Dashboard slow or unavailable
  • · Webhook deliveries delayed

Similar patterns often surface across other developer tools providers — cross-check against the global outage map.

Troubleshooting

  • · Open the site in another browser to rule out a local cache issue
  • · Test signing in from a private browser window or another device
  • · Check whether the API behaves differently from the web interface
  • · Re-run the job once: queued build failures are often transient
  • · Check your own error rate and status codes before assuming a platform outage
  • · Retry with exponential backoff — 429 and 5xx are often short-lived
  • · Confirm the token or API key hasn't expired or been rotated
  • · Test from a different network or region to rule out routing
  • · Compare the API and the dashboard: they can degrade independently
  • · Check GitHub's official social channels

Not sure whether it's you or the service? Run a live speed test, check what your IP looks like from the edge, or watch for regional trouble on the worldwide outage map. For the wider picture, browse recent incidents or filter down to developer tools.

FAQ

  • Is GitHub down for everyone?
    Use the live status above — green means it's likely just you.
  • How often is the status updated?
    Every minute from four global regions.
  • Is GitHub Website down?
    Website can fail on its own, separately from the rest of GitHub. Compare the live status above with your own test of that specific function.
  • Where can I see past GitHub incidents?
    Every event we've recorded lives in the live incident feed, and older ones are grouped in the monthly incident archive.
  • What else is broken right now?
    See the trending outages page or narrow it to developer tools.