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:

• 
  WealthRewired (@wealthrewired8) reported 2 minutes ago

  @LearnWithBishal 57,000 GitHub stars in 120 hours is the part that stands out to me. Not the AI assistant itself. When developers adopt something that fast, it usually means it's solving a real problem, not just riding a hype cycle. Running locally, no account, no subscription, no cloud dependency. That's a combination a lot of people have been asking for.

• 
  David Jennings (@ChilliDoor) reported 4 minutes ago

  @aap_twak @joshmanders The recent security issues with GitHub show that that's not really true anymore. You now need at least a basic level of caution

• 
  Alex (@realalexniebuhr) reported 4 minutes ago

  @pavitrabhalla I don’t think it’s right. Define task as GitHub issues have one sandbox/agent per issue.. let that sandbox/agent work for hours than PR & merge

• 
  maria (@maria_rcks) reported 5 minutes ago

  This is for keeping you distracted when github is down

• 
  Alvaro Lamadrid (@aglamadrid19) reported 6 minutes ago

  @ibuildthecloud what set me aside from it, its that i had opencode installed and regularly give it a try, but between some updates i guess its not showing my chat history. found some people reported that on their github, but honestly im not going to mess with sqlite or whatever specially if its not well documented the fix. Good bye opencode at least for now, al tried grok build cli whatever, i didnt like the tui and grok build (model) couldnt do something in many hours where gpt 5.5 max whatever got done in like 30 mins. also claude opus is super expensive i guess

• 
  Michael DePetrillo (@klassicd) reported 8 minutes ago

  @ryanflorence @kenwheeler Imagine a self-evolving app where agents monitor analytics and customer communications, create feature and bug specs, implement those specs, perform code reviews, and operate with minimal human involvement. OpenClaw was doing something similar with GitHub issues and reports.

• 
  Two Seven One Three (@TwoSevenOneT) reported 9 minutes ago

  New #redteam tool for blocking EDRs: EDRChoker Instead of fully blocking the EDR agents' connections to their server, we can throttle their bandwidth so they consistently time out when sending data, which is effectively the same as blocking but avoids triggering "block" or "drop" packet events #pentest #cybersecurity Github: TwoSevenOneT/EDRChoker

• 
  Jake Colling (@JacobColling) reported 9 minutes ago

  @dok2001 This is why we named our company Firstloop Software dev is concentric loops now. - Agent doing dev and verifying it's changes with static analysis and e2e playwright - Next layer is telemetry loops: does the system do what it's supposed to and bug reporting (feeding into github issues to spin up more agents) - Most important part of course is the market loop (does this matter to customers/clients)

• 
  Topu (@TopuWeb3) reported 11 minutes ago

  @ekinoks_26 @quipnetwork github stars help, but actual audits, issues closed, and releases matter more, tbh.

• 
  stepan (@cyntro_py) reported 18 minutes ago

  Spent some time over the weekend building a scraper to collect all existing dynamic workflows. The feature only appeared about a week ago, so there aren't that many in the wild yet - around 800. Based on GitHub activity, roughly 100 new ones are being published every day. Almost all of them are focused on software development, but the main advantage over skills is already obvious. Skills are an old concept at this point. They were hugely popular in February-March 2026, but it's June now, and the models have predictably absorbed most of the knowledge that any public skill on the internet could provide. In more than half of cases, public skills either provide no measurable benefit or actively make the outcome worse than simply asking an LLM to solve the problem. I ran a small eval to test this: comparing an agent equipped with coding skills against a plain LLM that was asked to come up with a plan and implement the solution. The results were far from favorable to skills. Workflows are different because they are codified, programmable systems that manage and orchestrate work. If the purpose of a skill was to tell an LLM how to perform a task, today's work is increasingly shifting toward building algorithms with validation, feedback loops and control mechanisms that orchestrate agents around a goal.

• 
  WarChud (@SheerC12972) reported 20 minutes ago

  @ArcanesValor @chamath Look at the github issues for DeepSWE They have massive issues that makes deepseek look 4x more expensive and fail benchmarks due to implementation bugs

• 
  Polycarp 🇰🇪 , PhD (@kidiwalogha) reported 21 minutes ago

  @itsalexzajac What happens when GitHub copilot takes over a project repository. From creating issues, commits, pull requests, reviews, resolving comments and merging.

• 
  yourclouddude (@yourclouddude) reported 21 minutes ago

  2026 PROJECT BUILDING CHALLENGE 🚀 1. Build 1 project every month 2. No tutorial copying 3. Push code to GitHub daily 4. Write a README for every project 5. Learn by building, not watching 6. Solve 1 real-world problem each week 7. Deploy at least 1 project/month 8. Share your progress publicly 9. Improve 1 old project every week 10. Finish projects before starting new ones By the end of 2026, you'll have a portfolio most people never build. Who's in? Mark your attendance 👇

• 
  296 (@twoninetysix) reported 28 minutes ago

  since when did github become a slow piece of ****

• 
  mo (@moboudra) reported 28 minutes ago

  @linzidongus can you submit a github issue with more details? i'd be happy to help fix this for you