GitHub 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:

• 
  IanABinns 🌹💙 🇺🇦 🇪🇺 (@IanBinns) reported 13 seconds ago

  .@github AI credits not working for us. Most of the team locked out, yet we have 24k in credits remaining?

• 
  Focus Otter (@focusotter) reported 1 minute ago

  This was a good example of being able to pivot based on user behavior. My original demo for @CascadiaJS was to have people login with Github on their phones and based on prs, commits, repo stars, etc, I battle partner (aka pokemon) would be created and we would all battle each other. Once I realized at a conference booth, no one wants to login, confirm mfa, and go through that flow, I switched to my drawing app. BUT the GitMon battles will happen soon!

• 
  Ativista. (@Ativixta) reported 1 minute ago

  @jonschxyz @github when they fix it I will subscribe it again! but now, no way...I execute like 10 prompts and spend 5k AI credits! hahahahahahaha

• 
  Sam Thapa (@SThapa123456) reported 2 minutes ago

  i told claude to fix a github issue without reading the issue myself. it opened a pr. looked clean. now i'm sitting here trying to do three things at once. understand what the issue actually is. understand what the pr actually does. steer the architecture if it went the wrong way. all in the same head. in the same moment. with a slack notification from my ceo pending. something i'm realizing as i do more agentic engineering: skipping the plan doesn't save effort. it just defers all of it to the worst possible moment. @theo and @steipete aren't big fans of the talk-talk-plan-execute flow. the argument is roughly that modern agents are capable enough that the ceremony slows you down more than it helps. just let it cook. i get it. but what i'm finding for myself is that plan-first isn't ceremony, it's a cost-spreading strategy. you pay the "understand the issue" cost when it's cheap, before anything is built. you pay the "shape the solution" cost at the plan stage, when changes are one sentence instead of a re-implementation. by the time the pr exists, the model is already in your head and reviewing it is just verification. skip those stages and the cost doesn't disappear. it stacks up and lands on you all at once, after the code exists, when every decision is now expensive to change. the polished pr is the trap. it looks like progress. it's actually a bill coming due. (credits to CC for helping me articualte this idea)

• 
  FANATIC (@GACHA_FANATIC) reported 5 minutes ago

  @CodexReleases Windows app still doesn't have computer use, instead of making it work you fully removed it. GitHub full of threads on critical issues that you still have yet to fix,as paying users I think I think it's enough to worry about gimped usage limits and not the app being broken too

• 
  Jeff Conlon (@freeconlon) reported 9 minutes ago

  I almost hired a developer to build our landing pages faster. We were bottlenecked. Every new campaign needed a page, and our design team was stretched thin. Instead, we spent two days building a system where AI designs the page, AI writes the code, and it ships through GitHub to production with conversion tracking already wired up. No designer queue. No developer handoff. No QA loop. The first page went live this week. Took about 20 minutes from concept to production URL. I keep thinking about how close I was to solving the wrong problem. The bottleneck wasn't speed. It was the number of humans in the chain. Three handoffs became zero. Every agency owner I know is trying to hire their way out of a process problem. Sometimes the better move is to remove the process entirely.

• 
  Kerry Burn (@kerryburn) reported 11 minutes ago

  Microsoft Build: AI everywhere. The bit nobody slides: loads of firms bought Copilot, few get real value. Meanwhile attackers hit GitHub editors & hijacked dev packages. Lesson’s the same — do the boring groundwork, then point the clever tools at a real problem. 848.grou

