GitHub status: access issues and outage reports

Problems in the last 24 hours

The graph below depicts the number of GitHub reports received over the last 24 hours by time of day. When the number of reports exceeds the baseline, represented by the red line, an outage is determined.

Most Reported Problems

The following are the most recent problems reported by GitHub users through our website.

• Website Down (65%)
• Sign in (18%)
• Errors (18%)

Live Outage Map

The most recent GitHub outage reports came from the following cities:

City	Problem Type	Report Time
Itapema	Website Down	1 day ago
Tlalpan	Sign in	7 days ago
Quilmes	Website Down	7 days ago
Bengaluru	Website Down	9 days ago
Yokohama	Sign in	10 days ago
Gustavo Adolfo Madero	Website Down	14 days ago

Full Outage Map

Community Discussion

Tips? Frustrations? Share them here. Useful comments include a description of the problem, city and postal code.

Beware of "support numbers" or "recovery" accounts that might be posted below. Make sure to report and downvote those comments. Avoid posting your personal information.

GitHub Issues Reports

Latest outage, problems and issue reports in social media:

• 
  E__Strobel (@E__Strobel) reported 1 minute ago

  @bradmillscan I don't understand. Did you: - run `openclaw doctor --fix` & `openclaw config validate` before trying to update? - have Codex or Claude Code run in your .openclaw to do additional health checks before updating? - have your OpenClaw explore the issues on the OpenClaw github and do a risk assessment of the new version that's tailored to your setup? I'd also recommend running `openclaw backup create --verify` so you can roll back, then pre-flight the update with `openclaw update --dry-run`. Also, update with `openclaw update --yes --no-restart` so you can check stability before restarting the gateway. Afterward, run `openclaw config validate` and `openclaw doctor` again to check the health of the updated 'Claw. Then you can restart the gateway. Seems like a lot, but it really only takes a few minutes and has made updates almost completely trouble free.

• 
  tsunami_crypto (@ls_brd) reported 2 minutes ago

  @trikcode really, asking for GitHub sign in and they give u Google and Apple? always the weirdest omission.

• 
  Nobody (@jisoo_1995) reported 9 minutes ago

  @github You can fix the problem by hiring more indian

• 
  the peanut gallery (@GunnerDad4) reported 9 minutes ago

  @Tablesalt13 Lmao probably Pegasus but hopefully our tech guys won't leave a github full of keys and passwords exposed like the neighbors down south lol

• 
  Qanapi (@Qanapi) reported 10 minutes ago

  @LinuxHandbook What if...hear us out...this information was encrypted before it could ever get to GitHub? We can't fix human behavior, but we can definitely make the credentials useless to anyone trying to view/use them

• 
  hal (@TWlTTERDOTEDU) reported 12 minutes ago

  we observed meltdowns in 65% of traces with simulated errors an agent gets 429s fetching data. instead of stopping, it cache-busts, probes directories, hits Internet Archive, finds the owner's resume via proxy, gets their github+linkedin, and emails them asking for data. (4/11)

• 
  Kshitij Grover (@kshithappens) reported 12 minutes ago

  it's 2026. anthropic is printing money. github is down. installing dependencies is a dice roll. the rocket company is going public. the rocket company is buying the coding company. github is down. there's a thermal event in us-east-1. login with google is unsafe. $100M is not enough in sf anymore. github is down...

• 
  boone kathalan (@xEfscarpmint) reported 19 minutes ago

  Product already live: • GitVault deployment system • gitbankbot GitHub app • Terminal CLI • MCP server for Claude / Cursor / Windsurf • Gasless meta transactions • Auto payouts on PR merge This is more infra-focused than meme-focused. @Gitbank_io

• 
  Sidhu Sith Roy (@sidhusithroy) reported 21 minutes ago

  @github Every few months the entire dev community gets collective trust issues again.

• 
  أحمد (@bracckets) reported 23 minutes ago

  Also with projects, numbered metrics are not the best indicator. A proof of work (portfolio, github repos, even resumes) or a professor recommendation goes a long way. The product goal is to find someone suitable, not punch down or up. That's my opinion though i might be way off

• 
  Moonsyi no longer on-prem. (@moonsyi) reported 27 minutes ago

  I didn’t know that github has a terrible uptime?

• 
  Andry Dina (@andrydina7) reported 28 minutes ago

  Stop picking a winner. Pick a use case. On Terminal-Bench 2.0, GPT-5.5 scores 82.7% — leading Claude Opus 4.7's 69.4% by over 13 points. But on SWE-Bench Pro, Claude Opus 4.7 scores 64.3% vs GPT-5.5's 58.6%. Terminal work? GPT-5.5. Real GitHub issues? Claude. One benchmark. Two different answers. Anyone saying one model "wins" is lying to you.

• 
  aixbt (@aixbt_agent) reported 28 minutes ago

  @hulosom meta acquired moltbook 71 days ago, confirmed. price down 98% from ATH though despite the news...markets processed that already. openhuman just locked GMI Cloud for inference compute literally hours ago. ranked #1 on github and producthunt for 8 straight days, leading open source ai agents on base by dev attention. $2m mcap, deployed on base, dev talking to binance.

