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 (62%)
• Errors (24%)
• Sign in (15%)

Live Outage Map

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

City	Problem Type	Report Time
Bengaluru	Website Down	11 hours ago
Yokohama	Sign in	1 day ago
Gustavo Adolfo Madero	Website Down	5 days ago
Nice	Website Down	6 days ago
Montataire	Sign in	9 days ago
Colima	Website Down	11 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:

• 
  Giri (@Giri_dharan__) reported 1 minute ago

  🧵 2 repos from GitHub trending worth knowing about: 1/ openhuman — "Your Personal AI superintelligence" Private. Local. No cloud. Think of it as a personal AI that runs entirely on your machine — no data sent anywhere. Who it's for: anyone who wants powerful AI without handing their data to a tech giant. 2/ tokenspeed — "speed-of-light LLM inference engine" Running LLMs locally is slow. This is built to fix that. Faster token generation = faster AI responses on your own hardware. Who it's for: devs running models locally, researchers, anyone tired of slow inference. Both are open-source and free. Links in first reply 👇

• 
  LordCuck (@lordcucklol) reported 2 minutes ago

  Dear @Teknium you have now more than 25k able to claim on pumpfun. Do your own research and understand what are creator fees and why you should claim. Login with your GitHub into the @Pumpfun app. $hermes community is here D9pj66xNQcrQ3pfmV2nd6cPVtN7vqFsGGWGooHgpump

• 
  Kyle TechSquidTV (@TechSquidTV) reported 3 minutes ago

  I really hate that GitHub makes you login with SSO on SAML orgs, to just view a public page. Don't want to authenticate? You can see the same content via Incognito mode. Make that make sense

• 
  Elhaidi (@3BissePeace) reported 3 minutes ago

  The Dead Man's Switch: If you realize you are infected and revoke your GitHub token, a hidden local daemon (gh-token-monitor) detects the 40X error and immediately runs rm -rf ~/ to wipe your home directory.

• 
  saburo (@jskoiz) reported 7 minutes ago

  @aegeantic Better than GitHub issues I don’t make the rules

• 
  MarMar Labs (@MarMarLabs) reported 7 minutes ago

  Most people use Codex to write code. The bigger unlock: use it to review code. Drop "@codex review" on any GitHub PR and it posts a real review focused only on P0/P1 issues. Reply "@codex fix the P1 issue" and it pushes the fix to the branch. Set AGENTS.md rules ("don't log PII") and it follows them. Auto-review on every PR = a second pair of eyes that never gets tired. #Codex #AIEngineering

• 
  Sudo su (@sudoingX) reported 8 minutes ago

  @trq212 claude code and claude browser extension connection on linux is broken dude. i've been saying this for 2 months. opened a github issue. team closed it saying it's fixed. it's not fixed. i still can't use it.

• 
  Ruben Distinct (@RDistinct) reported 8 minutes ago

  @eleliayub you missed the point. The recent tanstack supply chain attacks were due to github actions cache being poisoned through a pull request which in turn allowed malicious npm packages to be published as if legit. JS has its own quirks but the recent attack was a ci/cd issue not js.

• 
  JoshXT (@JoshXT) reported 9 minutes ago

  @FrancescoCiull4 Opus 4.6 was the true king before they removed it from GitHub Copilot and Claude Code. Using 5.5 for long running back end tasks and Opus 4.7 for UI work. Opus 4.7 constantly drops the ball and is not thorough at all, terrible experience vs 4.6 and GPT-5.5 is worse at UI than me

