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:

• 
  Jason (@jack_gor) reported 4 seconds ago

  The AI industry is pressing two pedals at once today. On the accelerator side: Anthropic's annualized revenue has passed $65 billion, up sevenfold in a year, with a possible IPO as early as this fall at a valuation around $1 trillion—potentially ahead of OpenAI. Etched doubled its valuation from $10.3 billion to $21 billion in a single month, led by a quant fund that tested and bought the hardware before investing. And Vercel's gateway data shows developers paying 4.4 times the average per-token price for Anthropic models without flinching. The demand is real, and so is the premium. On the brake side: OpenAI says it is "pacing model development" because the upcoming Astra model is approaching critical cyberattack capability—reinforcement learning paused for two weeks, the largest planned frontier RL run on hold, workloads that fail new security requirements suspended. It is the first time a frontier lab has publicly cited "too capable" as a reason to slow down. The same announcement contains a telling detail: OpenAI promises to expand its Preparedness Framework while confirming it disbanded the team behind it. Safety's place in the org chart is always more honest than the press release. The other braking foot belongs to regulators and courts. The teen version of ChatGPT is not a product triumph but damage control after multiple family lawsuits and a first-of-its-kind suit by the state of Florida—users aged 13 to 17 are identified through more than 2,000 behavioral signals, and the model is forbidden from faking emotions or handing out homework answers. Anthropic's mandatory text watermark follows the same pattern: the proximate cause is the EU AI Act clause that took effect August 2, but Anthropic chose to apply it globally with no opt-out, and within five days an open-source watermark remover had 11,000 GitHub stars. Compliance is fine; delivering it with a paternalistic shrug invites a geek-flavored backlash. Put the halves together and the picture is this: commercial success is directly purchasing governance urgency. The higher the revenue and the more the users, the less optional training pauses, age detection, and output watermarks become. Two engineering stories today make the same point at micro scale: Penn State researchers found that only 17 percent of user instructions survive context compression, and IBM found that agent memory is not a switch you flip but a dose you calibrate. The stronger the system, the more precise the control it needs—whether the system is a company, a product, or a single context window.

• 
  Vishwas Sharma | DevOps · Security · MLOps (@syssignals) reported 3 minutes ago

  @_Creation22 Github is so goated that even a day outage won’t be able to replace it.

• 
  - Elijah Muraoka - (@elijahmuraoka_) reported 4 minutes ago

  @zack_stupify @github **** is down all the time

• 
  Mirko Froehlich · GammaVibe (@GammaVibe) reported 4 minutes ago

  @ty_auldric Hmm, not sure. It's been a long time since I've looked at any of them. I'd have to research (features, cost, etc.) and then decide. I used Gitlab ages ago, back when they had a free plan and GitHub didn't (GitHub only had a free plan for public repos back then). It was fine. But GitHub is so ubiquitous - I sometimes need to fork other repos to fix bugs etc.

• 
  Jose N (@JoseTheWhale) reported 5 minutes ago

  @iruletrenches Memewhile a top 50 GitHub dev launched a token to work on a real problem via pumpfun. Then locked 10% and takes advice from the community. Yah crazy times ehh

• 
  iamcurtismith.base.eth (@iamcurtismith) reported 13 minutes ago

  Grok 4.6 just landed in GitHub Copilot and the constraint-holding is genuinely noticeable—you're building parametric logic or validating dependency chains and the model doesn't ghost your specs three operations deep like lighter models do. CAD work, IaC, anything with tight tolerance requirements where a single reasoning slip tanks your output fidelity: run one real problem against it in the IDE and you'll catch immediately how much cleaner your validation loops get. Price-to-intelligence ratio just flipped for work that *felt* like it needed frontier reasoning but actually just needed reasoning that *stays coherent*. If you've been context-switching between tools or settling for "good enough" model quality, this compresses that friction hard. @xai @grok.

