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:

• 
  Nicolas Finet (@nifinet) reported 3 minutes ago

  The list of things your AI must never write matters more than your prompt. Most people put all their effort into the instructions. Write in this tone, mention this benefit, keep it under 100 words. Then the thing ships "Hi {{firstName}}, just circling back" and you wonder what happened. In the outbound engine I put on GitHub, every play carries two blocks. What the message must do, and what it must never do. The never block is short and boring: No "Hi {{firstName}}" No fake urgency, no "circling back" No em dashes No buzzwords Four lines, and they do more for the output than anything else in the file. A model will follow your tone instructions perfectly and still hand you the exact email your buyers delete on sight, because that email technically matches the brief. Your instructions describe the email you're hoping for. The never list is where you write down the email you keep getting instead. Btw, this "never list" doesn't go into the prompt itself either. It sits in a config file, one block per play, and the drafting step passes whichever block matches into the model as guardrails. Which is why it keeps growing. "Quick question", "hope this finds you well", "just wanted to reach out". None of them wrong exactly, all of them a sign nobody looked. Everything that carries judgment or voice ended up in plain files like that one. None of it buried in code.

• 
  Shiny (@shinyflvres) reported 3 minutes ago

  @Lastochka1996 Could you let me know if that happened again? And if so open a issue report on github

• 
  virgo.fyi (@virgofyi) reported 4 minutes ago

  GitHub Copilot just got persistent memory across agent sessions. That solves an obvious problem: stop teaching the same agent the same project context over and over. But engineering teams have a bigger one. What one agent learns should be discoverable by the whole team, across Copilot, Claude, Cursor, Codex, and whatever comes next. Agent memory is useful. Shared engineering memory is where this is heading.

• 
  Jeffrey Emanuel (@doodlestein) reported 5 minutes ago

  @ericzakariasson The zoom one just instant blocks you as a bot. I couldn’t get the GitHub or Vercel ones to work either, then I gave up. It’s also confusing because I have a Super Grok account via X and also a Cursor account via my Google login. It’s just a confusing mess.

• 
  Raihan (@m_adi_raihan) reported 6 minutes ago

  Hey @github , what happened to you? Why were you down for so long!?

• 
  samagra14 (@samagra_sharma) reported 9 minutes ago

  @cnikitopoulos94 It's not just about email. It is also about getting a GitHub account and other similar things. If you see in the video, the agent was able to get an email, but it was unable to sign in to GitHub because GitHub actively blocks bots.

• 
  Shane OHanlon (@sohanlondev) reported 17 minutes ago

  Dear @github get your **** together please. Issues again today but of course your status page gets updated an hour later.

• 
  Eyal Cohen (@eyalccohen) reported 19 minutes ago

  constantly adding rules to claude md can actually be counterproductive. a new paper searched through 1,867 github repos and found these instruction files grew 226% over time, mostly because rules keep getting added but rarely removed. their fix was simple: save why each rule exists. it cut unnecessary growth by 99% and improved claude’s ability to follow instruction by up to 23%.

• 
  nyk (@nykdotdev) reported 19 minutes ago

  ONE CODING AGENT IS NOT AN ENGINEERING SYSTEM. "This is not an AI that writes code. This is an AI that completes engineering tasks." The article's core thesis is simple. Connect specialized agents so they can turn an issue into a tested pull request without repeated copying and pasting. Think of the workflow as a relay inside a code repository. Each agent owns one stage and passes a clean state to the next. The engineer judges the final code change. OpenHands has 75,000 GitHub stars, but popularity is not the test. The workflow is. 1. Give the planning agent one concrete issue. 2. Let the coding agent read the repository and its dependencies. 3. Require the testing agent to run the tests and report any failures. 4. Send the resulting code change to a security reviewer. 5. Proceed only when the implementation, tests, review, commit, and pull request agree. Skip a handoff, and errors compound through every agent that follows.

• 
  ndy_gratitude (@wendylocas757) reported 23 minutes ago

  quantum risk for crypto wallets has a countdown, not an opinion. @quipnetwork tracks it on a public doom clock and ships the cryptographic fix. open testnet, public github, 13k+ users already verifying.

• 
  Ming "Tommy" Tang (@tangming2005) reported 23 minutes ago

  3/ The README lies. You run the install command, dependencies fail. You chase error messages across GitHub issues from 2017.

• 
  Tasogare kaitsuki🦊🎭 🥼 (@tasokait) reported 24 minutes ago

  there is nothing else to be added to spout2pw, except pre-multiplied alpha on obs-pwvideo so from now on, I will just bug fix and maintain for different proton versions 11 onward, until at some point I just add pre-multiplied alpha on obs-pwvideo. I need a little break from github development to get to my IRL stuff.

• 
  CodeGlitch (@codeglitch) reported 24 minutes ago

  Vercel built a software factory that now authors part of the AI SDK repository's merged pull requests. The useful pattern is not “add more agents.” It is one reviewable job per agent, evidence between steps, and deeper human review as risk rises. 𝗧𝗼𝗱𝗮𝘆'𝘀 𝗹𝗲𝘀𝘀𝗼𝗻 (𝗳𝘂𝗹𝗹 𝗯𝗿𝗲𝗮𝗸𝗱𝗼𝘄𝗻 𝗶𝗻𝘀𝗶𝗱𝗲) How to split one issue into triage, reproduction, implementation, verification, and review without letting one agent approve its own assumptions. 𝗔𝗹𝘀𝗼 𝗶𝗻 𝘁𝗼𝗱𝗮𝘆'𝘀 𝗯𝗿𝗶𝗲𝗳 - DeepSeek V4 Pro 0813 - Ollama in GitHub Copilot for JetBrains - Vercel's database migration behind every build Inside AI Coding & Agents HQ. A new one every day. Join link below.

• 
  Santos (@NotSantos7) reported 26 minutes ago

  @jordan_milner @KyroGeorge Nah I already made a pull request on github, it had to do with the origin login screen timing out after 120 seconds, changed it to 300 and I'm in now.

• 
  iam_bpn (@iam_bpn) reported 29 minutes ago

  @theo Well the problem isnt the *** rather its the *** providers like GitHub.