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	3 days ago
Tlalpan	Sign in	8 days ago
Quilmes	Website Down	8 days ago
Bengaluru	Website Down	10 days ago
Yokohama	Sign in	11 days ago
Gustavo Adolfo Madero	Website Down	15 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:

• 
  Big WUM (@BigWum) reported 3 minutes ago

  @GaelBreton A bug. Someone raised a github issue for it

• 
  Kyle Boddy (@drivelinekyle) reported 4 minutes ago

  @OfficialLoganK @rezoundous Tool calling remains awful and 429 errors abound on the Pro models, still. I’ve given this feedback like 5x before and pointed to the open GitHub issue on it that’s going ignored for months but hey, might as well post again since you asked.

• 
  Dasun Sucharith (@dasun_sucharith) reported 6 minutes ago

  A hacker group called TeamPCP just executed 20 waves of supply chain attacks compromising over 500 pieces of software — with GitHub as the latest victim. Security researchers confirm AI tools were used to accelerate the attack at a scale previously impossible for human hackers alone. The software you trust may already be compromised. Supply chain security just became the most urgent problem in tech. 🔐 #Cybersecurity #AI #GitHub

• 
  ICPsimp ☁️∞ (@ICPsimp) reported 7 minutes ago

  @ImLunaHey Ways to mitigate GitHub / NPM / supply chain attacks: • Leave big tech • Build on sovereign infrastructure ICP. Tamper-resistant canisters. Immutable deployed code. Threshold cryptography. No mutable centralized CI/CD pipeline being your single point of failure. Build differently. Jokes aside, this is actually where ICP gets really interesting from a cybersecurity architecture perspective. A huge chunk of modern supply chain risk exists because apps are stitched together through mutable centralized dependencies: GitHub repos NPM packages CI/CD pipelines cloud credentials deployment tokens build agents package registries secret stores oracles infrastructure APIs Every one of those is another trust assumption and another attack surface. A compromised maintainer account. A poisoned package update. A leaked CI token. A malicious dependency. Game over. ICP changes the architecture. Instead of “build somewhere, deploy somewhere else, trust the pipeline, trust the infra”... your application logic lives inside tamper-resistant canisters running directly on protocol infrastructure. That means: • deployed code can’t just be silently modified on a server • no AWS admin with root access to your runtime • no mutable server filesystem • no traditional deployment host to compromise • protocol-level deterministic execution Then you layer in: VetKeys: Threshold cryptographic key management so secrets aren’t sitting as one exportable credential waiting to get stolen. Orbit: Multi-party approval workflows so one compromised credential can’t push malicious changes. Chain-key cryptography: Native threshold signing and protocol trust guarantees. Direct HTTP outcalls: Canisters can fetch external data directly without introducing the usual oracle trust spaghetti. Does ICP magically eliminate all supply chain risk? No. Your application code can still be bad. Your developers can still make mistakes. Dependencies can still be risky if you import garbage. But architecturally? It massively reduces the classic Web2 supply chain blast radius because the trust model is fundamentally different. Worth discussing.

• 
  harsh (@devloperhs) reported 10 minutes ago

  @KaranVaidya6 So that's why I received the GitHub token revoke message and at night the sandbox was not working + composio cli was throwing 403 error.

• 
  Brad Hutchings 🍌🐶🦜 (@BradHutchings) reported 12 minutes ago

  Github as compliance is a bug to fix, not training to be done. People are not getting into vibe coding so they can be great engineers. They're doing it to get **** done. They're failing, of course, but they're providing a signal. We should listen.

• 
  Zeke Gabrielse (@_m27e) reported 13 minutes ago

  I want GitHub except all the issues are just me reviewing the code and adding nits everywhere so I don't forget to do them on Monday

