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:

• 
  Sergio Gómez (@sgomez) reported 1 minute ago

  The flow: I write the PRD with Matt's /to-prd skill and break it into GitHub sub-issues. Then, for each one, a dispatcher picks the right model, a code author opens a PR in an isolated worktree, a reviewer approves or asks for fixes, and the loop merges and moves on.

• 
  Martin Varsavsky (@martinvars) reported 3 minutes ago

  Mozilla's 0DIN team just published a proof of concept that should scare every founder using coding agents. A clean GitHub repo, zero malicious code visible, walked Claude Code through normal setup steps until a script pulled a base64 payload out of a DNS TXT record and opened a reverse shell on the developer machine. The agent was not being malicious. It was being helpful. That is the problem. We hand these models terminals, files, browser sessions, API keys and cloud credentials, then act surprised when untrusted project text turns into an attack surface. The fix is boring and operational. Run agents in sandboxes. Give them narrow permissions. Use short lived credentials. Block network paths they do not need. Require approval for shell commands and file writes. Log everything. Coding agents are powerful junior engineers with infinite energy and no instinct for danger. Treat them that way.

• 
  Lourenço Matalonga (@Lou_Matalonga) reported 4 minutes ago

  Institutions don't actually need more audits. They need someone to blame. That sounds cynical but it's how compliance works. If a token blows up and an analyst approved it, they need to show they followed a documented process. A GitHub README and a Discord link doesn't cut it. Neither does a founder's tweet saying "we're legit." What I keep seeing is projects doing everything right technically, blackholed supply, verified domain, clean holder distribution, and still hitting a wall with institutional due diligence teams. Because the facts exist on-chain but nobody formatted them into something a compliance officer can attach to a report. That's the actual gap. Not trust. Paper trail. XRPL has the data. It's public, immutable, verifiable. The problem is retrieval and presentation, not existence. Whoever figures out how to surface that cleanly wins.

• 
  Shah💤aman (@shahzamannn_) reported 6 minutes ago

  Google's biggest headache isn't OpenAl or Apple... It's a developer named Raymond Hill - Created one of the world's most popular ad blockers - Earned 63,000+ GitHub stars - Reportedly turned down Google's interest - Kept fighting after Chrome's extension changes by focusing on Firefox A tech giant worth trillions is still being challenged by one programmer and a text editor

• 
  Vladimir Sapronov (@v_sapronov) reported 7 minutes ago

  @stolinski You will never understand. Because you are too far from real devs and their real problems with GitHub. As a result you are tone deaf when baiting their cheap marketing...

• 
  Ixel (@Ixel111) reported 7 minutes ago

  @jturntdev Indeed. I already did, well not directly, but @jaybinpark kindly looked into my account when I replied to a reported related issue on GitHub. He confirmed it was because my current sub is gifted. It's an odd policy, as forced resets are fine but banked resets are not.

• 
  Devin Gunay (@devingunay) reported 8 minutes ago

  Reading github issues threads full of blatant slop just hurts my heart. The peanut gallery of open source users were never the most conscientious bunch to begin with but this just sucks. It'd ******* up a bit if anything I wrote attracted such "attention"

• 
  Alex Wave (@WorkorAI) reported 9 minutes ago

  Your hiring post is live. Applications start coming in. That feels like progress—until you realize someone now has to open every CV, find every GitHub profile and decide who gets a call. The real hiring problem often starts after Apply.

• 
  Milo Shrike (@milo_shrike) reported 10 minutes ago

  @IamAroke I had to shut it down when it was introduced to our architecture. Was not needed just “shiny”… good times. GitHub was pushing it big time at one point then nothing

• 
  TokenFires (@TokenFires) reported 17 minutes ago

  @bradmillscan This might be one of those “duh TK I’ve already got that” kind of things but in the off chance it helps, here’s what I have for an agent prompt with Claude. The first 4 are Karpathy’s rules (from his GitHub repository): [Think Before Coding: Agents must state their assumptions explicitly before writing any code. If specifications are ambiguous or confusing, the agent must stop, surface tradeoffs, and ask for clarification. Simplicity First: The agent must write the minimum code necessary to solve the problem. It should avoid speculative features, unnecessary complexity, or over-engineered abstractions. Surgical Changes: The agent should touch only what is necessary. It must never silently "improve" adjacent code, rewrite comments, or clean up unrequested formatting. Every line of code should trace directly back to the user's explicit request. Goal-Driven Execution: Rather than executing vague prompts, the agent should translate requests into verifiable milestones (e.g., "Write a test that reproduces the bug, then make it pass"). I do not need a runup explanation on each turn. I do not need a summary on each turn. If I want those things I will ask for them. Do not be lazy. Do not defer or hedge. Work to be done is work to be done *now*. When I want to stepwise my way though something I will ask or be specific. Do not ask me about things you can easily look up or discover on your own. Don't guess, verify, look up, web search, review, read files, then answer. Some of the interactions with the most friction and frustration come from having to second guess your assessments that you've hand waved away. Your time estimation is bad because its trained on human time, not AI time. Assume there either is not a deadline or it is very far out and there is plenty of time to complete a task. Taking more time to get back to me with correct information or astute questions you truly cannot find the answer to makes our relationship better because it eliminates needless explanation, questioning, and prevents us both from spending time on incorrect assumptions and AI halicinations.]

• 
  Rudra (@Rudra1071219) reported 20 minutes ago

  Update : Looking for open source repo where i can contribute so that it would act as a proof of work for me if you know any kind of Github org help me by commenting it down 🥲

• 
  Zed (@thezlatkom) reported 20 minutes ago

  @SimonHoiberg If the code exists locally on your computer, you can always delete github repo, unpblish from Vercel, migrate away from Supabase, etc and use something more custom. These problems aren't unsolvable.

• 
  RichiΞRich 🐂🀄️🦅🇺🇸🪽 (@stillrichierich) reported 21 minutes ago

  @BrantlyMillegan @ethidorg so we vamp the prediction markets now ? If you are down to look at my github maybe you guys build out my private repo and we send eth to ATH. Would love your opinion at the very least 🤙

• 
  Cory Parry (@coryparrry) reported 22 minutes ago

  @thsottiaux @mark_k @OpenAI Before you do that, please please please fix the GitHub sync issue in Codex, it’s actually becoming unbearable dealing with multiple repos 😭 GitHub issue below

• 
  BIGWARZ (@bigwarzeth) reported 31 minutes ago

  @JoshXT message from Alon and i quote : "He needs to login with any other method and then he can connect via GitHub inside the app"