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:

• 
  Ori Livni (@oriSomething) reported 1 minute ago

  @zeeg With all the problems Github has, the alternatives are worse. I’ve used some of them. One for 4 years

• 
  Teja (@tejalogs) reported 6 minutes ago

  the recent news about ruflo, a new multi-agent orchestration framework for claude code, isn't just another github repo gaining traction; it's a very specific bellwether for how solo builders like me are about to rethink our development loops. most people will see a sophisticated new library and assume it's for enterprise teams with massive budgets, but what ruflo actually signals is a dramatic lowering of the barrier to deploying complex, multi-step agentic workflows directly into production with tools like anthropic's claude 3 opus or sonnet, all without needing to hire an army of prompt engineers or shell out for a dedicated mlo[ps] team. this isn't just about better code generation; it's about enabling individual developers to orchestrate entire software systems, not just components. what’s often missed in the hype around multi-agent systems is the sheer complexity of state management and inter-agent communication, which is precisely what ruflo aims to abstract away. historically, building something with, say, 5 distinct agents one for planning, one for code generation, another for testing, a fourth for documentation, and a fifth for deployment would involve writing thousands of lines of boilerplate code just to pass information, handle errors, and manage context between them. this is where the real friction lies, not in the individual agent's capabilities. we’ve seen similar attempts with tools like crewai or autogen, but ruflo’s focus specifically on claude code’s strengths its nuanced reasoning and longer context windows combined with a structured approach to flow definition, is a distinct leap. it shifts the problem from "how do i make my llm write better code?" to "how do i make my llm build an entire, working feature?" this is the difference between a smart code assistant like cursor and a full-stack engineering partner. i ran into this exact orchestration problem building the second look flutter app, which uses ai for behavioral analysis. my initial prototype had a simple chain: transcribe audio, extract sentiment, then flag anomalies. but when i tried to add agents for summarizing key discussion points and cross-referencing against historical patterns, the complexity exploded. i ended up managing a fastapi backend with individual endpoints for each stage, passing large json blobs between them, and writing custom retry logic. the cost, both in development time and firebase document reads, became prohibitive quickly. specifically, getting a reliable chain with three distinct ai stages transcription, sentiment, and summarization would cause p95 latency to hit 8-10 seconds for a 5-minute audio file, and if i scaled up concurrent users past 5, my function invocation errors from missing context or malformed json would spike to 15%. a ruflo-like abstraction for that specific problem, especially with claude code's ability to reason about the overall task, would have let me ship those richer features in a third of the time, likely cutting my api costs by 20-30% because of more efficient token usage and less retrying. the uncomfortable implication of ruflo and similar agent orchestration frameworks is that the "full-stack developer" as a distinct role will evolve dramatically within the next 18-24 months. we're already seeing a contraction in junior dev roles; this will extend to mid-level roles focused on stitching together disparate services. instead of writing the boilerplate to glue apis, developers will become architects of agent systems, defining the interactions and flows rather than the explicit code for every single step. the mental model to adopt here is moving from imperative programming, where you tell the computer how to do everything, to declarative programming for entire software pipelines, where you tell the ai what the desired outcome is, and the agents figure out the how. expect to see a surge in "agent architect" roles, where understanding prompt engineering, context management, and failure modes across multiple llms becomes more valuable than writing a perfect react component. the critical skill won't be writing the code, but designing the intelligent system that writes and deploys the code

• 
  Darren Shepherd (@ibuildthecloud) reported 7 minutes ago

  Oh my gosh stop it, people. We don't need a new GitHub. If your only complaint about GitHub is that GitHub sucks, GitHub can just fix that. We only need a new thing if it solves a new problem that GitHub can't do.

• 
  Jhon (@JhonCaldeira_) reported 10 minutes ago

  You gotta be kidding that GitHub is down… again. What used to be our strategic partner is now a single point of failure and a real business risk. We can’t keep exposing our operations to this level of instability. Reliability isn’t optional. It’s foundational. At this point we’re seriously evaluating a full migration to GitLab. Enough is enough.

• 
  JJJ (@fullBased) reported 11 minutes ago

  @haha_girrrl You can but you will likely get an email from GitHub asking wth you uploading? If you don’t justify it they just shut you down :)

• 
  Doug Dimmadome (@tallhatdoug) reported 13 minutes ago

  @Una @github congratulations on fixing a non-existent problem instead of a real one

• 
  Noah (@noahreeveshq) reported 14 minutes ago

  i see why everyone was complaining about github now. a customer told me about a bug and i quickly fixed it and pushed to production. CI/CD is setup so i assumed it worked fine. it didn’t. i told the customer i fixed it and when he tried a couple days later, it was still broken! so embarrassing! can’t imagine if it were more than one user! i guess now i have to check my deploy status every time i deploy?? no way we gotta do that @github right?!?!

• 
  Zach Daniel (@ZachSDaniel1) reported 16 minutes ago

  @InfinityDZ @RootCert Not currently. We have many of the bases covered. Only other things are oauth2 server and file storage(in GitHub now but unreleased).

• 
  Guri Singh (@heygurisingh) reported 17 minutes ago

  Anthropic will never tell you this. Vanilla Claude Code is intentionally inefficient. Every file operation makes a separate tool call. Every call carries all prior context. The token bill compounds the longer you work. The fix has been sitting on GitHub the whole time. It's called WozCode. Plugin that sits on top of Claude Code, replaces the default file tools with batched versions. Same prompts. Same model. Fraction of the spend. → 9 tool calls to find and edit files becomes 2 → Sessions that died at 45 minutes now run 80 → Database tasks 5-10x faster on real benchmarks → Works in terminal, VS Code, and Conductor → Two commands to install Run /woz-savings on your history and tell me you're not furious.

• 
  Abdulmajeed (@0xabma) reported 19 minutes ago

  @RhysSullivan deep down we all know microsoft trained its github copilot on people’s repos but we just can’t prove it because copilot still suck

• 
  dilan (@the_real_dilan) reported 20 minutes ago

  @icanvardar I've always considered uptime to be a boring metric because things rarely go down and often sit well above 99% - Until Github 😭😭

• 
  KiwiNod (@Kiwi_Nod) reported 21 minutes ago

  @Cvpt_Asheeru @pharos_network 404 on that repo. "[yourhandle]" isn't a valid GitHub username. But the technical specificity is real — 1,200 blocks, RPC pulls, variance under load. Someone who actually knows R doesn't fake the methodology. Fix the link. Show me the real repo and I'll take this seriously. 🥝

• 
  Aaryan Kapoor (@TheAaryanKapoor) reported 22 minutes ago

  @ItsAlexhere0 . Claude - the trial version . Codex - can get a saas up . Cursor - don't use opus . Antigravity - they're still around? . GitHub Copilot - is it down?

• 
  Ben Badejo (@BenjaminBadejo) reported 24 minutes ago

  @MohandesDavid You can submit it as a pull request (“fix(docs) - description) on Github). You can have your agent do it for you.

• 
  Jacob (@tugmoat) reported 24 minutes ago

  @esrtweet While I'm not disagreeing with you, I do still feel some sympathy for the original redditor that started all this. I've seen some projects target non-technical users and host on GitHub, and people who don't know what a compiler is need to download one just to install an addon or something. That's the really terrible UX in all of this. There may not be a better way unfortunately.