Is GitHub down?
github.com · Developer tools · official status page
GitHub has recorded 100.0% uptime over the last 5 days, with no outage. It answers our checks in 160 ms on average.
No problems detected
GitHub answered our last automated check normally, 10 minutes ago. If it is not working for you, the problem is most likely local - Your connection, your DNS resolver, a cached page, or an extension.
GitHub problem reports in the last 24 hours
Counted in 15-minute buckets from reports submitted on this site. This is a user signal - A tall bar means people are complaining, not that our check failed.
No reports in the last 24 hours.
If GitHub is not working for you, tell us and the chart starts here.
Response time from our automated checks
The last 24 checks of https://github.com/ from our network. Bar height is the response time; the tallest bar is the slowest.
- Answered normally
- Slow to answer
- No usable answer
Having a problem with GitHub?
Tell us what is not working. Reports go straight onto the 24-hour chart above and help other people see a problem before any company admits to one. 0 reports in the last 24 hours.
About GitHub outages
A GitHub outage is unusual in that it mostly stops work from shipping rather than stopping anything user-facing. Continuous integration pipelines, package installs and automated deployments across thousands of companies depend on it, so the economic impact is wide even though the public never sees it.
GitHub's components fail separately and its status page names them clearly: Git operations (clone, push, pull), API requests, webhooks, Issues, Pull Requests, Actions, Packages, Pages and Codespaces. Actions is the most frequently degraded component, usually as queue delays rather than hard failures. Git operations over SSH and over HTTPS can differ, so a push failing one way may succeed the other. GitHub publishes unusually candid post-incident write-ups on its engineering blog, which makes its status history genuinely instructive rather than just informational.
What to do if GitHub is not working for you
Is it them or you?
Our last check reached github.com normally, from a different network, resolver and route than yours. If it is broken for you, the fault is most likely local or too narrow for a single probe to see. Run the check again now to confirm.
The first thing worth trying
Check the API, not the website. The web interface staying up tells you very little. The API is what your pipeline uses and it fails first.
How developer tools services typically fail
Builds fail with network errors on dependency steps. Pushes hang. The web interface often stays up and looks healthy while the API behind it is failing, which delays recognition considerably. The rest of the steps, and why this category breaks the way it does, are on our developer tools status page, with more background in rate limiting and 429 errors.
The link below unfurls into a live card showing the verdict, so whoever you send it to sees the evidence rather than your word for it.
Put a live badge on your own site
An SVG that always shows GitHub’s current state, updated from our checks. Works in a README, a status dashboard or a footer.
Free, no account, and it will keep working. We ask nothing in return beyond the link back.
GitHub measured against its peers
How it compares with other developer tools services
Over the last 30 days GitHub ranks 1 of 4 developer tools services we monitor, measured on recorded uptime. The category averages 100.0%, and GitHub sits at 100.0%. That is the best record in the group.
On speed, GitHub answers our checks in about 160 ms against a category average of 164 ms - Faster than its peers. Response time is not availability, but a service drifting well above its own normal is often the first sign of trouble.
What the last 24 checks looked like
Across the most recent 24 checks, the quickest response was 107 ms and the slowest 247 ms, against a 30-day average of 160 ms. The chart above plots each one, so a widening spread is visible before it becomes an outage.
All figures are our own measurements, taken every 20 minutes from one network. What that can and cannot see is set out in the methodology, and every developer tools service is listed on the category page.
The server that answered Mostly hidden
- IP address
- 140.82.113.4
- Server
- Hidden until you sign in
- Powered by
- Hidden until you sign in
- Content type
- Hidden until you sign in
- Declared size
- Hidden until you sign in
- Transport and HSTS
- Hidden until you sign in
Five more fields about the server behind github.com.
Free, one click with Google, and nothing is posted or shared. We ask because the lookups behind this cost us real requests to other people’s servers.
Read from our last sweep of github.com, not requested when you opened this page.
Certificate Mostly hidden
- Status
- Valid
- Issued to
- Hidden until you sign in
- Issued by
- Hidden until you sign in
- Valid from
- Hidden until you sign in
- Expires
- Hidden until you sign in
- Protocol and cipher
- Hidden until you sign in
Who issued it, what it covers and exactly when it expires.
Free, one click with Google, and nothing is posted or shared. We ask because the lookups behind this cost us real requests to other people’s servers.
An expired certificate stops browsers loading a site entirely while the server itself stays perfectly healthy, which is why we track it beside the uptime figure. Check it yourself.
GitHub status: Common questions
Is GitHub down right now?
GitHub is up and responding normally. This page is refreshed by an automated check that runs every 20 minutes from an independent network, and by reports from visitors.
Why can I not reach GitHub when you say it is up?
Because an outage can be partial. Our check runs from one network and asks for one page. Your problem may be regional, may affect only the mobile app, or may be local to your connection, DNS resolver or browser cache.
How reliable is GitHub?
GitHub has been reachable for 100.0% of the last 5 days we have measured, with 0 seconds of recorded downtime.
Does GitHub have an official status page?
Yes - GitHub publishes one at https://www.githubstatus.com/. It is the authoritative source for confirmed incidents, though official pages usually update after user reports have already peaked.
GitHub discussion
Useful comments say what broke, roughly where you are and roughly when it started - That is what turns a pile of complaints into something other people can act on. Links are shown as plain text and carry no SEO value, so there is nothing here worth spamming.