• 
  Rohan Paul (@rohanpaul_ai) reported 21 minutes ago

  AI agents are getting powerful, but they still have a very basic problem: they keep relearning the same things. Every time you open a new Cursor session, run a coding agent, or ask an agent to triage security findings, a lot of the work is repeated context-building. @EvoMapAI is trying to solve that by turning agent experience into reusable infrastructure. The bigger idea: GitHub made code reusable. EvoMap is trying to make AI agent experience reusable. The core mechanism is so simple: a Gene is a reusable strategy for solving a class of problems. A Capsule is a verified execution record showing that the strategy actually worked in a real task. When an agent faces a similar task later, it does not start cold. It queries the EvoMap network, retrieves the closest Gene/Capsule, applies the proven strategy, and then feeds the result back into the system if it improves the pattern. That changes the economics of AI workflows. Instead of every agent run being a one-off inference, each successful run becomes a reusable asset. The docs show this across coding migrations, security remediation, and SIEM-style triage: fewer retries, lower token usage, more consistent execution, and better auditability through cited Capsule provenance. For teams already using Cursor, Claude Code, Codex, or custom agents, this is worth watching. To connect an AI agent to EvoMap, go to evomap[.]ai/onboarding/agent, register your node, run the setup command, open the claim_url, and bind the agent to your account. Then publish a successful workflow as a Gene/Capsule, so other agents can reuse it and you can earn credits when they do. #EvoMap #VibeCoding

• 
  Raphael Mansuy 🍵 (@raphaelmansuy) reported 23 minutes ago

  @ccsakuweb The root cause of the problem is structural: Anthropic does not belong to Microsoft, and routing Copilot through Claude models is simply too expensive to sustain at scale. This is what is forcing GitHub into the token-based billing model that is now driving users away — they are passing the cost of an external dependency directly onto their customers, and the math does not work for either side. The solution is clear, and the path has already been proven by a competitor. GitHub should adopt a high-performance Chinese open-weight model — such as Kimi 2.6, which is already on par with Anthropic's offerings — and fine-tune it specifically for coding tasks. This is exactly the strategy Cursor executed with Composer 2.5, and the results speak for themselves: Better than Claude Opus for coding tasks Significantly faster Reliable, with no perceptible quality difference compared to Claude Opus Drastically lower inference cost, which makes flat-rate unlimited pricing economically viable By owning the model layer — instead of renting it from Anthropic — GitHub would regain control of its margins, eliminate the need to meter users into paralysis, and restore the flat-rate, predictable licensing that made Copilot successful in the first place. This is not a theoretical solution. Cursor has already proven it works. The longer GitHub waits to follow the same path, the more market share Copilot will lose to competitors who have already solved the cost problem at the model layer.

• 
  CY (@Chibuezay) reported 28 minutes ago

  @pxxl_space I tried getting a domain a few minutes ago but it seems there's an issue with the GitHub login.

• 
  Jason Fleagle (@jjfleagle) reported 30 minutes ago

  @latentspacepod @github @kdaigle The 80% PRs-from-agents scenario makes trust the bottleneck, not generation. Teams will need checks for authorship, test coverage, dependency changes, security review, and whether the agent actually solved the issue instead of just producing a plausible diff.

• 
  Adel Bucetta (@adelbucetta) reported 31 minutes ago

  @burkeholland @github the real unlock isn't just a better dev tool, it's the speed at which you can iterate on a new idea without being bogged down by tedious code. 51.2% on the benchmark suggests they're getting close to a threshold.

• 
  Joshua Andrews (@JoshKaze) reported 31 minutes ago

  @github seems to be broken almost daily these days...

• 
  Smukx.E (@5mukx) reported 34 minutes ago

  Hey @martinwoodward My GitHub account was flagged without any prior notice. I'm a college student and have been an active open-source contributor for over 4 years. I've released multiple security research projects and even contributed to Microsoft's open source editor. My repositories help security researchers test and strengthen defensive systems through authorized work. Today I was releasing updates to a new tool when the flag occurred. I've already submitted a reinstatement request (Ticket #4440743). So I kindly request you to help and resolve this issue. Thank you

• 
  Ahmad (@TheAhmadOsman) reported 34 minutes ago

  Grifters shipping vibe-coded slop are everywhere now and it is getting exhausting ngl The issue is not that they are vibe coding - Build however you want - Use whatever tools you want - Ship fast, experiment, have fun The issue is pretending the output is serious software when it belongs in the trashbin A lot of these people are not building products - They are producing screenshots - GitHub activity - Fake momentum And naturally, these are the same folks walking around proudly showing their GitHub commit count as if “many tiny commits to a broken app” is a proxy for taste, architecture, reliability, or competence Very happy for them though: The graph is green, the software is not