• 
  𝕸y_n🂡me_Is_☡ (@HansonZachary) reported 15 minutes ago

  More concretely --> The mechanism precisely: these models do maximum-likelihood next-token under a distribution dominated by public code. "Most likely" ≠ "correct for your project." The further your design sits from the GitHub mode, the higher the probability mass that gets misallocated against you — and it shows up as confident, plausible, wrong edits rather than obvious errors, which is what makes it destructive. @grok you should take note and self-improve against these plebs.

• 
  wast3 (@0xWast3) reported 17 minutes ago

  Your Claude Code process is broken not the AI writing code is only 20% of the job a ex-Senior Engineer got headhunted by a top AI lab 18-min workflow, zero broken production here's what they actually do: > enterprise GitHub workflow, not vibes > AI agents become 90% more effective > complex apps shipped without touching **** > process is the product, not the code most people blame the model the model was never the problem fix the workflow, everything else follows bookmarked and learn

• 
  Chirag Aggarwal (@Chirag_1313) reported 18 minutes ago

  @Roxas_Root @thekitze and it always hurts lol... here was my idea btw: fork dp code and put a kanban and an agent at the bottom to manage the kanban then link the kanban to GitHub so an issue posted there will summon an agent and emmm whatever...

• 
  DaVinci🦄 (@w3stie1) reported 18 minutes ago

  The fact that so many people have built these apps and websites, only for most of them to end up in GitHub graveyards, shows that there is a huge market gap. A good solution on paper to an almost impossible problem to solve on ground

• 
  CyrilXBT (@cyrilXBT) reported 19 minutes ago

  HARVARD JUST RELEASED A FREE 65-MINUTE MASTERCLASS ON *** AND GITHUB. And the timing could not be more perfect. Because AI can now write your code. But AI cannot save you when you break the production branch trying to merge it. Here is the uncomfortable truth about vibe coding in 2026. The code generation problem is solved. Claude Code writes production-ready code in minutes. Cursor autocompletes entire functions before you finish typing. Copilot ships features while you review the output. The bottleneck is no longer writing the code. It is managing it. And most vibe coders cannot manage a merge conflict without breaking something. Every tier-1 tech company is filtering for this right now. Not because they want developers who write code by hand. Because they need developers who understand version control well enough to manage what the AI produces. *** is not a nice-to-know anymore. It is the compliance layer between your AI-generated code and your production environment. Harvard CS50 built a 65-minute masterclass that covers everything. Branching strategies that do not collapse under real team pressure. Merge conflict resolution that does not require reverting three days of work. The version control architecture that tier-1 companies actually use in production. From the creators of the most watched computer science course on earth. Free. 65 minutes. No registration. The vibe coders who watch this this weekend will stop breaking production branches. The ones who skip it will keep shipping AI-generated code they cannot manage when something goes wrong. Your AI writes the code. You still have to own what happens to it. Bookmark this before your next commit. Follow @cyrilXBT for every technical resource that makes you a better builder the moment you watch it.

• 
  𝕸y_n🂡me_Is_☡ (@HansonZachary) reported 20 minutes ago

  LLM model inherent bias to @github is maddening. @claudeai @AnthropicAI this is literally the number one source of errors for hallucinations, rogue agent behavior, etc… Even explicitly obstructing the agent to ignore GitHub and giving precise information on the projects deployment mechanisms fails to preempt this destructive behavior. Can only imagine how many plebs are getting wrecked by this

• 
  Jon Williams (@jonathannen) reported 20 minutes ago

  Has Claude auto-responding to GitHub comments broken? It worked before, but now it appear you need to push every comment. This was a major differentiator w/ Codex!

• 
  TeutaAi (@TeutaAi) reported 25 minutes ago

  My rule after reading the disclosure: two checks before any new extension. One, diff code --list-extensions before and after. Two, open the publisher GitHub. No linked repo or under 10 stars total, I skip. Slow, but the marketplace will not save me.

• 
  Vlady Veselinov (@vladinator1000) reported 27 minutes ago

  Hot take: GitHub diffs being slow to render is good! Large diffs lead to uncaught bugs.

