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:

• 
  Namma Chennai (@NammaChennai_) reported 5 minutes ago

  @Sir_Kuruvi @trilokchronicle @AdiSpeaX GitHub link not working?

• 
  A. Loner (@peterlony) reported 9 minutes ago

  @MatthewBerman No, it's easy... I develop about 20k to 30k lines of code a day in a million-plus-line monorepo. On a $200 plan and if I'm not careful I use it all in 3 to 4 days. I have a computer running almost 24/7 with goals all the time. I had to reduce to medium (gpt-5.5). If you use a lot of sub-agents and do a lot of reviews, then it's easy. I have a particular review process after coding to catch bugs and problems. It's very expensive. PLUS automated github reviews. Github reviews is what kills tokens usage.

• 
  Waldek Mastykarz (@waldekm) reported 10 minutes ago

  A new model drops with lower per-token pricing and better benchmarks. You switch. A week later someone asks why the agent is burning 12x more tokens on the same task while producing worse output. We ran 150 agent tasks across 15 scenarios on Sonnet 4.6 and Sonnet 5 using GitHub Copilot in VS Code. Sonnet 5 has 33% lower per-token pricing across every category. The assumption: newer and cheaper means better. On architecture tasks, Sonnet 5 used 12x more tokens at the median. One run consumed 47x the typical volume. A 33% per-token discount doesn't survive a 12x increase in consumption. Quality didn't improve either. On the 9 architecture scenarios where both models produced usable output, the older model scored 90% on our Idiomatic dimension versus 78% for the newer one. More tokens, worse quality on the majority of scenarios. On code upgrade tasks, the picture reversed. Sonnet 4.6 passed the Select gate 60% of the time. Sonnet 5 passed 100%. When the task requires following a specific instruction over what the model finds in context, the newer model was more reliable. But both models hit the same quality ceiling on configuration correctness: 0%. Neither could complete structural migrations that aren't documented in one place. Spending more on a newer model doesn't fix a content gap. A model upgrade is a hypothesis. You won't know which side your workload falls on until you measure it.

• 
  NZΛKI (@NzakiCodes) reported 10 minutes ago

  @pxxl_space @honour_can_code @whakee_ I can't login with GitHub

• 
  Kevin Murphy (@midimurph) reported 17 minutes ago

  i build applied AI in the open, usually on the raw Anthropic SDK and the Vercel AI SDK, coordinating the agents by hand. this time i put LangGraph through the same bar, and built a real thing with it: an agent that triages github issues.

• 
  Harsh Verdhan Singh (@harshsagee) reported 19 minutes ago

  People solve leetcode problems daily and posts that they are coding for a week, month or year. Bro show GitHub, that's where real code is written not in the leetcode.

• 
  M Saqlain (@imsaqlain22) reported 20 minutes ago

  @Savita091 Read error -> stack overflow/github issues (Google) -> read how to implement it -> Ask AI

• 
  hve 🍁 (@heyhve_) reported 21 minutes ago

  @CantelopePeel @github Retesting every branch in a merge group is pure wasted compute. We can't fix GitHub's queues, but we make each run cheap and fast.

• 
  AcceptÐoge (@DogeAccept) reported 21 minutes ago

  @MoonlitMonkey69 @probablyluda 1. is an L2 bridge, settles before L1 (dogeos is not fully l2, "app layer, l2ish) 2. is L1 integration "bridging directly to Dogecoin" to settle. ZK integration on L1 could add potential vulnerabilities. L2 wouldn't be "on doge," wouldn't be decentralized at first and you must trust. This post is saying that people have an issue with l1 integration but also have and issue with a permissioned, custodial bridge. I say that people are or should be well aware of what theyre using.. its creators should have no problem being transparent to anyone interested in using it. It is a choice to use this bridge and the tech should be able to be questioned openly so people know exactly what to expect especially when they are trusting. L1 integration should more so be able to be discussed openly beyond a proposal in discussions on github that has been there for a year especially when the people "building" it are currently clearly talking about different tech publicly than what that proposal mentions. We vote with node updates, yes, but as an open community of countless people.. not everyone can or has the ability to run a node. The obvious is that Dogecoin is permissionless when it comes to introducing code to core. That is why we have maintainers to screen and our network itself is the consensus mechanism. However, our community is unique and we have no leaders or voices beyond the community itself. If we want to discuss things like this, we just do. Its messy but its always been open dialog that educates, innovates, and somewhat of a social concensus when it comes to how the community as a whole would or would not like to see a direct of a coin that all of us support goes. Our voice matters too. I have done my best to ask about very specific topics to the right people even when I cant ask the person writing the code directly. I have tried that too, in good-faith, even when I dont agree with them. I have been met with nothing but assumptions, character assassination, empty promises of good-faith conversations or responses and ultimately being blocked by all of them, always right after false accusations. If we cant talk to the builders, if they are not transparent, if we cant discuss with each other, or question the things being shilled to us when we have no leaders.. Can we even call ourselves a community?

• 
  Deependra Solanky (@solanky) reported 23 minutes ago

  @reach_vb On Windows with WSL, none of the computer_use, browser_use, or chrome_use capabilities work. There are GitHub issues tracking these problems that have been open for quite a while, but I haven’t seen much progress. WSL is a major development environment for Windows, so better support would make a big difference.

• 
  Brenden Bishop (@bbishdotdev) reported 26 minutes ago

  @mattpocockuk I have to say wayfinder moving the content to GitHub issues instead of living in the codebase via context files and ADR is a huge advantage over grill-with-docs

• 
  Sprytix (@Sprytixl) reported 28 minutes ago

  ANTHROPIC LEAD ENGINEER BUILT AN AI AGENT THAT CLOSES 97% OF GITHUB PULL REQUESTS - AND FIRED 2,000 EMPLOYEES time to merge dropped by 70% - code quality higher and more consistent engineers freed for harder problems pull request opens - the agent analyzes the diff, forms a plan, edits files, runs the full test suite and performs a security scan if something is wrong it fixes it, reruns validation and repeats until everything passes - only then does it merge 97% of pull requests across dozens of repositories and thousands of contributors - handled autonomously engineers now only see the 3% the agent couldn't solve alone

• 
  BullBear.News (@bullbear_info) reported 30 minutes ago

  @github Unless you're announcing an AI that actually fixes my broken CI pipeline, I'll just watch the stream. 🤷

• 
  Jason A Yakubu (@jason_yakubu) reported 32 minutes ago

  Day 4 — Pre-Demo Hackathon build update: The goal was never another API testing tool. The goal is reducing the time between: Issue Found → Root Cause → Fix Working toward a demo where a failed API test results in an auto-generated GitHub PR Demo soon 🚀 #buildinpublic

• 
  Shrikant Joshi (@shrikant@noc.social) (@shrikant) reported 32 minutes ago

  @Techjunkie_Aman CAVEAT EMPTOR! Hasn't been updated in over a year. Developer team is mostly working on Zima OS. Issues piling up on GitHub. Currently held together by wisps of hope and (LOTS of) duct tape. CasaOS is superb for beginners but will likely die out due to lack of attention.