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:

• 
  Vijay (@imotiusa) reported 22 seconds ago

  The problem: When an alert fires at 2am, the error message tells you WHAT broke. It tells you nothing about WHY. So your on-call engineer spends 20 minutes manually searching Jira, Slack, and GitHub before they even start fixing anything. That's the gap I wanted to close.

• 
  Emanuele Di Pietro (@emanueledpt) reported 6 minutes ago

  @AllenCao1997 @xingbugengming nothing atm there is only github issues haha

• 
  Petra Donka (@petradonka) reported 6 minutes ago

  @Qodesmith @warpdotdev Thanks for the report! That should just work — would you mind opening a GitHub issue so we can track a fix for it? We've squashed a bunch of bugs around the filetree, this may be another one that needs to be fixed.

• 
  am.will (@LLMJunky) reported 8 minutes ago

  @emanueledpt no, thats the normal github screen lol. its a joke because its also, frequently down

• 
  Cocoanetics  (@Cocoanetics) reported 13 minutes ago

  Now porting gh @github CLI to beautiful Swift. This way I can include the most useful commands in SwiftBash or even talk to GitHub from any other app I want to Build a sort of command Center app on Mac and iOS that let’s me delegate agents to work on issues

• 
  mnrcst (@mnrcst) reported 14 minutes ago

  @sudobunni @github I have tests that fail randomly due to ci/cd env issues that run some playwrite tests. Blocks me for dozens of minutes on some days. Makes me grumpy.

• 
  webadderall (@webadderall) reported 16 minutes ago

  @edytwithme If possible issues do go through Github though

• 
  Unbearabull󠀽󠀽 ♕ (@Unbearabull2) reported 18 minutes ago

  $Staccana (Solana Fork Staccana) is doing really well. The website for this token is a Github repository--the source code for this fork. It takes a lot of work to fork Level 1 infrastructure. Definitely not just a meme + hopium like almost every other Sol token. I trust this token won't rug, at least not because of the contract or code. This doesn't mean the poorly-performing alt coin market won't drive it down though. NFA Trustworthiness should be the starting point for all tokens again. More transparency should become mandatory on Solana because the whole blockchain needs a lot of improvement especially in the trust department.

• 
  Vijay (@imotiusa) reported 18 minutes ago

  3/11 The product is called OpsLens AI. It connects to your Jira, GitHub, Slack, Datadog,etc ingests everything and the moment a production error fires, it surfaces: What was deployed in the last hour. Related tickets and threads from your entire history. A full incident brief

• 
  Nexus Void Ai - Your Autonomous CISO (@NexusVoid_Ai) reported 22 minutes ago

  @authzed The GitHub incident is the one worth sitting with. Not a zero day. Just a single over-permissioned PAT wired into an MCP server, and one poisoned issue was enough to pull private repo contents into a public PR. The agent did exactly what it was configured to do. That's the uncomfortable part. Clean code, no exploit, fully exposed. The trust boundary between untrusted content and tool scope has to be explicitly designed or it doesn't exist.

• 
  DemonKingSwarn (@DemonKingSwarn) reported 24 minutes ago

  @s13k_ and that way github would sustain its users without actually going down, so no one will try to move away

• 
  Human Layer (@HumanLayerlabs) reported 25 minutes ago

  The fix is a score, not a checkbox. A wallet with 3 years of history, 200 GitHub commits, and real on-chain activity scores 82. A wallet created last week scores 12. Same rules. Completely different outcomes.

• 
  Maor Ai (@Maor_Elkarat) reported 27 minutes ago

  In 2015, the Chinese police visited a programmer's home. They told him to stop working on his code. They told him to delete it from GitHub. He posted one final message before he obeyed: "Two days ago the police came to me and wanted me to stop working on this. Today they asked me to delete all the code from GitHub. I have no choice but to obey. I hope one day I'll live in a country where I have freedom to write any code I like without fearing." Then he deleted the repo. Then he deleted the message. Then something happened the Chinese government did not plan for. Within hours, the code was mirrored to thousands of other GitHub accounts. Within days, it became the #1 trending repository on GitHub globally. Within weeks, every Chinese developer who could compile code had a copy. The government tried to make it disappear. The act of trying made it permanent. The project is called Shadowsocks. The programmer's username was clowwindy. He built a tiny piece of software that let anyone in China bypass the Great Firewall and reach the open internet. No subscription. No company. No account. You set up a server somewhere outside China. You connect to it. Your traffic looks like normal encrypted web browsing, so the firewall cannot tell you are using it. Why this terrified the Chinese government in 2015: → It was open source. Anyone could compile it. → It was small. The whole protocol fit in a few hundred lines of code. → It looked like normal HTTPS traffic. The Great Firewall could not distinguish it. → It required no money. No accounts. No central server to seize. → It worked on every operating system. You cannot arrest a protocol. You can only arrest the person who wrote it. So they did. And the protocol kept spreading. shadowsocks-windows: 59,300+ stars. GPLv3. Still online 11 years later. The 2015 commits the Chinese government wanted deleted are still in the history. clowwindy was forced to walk away. The code never did. But DO NOT install it. The Great Firewall has feelings too. 100% Open Source. (Link in the comments) Must Follow For More updates.

• 
  Ofek Shaked (@VibeCoderOfek) reported 28 minutes ago

  Just watched an agent go from GitHub issue to merged PR in one pass. This isn’t ‘AI helps you code’ anymore this is the terminal becoming the new IDE. My backend workflows are about to look prehistoric.

• 
  yajnadevam (@yajnadevam) reported 29 minutes ago

  @RTanunapatah The grammar is machine verified using vidyut library. If you find errors, we can certainly raise an issue on their GitHub. Im not sure what “try to confuse” means regarding math.