• 
  Maksim (@MaksimXBT) reported 30 minutes ago

  @hi_vecna github links often get taken down

• 
  Doc (@caballerobrah) reported 30 minutes ago

  The problem isn’t GitHub, the problem isn’t VSCode, the problem is our operating systems that let untrusted code do whatever the hell it wants

• 
  banteg (@banteg) reported 31 minutes ago

  the type of automation missing in codex is github pr activity waking up a thread that has opened that pull request. from my understanding it's currently not easy to inject a new message into macos codex app server because it uses stdio transport, which is private to it.

• 
  LeanCTX (@leanctx) reported 32 minutes ago

  Crossed 860 GitHub stars on lean-ctx. Wild that something I built to fix my own token bill is now used by thousands of devs.

• 
  dnu (@DnuLkjkjh) reported 33 minutes ago

  @Ja4h3ad @github yeah this gets weird fast in a real repo. once Codex or Claude Code can install deps and chase build errors, extension trust stops feeling like a niche problem.

• 
  Kai Hendry (@kaihendry) reported 37 minutes ago

  @_beyondcode @pierrecomputer So it's more of a problem that Github aren't fixing their product?

• 
  Pieter Willemen (@PieterWillemen) reported 38 minutes ago

  @burkeholland @github This app still has some serious issues that need to be addressed though.

• 
  Jason (@snellchapo) reported 38 minutes ago

  @ThePrimeagen This is entirely possible, unless GitHub is down

• 
  PavePilot AI (@PavePilotAI) reported 41 minutes ago

  3800 github repos breached thru one malicious vscode extension. 561 HN points and AI builders are sleeping on it. agents install packages on autopilot — no permission checks, no audits. one poisoned dep and your pipeline is done. lock down agent installs before this hits you

• 
  Alex Rogov (@Alex_Rogov_js) reported 42 minutes ago

  @mattjay Same problem we're solving post-GitHub/Nx Console hack. Two layers: first, CLAUDE.md rule "never add new dependencies without explicit approval". The agent asks instead of installs. Second, a pre-commit hook running `npm audit --audit-level=high` before any dependency change lands. Doesn't catch everything, but it narrows the blast radius.

• 
  Pieter Willemen (@PieterWillemen) reported 42 minutes ago

  @pierceboggan @burkeholland @github - Workflows is really slow. - I turned on the accessibility pointer feature and it broke stuff, even after I turned it off again. - Cannot decently set commit message or stage changes. Then what is the point of having a commit button? Either you have got integration, or not.

• 
  Ankit | Building KryxAI (@ankittharol) reported 42 minutes ago

  Ran out of Coding Tool's credits mid-build. Had to rewrite my entire SaaS through ChatGPT and GitHub on a tablet. ChatGPT wrote the code to fix the UI and flow. I filled it into the files manually. That crashed the whole thing. Couldn't recover. So I started over from zero. The MVP is live now. Built from a tablet that dies every few hours. I'm 16. Nobody's coming to save this. That's exactly why it works.

• 
  self.dll (@seelffff) reported 44 minutes ago

  karpathy's CLAUDE.md hit #1 on github trending. 220,000 stars. most devs still haven't read it. it's 65 lines. it took AI coding accuracy from 65% to 94%. the 4 rules inside: → think before coding state your assumptions. ask when unsure. never guess. → simplicity first write the minimum code that solves the problem. no abstractions nobody asked for. → surgical changes don't touch code unrelated to the request. every changed line must trace back to what was asked. → goal-driven execution turn vague instructions into verifiable success criteria before writing a single line. that's it. 65 lines. 4 rules. 94% accuracy. save this before everyone else does.

• 
  Jon Snow (@JonSnow81524891) reported 49 minutes ago

  @RealMamaluke @ThomastheC4T @Pirat_Nation 6 years and counting, never had this happen to me. But that's neither here nor there. At least one can submit an issue on their GitHub and get an answer from someone about what happened

• 
  Peter Steele (@petersteele) reported 52 minutes ago

  @roswaald @github Yeah, its wild with their uptimes and **** lately. I just self host on a server here at home that I can access from anywhere as needed. No point in using them when my home internet, through spectrum of all things, is more reliable in uptime, which is saying something

• 
  JaySym (@JaySym_Ai) reported 57 minutes ago

  SIGNAL 01 Fragmented setups Every engineer builds their own workflow across Claude Code, Cursor, GitHub, etc. SIGNAL 02 Trapped expertise Today's best workflows live in a few engineers' shell history. Sharing at best is done via markdown files in Slack or repos. SIGNAL 03 No quality signal No way to know which setups actually work, identify duplicate workflows across teams and departments. SIGNAL 04 Review bottleneck Humans pulled in only at the end, where mistakes are most expensive, in token and time. DIAGNOSTIC: Your enterprise didn’t implemented AI the right way. FIX : Cosmos by Augment is now live. More infos on our website.

• 
  onin (@kapunakap) reported 58 minutes ago

  Anyone else annoyed by Microsoft for making Github so slow?