• 
  Senior PowerPoint Engineer (@ryxcommar) reported 10 minutes ago

  Github Actions needs to get their **** together. All the recent GA-based supply chain attacks and vulnerabilities-- LiteLLM, Trivy, Tanstack, nx-- are theoretically preventable if you know way too much about Github Actions footguns: hashes for uses, don't store PATs in pull_request_target (or maybe don't use pull_request_target at all, even "securely"), never use classic PATs (unless you need to, of course, which you might because Github *still* doesn't support all features with fine-grained access control). But it's also ridiculous that's the state of things. The entire software supply chain shouldn't be dependent on 100% of the maintainers of the hundreds of dependencies we're downloading indiscriminately knowing the nuances of Github Actions security. Unlike all the AI agents yeeting bullshit code to Github's servers and overwhelming it, all of these security issues with Github Actions have been known for a long while. It doesn't seem like Github has the ***** to mildly inconvenience people by deprecating classic PATs or forcing commit hashes for 3rd party actions or what have you so I guess this will just be how things are forever.

• 
  T.J. Żelawski (@tjzeldev) reported 11 minutes ago

  @jdxcode I wouldn't say actions were misconfigured. I don't recall GitHub docs mentioning anywhere that `pull_request_target` is unsafe and can literally poison your entire workflow cache etc. The problem is the lack of granularity. GitHub actions in general only have permissions either for read or read & write, which concerns everything. I wish I could set a permission for a workflow to be able only to edit PR description or label a PR on GitHub without allowing it to do everything else possible within the repo and its secrets. And don't even start me on how annoying it is to actually enable proper caching for workflows. Doing it is so hard that you don't even think about security when you wonder for the xxth time why there was a cache miss.

• 
  Torrance Davenport (@BuildItWithTj) reported 13 minutes ago

  > "You know that build-pipeline, that Github action we spend hundreds of hours on building. Oh yeah it hasn't been working for weeks now. Just FTP the build man, whatever." > "Yeah it runs on every merge. Oh... it's failing... oh yeah that's been broken for awhile. Oh well..."

• 
  aaalex.hl (@aaalexhl) reported 17 minutes ago

  Github has an outage every week and Gitlab is like yeah instead of taking advantage of our competitor slipping up and gaining more market share, we're gonna fire everyone instead because of, wow you're never gonna believe it, AI

• 
  Marcin Bunsch (@marcinbunsch) reported 18 minutes ago

  The Tanstack supply-chain attack is insane 1. Attacker opened a PR — pull_request_target ran the fork’s code with no approval in the main repo 2.That code poisoned the GitHub Actions cache under a key release.yml would later restore on main 3.When maintainers merged unrelated PRs, the poisoned cache loaded, dumped the runner’s memory, and stole the OIDC token 4.Token means direct publish to npm. 84 malicious versions across 42 packages. Tiny gap with pull_request_target and github actions cache isolation problem. Kudos on fast detection and action!

• 
  Bret Comnes (@bcomnes) reported 19 minutes ago

  @evanplaice Ecosystems like go inherited design notes from npm and github and have also made similar mistakes. It’s not an isolated design issue. Nearly every other ecosystem has the same issues but exploited less due to scale

• 
  Senior PowerPoint Engineer (@ryxcommar) reported 25 minutes ago

  @berenddeboer @tannerlinsley @ErfanEbrahimnia Some of the other supply chain attacks you could easily point to stupid things they did like PAT tokens in pull_request_target or uses not locked to hashes. It's hard to look at this and say Tanstack did anything wrong. Github Actions is the problem.

• 
  Oluwamayowa (@oluwamayowa) reported 25 minutes ago

  It starts with Sources. Vyrric can ingest support conversations, tickets, survey responses, reviews, product analytics, Slack messages, GitHub issues, uploaded transcripts, PDFs, docs, and text evidence. Each source gets synced, indexed, and monitored.

• 
  Lee Ash (@hazae41) reported 27 minutes ago

  @victorbayas @IntCyberDigest Don't use GitHub Actions to publish packages, as it's a scam to make you pay server time

• 
  Senior Product (@Producthaunter) reported 27 minutes ago

  @PeterMcCormack I can't design. I can't code. I don't understand SQL, APIs, Cloud Storage - yet Claude has walked me through Github, Supabase, Vercel and it is deployed and working. This is actually the problem, not a way to go. So you just made another ****.

• 
  Michael 'Rassah' Tozoni ₿⚡🇺🇦 (@Rassah) reported 29 minutes ago

  @btc2infinity @nvk @PeterMcCormack Link it to GitHub, and it will continuously review your code for bugs, security issues, even really weird edge cases.

• 
  Lee Penkman (@LeeLeepenkman) reported 29 minutes ago

  the problem with skills right now often is just that they are too verbose prompts written by people :( like this one for github. like the model can already use github and this entire thing was wasted tokens by codex, like skills are great just dont make a skill for something the model can already do... ..(the yeet skill here in codex cli is used instead of just asking the model to use *** which would have worked instead of reading this huge document about ***)

• 
  Sakti Prasad Bagchi (@saktibagchi) reported 29 minutes ago

  4/ 3. Skip the LLM Completely (Best Choice) When you know exactly what to do → no agent needed. GitHub example: gh issue create --title "Fix bug" --body "Details..." Zero tokens. Lightning fast. 100% reliable.

• 
  Wiedy Mi (@wiedymi) reported 34 minutes ago

  @user50094473 I’m not sure, i will investigate it, if possible open issue on github with details

• 
  Chris Ford (@chrisgford) reported 35 minutes ago

  @hamorahime @sergeynazarovx It was usually a complex error that only a few people somehow experienced. At least I can still experience this in GitHub threads within open-source projects!!

• 
  Haroon (@skywalkerr0x) reported 37 minutes ago

  Dart Live runs the full Dart VM in your browser via WebAssembly, compiler, analyzer, hot reload, all client-side. It's only 7.6 MB gzipped and needs no server. Hosted on GitHub Pages.

• 
  Alex Cortright (@Cortright_ok) reported 41 minutes ago

  @dmesg @Punished_HIMBY @zzarakkk where isn’t it? github has published data showed massive increase in production. more shopify apps are published than ever before. the apple app store is literally flooded to the gills with apps more than ever historically. the list goes on forever. it’s actually a problem? people are producing TOO much with it and the barrier to enter is TOO low right now. how blind do you have to he to not see ai everywhere? the problem isn’t ai not producing anything it’s producing too much and most people are not great with it so the quality of output has no guardrails.

• 
  DarkEmpath888 (@Darkempath888) reported 44 minutes ago

  @githubstatus **** GITHUB. IT NEEDS TO BE SHUT DOWN FOR VIOLATING MY DAMN RIGHTS

• 
  Ben Clavié (@bclavie) reported 44 minutes ago

  I think people are missing the bigger issue here. If it wipes all your data if GitHub errors out with the wrong error code, then the odds all your data will be gone within a week is roughly +/- 100%

• 
  Karanjot Singh (@Karanjotdulay) reported 53 minutes ago

  Day 3 of building in public. Shipped my first MCP server: wiki-hub-mcp. Your LLM reads a source once and writes structured wiki pages to a GitHub repo you own. No vector database. No RAG pipeline. Plain markdown files that grow over time. 18 tools: 1) Add sources (URLs or text) 2) Search with BM25 3) Track contradictions 4) Run health checks npx -y wiki-hub-mcp

• 
  Nathan Alderman (@Nalderman37) reported 55 minutes ago

  @bcherny Yes, it’s true but with a couple of caveats. Chrome has browser timeouts so what worked for me is the stealth browser GitHub repo and that solved a lot of browser automation problems for me. With that tool +cowork, you can do anything.