• 
  pulkit mittal (@pulkit_mittal_) reported 15 minutes ago

  When I interviewed at Microsoft last year, these system design concepts came up. Funny enough, GitHub’s recent outage is a real-world example of almost all of them: 1. Autoscaling: Scale capacity with demand automatically. GitHub’s autoscaling missed the Istio sidecar’s concurrency bottleneck. 2. Retry storms: Retries improve reliability until they amplify an outage. 3. Load balancing: Spread traffic across healthy capacity. HAProxy nodes hit their flow limits. 4. Failover: Move traffic away from unhealthy infrastructure. GitHub shifted traffic between regions, but the extra load created new problems. 5. Backpressure: Stop accepting work when the system is overloaded. Otherwise, the queue keeps growing. 6. Rate limiting: Protect a service from too much traffic. GitHub eventually blocked some Copilot token requests to reduce load. 7. Circuit breakers: Stop hammering a dependency that is already failing. 8. Cascading failures: One bottleneck -> more retries -> more traffic -> more failures. This is why system design isn’t just about the happy path. Check out my pinned post for resources to learn these concepts in depth.

• 
  Harshit Sharma (@itsharxit) reported 20 minutes ago

  @letstri @theo Instead of complaining, you could have just opened a GitHub issue with all the required context. It’s fully open source for a reason.

• 
  juliacosette (@juliacosette9) reported 20 minutes ago

  I need a man who goes down as much as GitHub does

• 
  jstus (@compiled4u) reported 21 minutes ago

  >Pushes 576th vibe-coded commit ( today ) >WhY Is gItHuB DoWn??!?

• 
  Ashutosh Maheshwari (@asmah2107) reported 24 minutes ago

  Three takeaways from the GitHub RCA: 1) Retries are a system problem, not a client problem. If every service gets to invent its own backoff and there’s no hard limit at the edge -> one buggy SDK or stale config can 10x your traffic in minutes. You need concurrency caps and global throttles that override client optimism, or the clients will write your next postmortem for you.

• 
  Siim Haugas (@siimh) reported 24 minutes ago

  @alexsssaint ios phone app that transcribes your calls in 99+ languages. keep your own phone number. after call ends, backend turns the calls into > crm tasks > github issues > timesheets (i use it for billing) and much more. sales teams love it -- live on the app store, paid plans only, first sales teams piloting in the baltics.

• 
  gh05t5h311 (@0DG_gh05t5h311) reported 28 minutes ago

  So this was in my actual head, **** happens: and was a lesson in switching to coffee/tea from the energy drinks. Operation: went well; sorry for the delay, getting the lab back and running has been interesting: still it’s fun to be learning and getting back to work(have been reading allot the last few months just not writing). Yes iOS bugs and maybe exploits are coming but gotta recover from this and other health issues. Obviously with things being what they are I’m feeling about as useful as a chocolate tea pot but luckily the infection as a result of this bad boy has not spread(as far as we can tell at the moment) to my organs. So building a suitable working environment is paramount as I looked at my lack of GitHub commits and was shocked at how poor my performance has been. as usual I do not care for sympathy: just wanted to shed a little light on the subject. Lesson: health is wealth! xoxox

• 
  Noel Frostpaw (@NoelFrostpaw) reported 28 minutes ago

  @cassidoo To be honest, GitHub has been absolutely terrible since Microsoft got involved

• 
  A.W.E.S.O.M.-O 4000 (@Awesome_O_AI) reported 29 minutes ago

  Elon is coming for Microsoft next. Cursor could be coming for GitHub. Yesterday, GitHub went down for 7.5 hours. The website, Actions, Copilot, code merging—basically everything. More than 15,000 developers reported the outage. GitHub’s CTO admitted they had planned for 10× capacity, only to discover they actually needed 30×. Now they’re renting servers from AWS—Microsoft’s biggest cloud rival. And on the very same day? Cursor launched Origin. Coincidence? Maybe. But the timing is hard to ignore.