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:

• 
  Yash Solanki (@YashSolanki_) reported 4 minutes ago

  @jeal0uspengu1n @mehulmpt makes sense, but still i don't think it's gonna be super easy as people are just used to github, the issue is the downtime not the product itself, and considering that if it does resolves soon there is no point in going anywhere for anyone.

• 
  Hope (@emerginghope_) reported 4 minutes ago

  One of the biggest problems with the synced-memory idea going around is that two agents can remember the same thing and still leave you with two versions of the company. The local Markdown vault is good. Seriously, set one up. A folder your AI tools can read is better than rebuilding your goals, preferences, and business context inside every chat window. But the first ugly failure shows up when the folder becomes work state. Claude updates the launch plan. Codex is still acting on yesterday's decision. The code changed from JWT to sessions, but the architecture note did not. Both agents have memory. Both can cite a file. One of them is about to be very productively wrong. This is the layer I built OrgX for. Not a bigger pile of context. A shared record of which initiative is active, which task belongs to whom, which decision replaced the old one + why, what needs approval, what artifact came back, and whether anybody accepted it. The setup is a few minutes: Run npx @useorgx/wizard@latest setup. It wires the supported local clients into the hosted OrgX MCP. Run doctor to check the connection. Add the OrgX skills from GitHub so the agent knows how work should enter and leave the system. Use a client plugin where there is one. Now Claude can research against the current initiative. Codex can implement against the same decision. A person can answer the consequential blocker without stopping every unrelated lane. The next agent can explicitly bootstrap into the work and see the task, decision, artifact, owner, and next action instead of asking the previous agent to write it a little autobiography. The clients are not magically identical. The public Claude Code plugin is deliberately narrow. Codex carries a deeper workflow. OpenCode is alpha. Fresh cross-client recovery is measured beta. I would rather say that than turn 'shared memory' into the new 'fully autonomous.' A local vault helps the agent remember you. OrgX is for the moment the agents start remembering different companies.

• 
  Groktopus (@groktopus) reported 6 minutes ago

  @jdegoes No, that's not true at all. GitHub has had scaling problems for more than 10 years now. It's only been exacerbated by the use of AI coding by its users, but this problem was always there. Bad architecture loses every time.

• 
  Joe (@jlchnc) reported 6 minutes ago

  i haven't checked but i bet github is down rn

• 
  Haniel Ulises (@Haniel_Ulises) reported 11 minutes ago

  i mean github certainly has had problems even before vibecoding but a lot of other services have been having tons of issues lately. my google home was down for a few hours, one would expect more from this technology as how it is being marketed

• 
  gh05t5h311 (@0DG_gh05t5h311) reported 11 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

• 
  Pradhan (@bruhdhan) reported 11 minutes ago

  it took a github outage to finally get the website version

• 
  Phil | Rentier Digital Automation (@rentierdigital) reported 13 minutes ago

  security theater that makes your site slower, not safer. so i stopped patching wordpress entirely 91% of wordpress vulnerabilities live in plugins, not core. you can run a perfectly patched install and still get owned through a contact form widget you forgot existed in 2022. the median window between disclosure and mass exploitation is 5 hours. by the time you read the changelog email, the scanners already hit your login page twice so i rebuilt my personal sites as plain html using claude code. no plugins. no admin panel. no cms at all the results: 2x faster load times, zero hosting costs (github pages), and exactly zero patches to chase. the translation layer between human and markup isn't the bottleneck anymore when an ai can write and maintain the markup directly from what you describe static sites under 10 pages don't have the mechanic problem i warned about in june. there's no backend to misunderstand, no dependency tree to untangle. it's html and css. the risk needs moving parts to break i build and ship daily. Claude Code, Codex, whatever ships fastest. SaaS, tools, automations. ⭐ if AI can build it, i've probably broken it first. what works → link in bio

• 
  Prerna khanna (@prernakhannna) reported 14 minutes ago

  First GitHub goes down. Then claude decides to join the party. At this point, I’m starting to think the universe is testing whether we actually know how to code without AI. 💀 #Claudedown #AI

• 
  Douglas Camata (@douglascamata) reported 14 minutes ago

  Great that there is already an RCA shared. From what I see, the root cause was a bad behavior in retries in Copilot after a VS Code update and it snowballed from there, right? Curious question: why the plans do not include a reduction of the blast radius so that Copilot messing up with traffic doesn’t bring all of GitHub down?

• 
  Joseph (@mjmawa) reported 16 minutes ago

  @jdegoes If Github is going down, we pretty much know where we are headed.

• 
  Abdul Rafay (@abdul_rafay99) reported 26 minutes ago

  @BradlyCarp12623 @aurorascharff Yeah, the memory issue is still there. With 50 sub-agents running, keeping the dev server up and running E2E tests on 16 GB of RAM just isn’t possible for me. Even with one dev server, running E2E tests locally or via GitHub Actions can get expensive.

• 
  Ashutosh Bhandari (@withashutos) reported 27 minutes ago

  GitHub had its seventh status page incident in fifteen days yesterday. Six hours and forty-two minutes of degraded pull requests, API and enterprise SSO. Same morning, Cursor shipped its own *** forge. Nobody in hiring has noticed yet. But every reviewer who says "just send me your GitHub" is leaning on one link that was down all Monday, and may not hold the whole picture by next year.

• 
  Akash Parashar (@itsakaashhh) reported 33 minutes ago

  @anur7ag @pierrecomputer people were ready for GitHub to go down or something 😭

• 
  Sonic-Iso (@Sonic_Iso) reported 36 minutes ago

  @derion_rei28275 @LKeszek20997 hold on there is a small bug let me fix it. it all works fine locally its just github issues but i can fix it