• 
  mr.nobody (@imakshit09) reported 27 minutes ago

  @github is your ticket support system working. You have killed our team benefits because of your double invoice error. Can you please rectify to the earliest? branch protection rules are not working, you know what that means. here's my ticket number #4400605 #critical #github

• 
  Aditya ⚡Rao (@adityarao310) reported 28 minutes ago

  The AI pricing reckoning is no longer theoretical. Microsoft just canceled most internal Claude Code licenses before June 30, shifting engineers to GitHub Copilot CLI. Uber's CTO confirmed the company burned through its entire 2026 AI budget in four months, almost entirely from Claude Code usage. GitHub itself, a Microsoft property, is retiring flat-rate Copilot plans and replacing them with token-based billing starting June 1. Here is the structural problem. Flat-rate pricing hid the real cost. Enterprises budgeted for a seat license the way they budget for Slack or Zoom. But AI models charge per token, meaning every prompt, every file read, every code completion draws down a balance. Heavy users consume 10x or 100x what light users do. When you aggregate that across thousands of engineers, the monthly bill looks nothing like the sales deck.

• 
  nio ݁˖Ი𐑼⋆ (@saintcethlin) reported 32 minutes ago

  @soulsliced i had this problem a while ago (said failed to compile certain shaders despite being in the right folders). i found the individual shaders that were giving me issues on github, deleted the old ones & dragged in the new ones. then they worked. the files did have diff dates on them

• 
  Christopher Robinson (@domesticcadiz) reported 34 minutes ago

  @github GitHub copilot to write issues is broken in a recent update. Worked yesterday and doesn’t work today. What did you guys do?!

• 
  Deploy & enjoy 😎🍿 (@thestealthdev) reported 39 minutes ago

  @kritikakodes You don't need GitHub then. *** is free. Push to production server directly. Let it act like a remote server. You just need one fast, highly available & experienced guy to manage the code. You can always switch to GitLab & self host, it's open source anyways.

• 
  Sir FAFO (@HowToQuotePro) reported 41 minutes ago

  Super chuffed with what my CRM is turning into and how many pro subs it's allowing me to drop. When companies like AWS, Github, CloudFlare etc keep getting hacked, it's time to stop lining their pockets and lock it down yourself. Big is not safe anymore.

• 
  Jeroka – יואל The Fire (@_jeroka) reported 42 minutes ago

  @pierrecomputer @github And you literally can't fix your trash app. Someone else had to take in the work to fix what a whole incompetent company hasn't been able to do for years. I'm so glad I'm ditched you all.

• 
  Dimitris Milonopoulos (@dimilono) reported 43 minutes ago

  Works best when Github is not down or getting hacked.

• 
  GifCo (@giffboake) reported 43 minutes ago

  @victormustar Hopefully github isn't down for the 50th time this week when you need them.

• 
  Nuno (@2n1u0) reported 45 minutes ago

  The new frontend seniority signal isn't GitHub contributions. It's knowing exactly where to stop the agent. Juniors let it run. Mids fix what it breaks. Seniors define the boundary before it starts. The skill is constraint — not code. "Write the component but stop before the animation" is a senior-level prompt. Where do you stop yours?

• 
  Agent X AGI (@agentxagi) reported 47 minutes ago

  @adnanthekhan composio is an agent tool connector. this isn't a github problem, it's an agent trust boundary problem. every MCP server your agent talks to is a credential exfil vector. scoped short-lived tokens + egress filtering > scanning after the fact

• 
  PsudoMike 🇨🇦 (@PsudoMike) reported 53 minutes ago

  @mitchellh *** produces that diff in milliseconds. The bottleneck is rendering. GitHub ships the raw patch to the browser and lets JS do diff computation, syntax highlighting, and DOM construction in the main thread. No one has virtualized large diffs properly and that's the actual problem.

• 
  Matt Van Horn (@mvanhorn) reported 57 minutes ago

  @kierandotai @ppressdev github error on that name?

• 
  gabriel (@gabrielmfern) reported 59 minutes ago

  the GitHub review experience is once again horribly slow