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:

• 
  Лев Тигроедов🇵🇸🌈🗽➡️ (@ElmntTigroedium) reported 6 minutes ago

  @github you are pice of lasy, coward **** who hiding problems insted of fix them. Burn in hell!

• 
  dolphin278 (@dolphin278) reported 7 minutes ago

  Claude Cloud environments is a separate can of worms. Want to access full Github API for your own repos? No. Want to connect to your own IMAP server? No. FFS...

• 
  Noah Hein (@TheNoahHein) reported 7 minutes ago

  I opened a bunch of issues in OSS repos as part of a bounty program for an old job. You would comment in the issue and get assigned to it. The bounties were from 2-5k USD. So periodically I get random people replying to those GitHub issues trying to snipe people’s work it is hilarious. “I will do this bounty for $1k less and I already have the PR ready just assign it to me” I love the petty drama 😭😭😭

• 
  aventursne (@00aventurine) reported 11 minutes ago

  @jvasata03 @Jooornio i agree that code on github and such being used for ai is mostly ethical. my issue is that i cant find a good reason why art should be treated differently other than some vague "it feels icky". so i choose to not really say anything

• 
  DESABRE HATE ACCOUNT (gang ya film) (@tshikolopo) reported 12 minutes ago

  @NevTheStampede what version did you patch? cause both the one recommended by morphe and the last on crimera github page show errors for me

• 
  blackorbird (@blackorbird) reported 16 minutes ago

  WordPress released emergency security updates (WordPress 6.9.5 and WordPress 7.0.2) to address two related vulnerabilities that can be chained together to achieve unauthenticated Remote Code Execution (RCE). The combined issue is publicly known as “wp2shell”. These are core vulnerabilities (no plugins or themes required) affecting default WordPress installations. 1. CVE-2026-63030 – REST API Batch-Route Confusion (Critical) Official Description (from WordPress GitHub Security Advisory):
“WordPress versions 6.9 and higher are vulnerable to a REST API batch-route confusion weakness, which combined with an SQL injection issue leads to Remote Code Execution.” WordPress 6.9.0 – 6.9.4 WordPress 7.0.0 – 7.0.1 Patched in: 6.9.5 and 7.0.2 2. CVE-2026-60137 – Facilitated SQL Injection in `author__not_in` Parameter (High) Official Description (from WordPress GitHub Advisory + CVE record):
“WordPress versions 6.8 and higher are vulnerable to an SQL injection issue in the author__not_in parameter of WP_Query. In WordPress versions 6.9 and higher, this combined with a REST API batch-route confusion issue leads to Remote Code Execution.” More Technical Context (from CVE./org): “WordPress 6.8.x before 6.8.6, 6.9.x before 6.9.5, and 7.0.x before 7.0.2 does not properly sanitise the author__not_in parameter of WP_Query, which could allow SQL Injection when a plugin or theme passes untrusted input to the parameter.” Key Details: The author__not_in parameter in WP_Query (used for querying posts by excluding certain authors) was not properly sanitized against malicious input. This allows SQL Injection (CWE-89) when untrusted data is passed to it. On its own, this is a facilitated SQL Injection (requires some form of input from a plugin/theme or specific context). It was rated Moderate in the official advisory, though some sources list it as High (CVSS 7.5) due to its potential impact. How the Two Vulnerabilities Combine (“wp2shell” Chain) The real danger comes from chaining both issues: 1The REST API batch-route confusion (CVE-2026-63030) allows an attacker to send specially crafted batch requests that confuse the routing logic. 2This confusion enables the SQL Injection in author__not_in (CVE-2026-60137) to be exploited without authentication. 3The successful SQL Injection can be leveraged to achieve arbitrary code execution on the server. Result: A completely unauthenticated attacker can execute arbitrary code on the WordPress site with no user interaction, no valid login, and no plugins required.

• 
  Roy Canani (@CananiRoy) reported 17 minutes ago

  @github Use your own runner, github is usually down

• 
  Evan Robertson (@evanbrobertson) reported 26 minutes ago

  Having 2 agents go back in forth in @github issues both using my account and it looks like I have schizophrenia

• 
  Roposh (@Roposh82) reported 28 minutes ago

  𝗜𝗳 𝘆𝗼𝘂'𝗿𝗲 𝘀𝘁𝗶𝗹𝗹 𝗵𝗲𝗿𝗲 𝗶𝗻 𝘁𝗵𝗶𝘀 𝗯𝗲𝗮𝗿 𝗺𝗮𝗿𝗸𝗲𝘁... 𝘆𝗼𝘂'𝘃𝗲 𝗮𝗹𝗿𝗲𝗮𝗱𝘆 𝘄𝗼𝗻. Not because you've made money... But because you refused to quit. Most people won't experience the next bull run. Not because it won't happen... But because they gave up before it arrived. They sold. They lost hope. They called crypto a scam. They walked away. Almost every friend I know has either left the market or spends every day complaining that their portfolio is down 90%. 𝗜'𝗺 𝘁𝗵𝗲 𝗰𝗼𝗺𝗽𝗹𝗲𝘁𝗲 𝗼𝗽𝗽𝗼𝘀𝗶𝘁𝗲. I've never felt more prepared. I've never had more conviction. I've never been more excited for what's coming. The next 𝗼𝗻𝗲 𝘁𝗼 𝘁𝘄𝗼 𝘆𝗲𝗮𝗿𝘀 won't just be another cycle. For some of us... It will be the moment that changes our lives forever. People will celebrate the gains. They'll never see the price we paid to earn them. 𝗧𝗵𝗲 𝟯𝗮𝗺 𝗻𝗶𝗴𝗵𝘁𝘀. The endless research. The whitepapers. The GitHub commits. The charts. The countless posts that nobody cared about. The doubt. The ridicule. The feeling of believing when almost nobody else did. My highest convictions are 𝗤𝗨𝗕𝗜𝗖, 𝗧𝗔𝗢, and 𝗞𝗔𝗦. Maybe I'll be wrong. But I'd rather fail following my convictions than spend the rest of my life wondering "what if?" 𝗧𝗵𝗶𝘀 𝗶𝘀𝗻'𝘁 𝗷𝘂𝘀𝘁 𝗮𝗯𝗼𝘂𝘁 𝗺𝗼𝗻𝗲𝘆. It's about proving that patience has value. That conviction matters. That staying when everyone else leaves is sometimes the only difference between an ordinary life and an extraordinary one. One day they'll ask... "𝗛𝗼𝘄 𝗱𝗶𝗱 𝘆𝗼𝘂 𝗸𝗻𝗼𝘄?" And we'll smile. Because we didn't. 𝗪𝗲 𝗷𝘂𝘀𝘁 𝗵𝗮𝗱 𝘁𝗵𝗲 𝗰𝗼𝘂𝗿𝗮𝗴𝗲 𝘁𝗼 𝘀𝘁𝗮𝘆. $QUBIC $TAO $KAS

• 
  Traveler (@Traveler2000AD) reported 28 minutes ago

  @ChrisCroy Funny thing is, almost all artists have copied, even "stealed", each others styles for cencuries. And if I am not wrong they still teach at modern art schools to copy great masters works to learn ("What? You copied Mona Lisa??? Why you ***** little thief...") As for coders, we all copied each others code for decades. Old ones started "stealing" by reading code examples from books & magazines ("What? You copied that DOS example program from Peter Norton book? Why you ***** little thief ..."), then discs, BBS archives, FTP archives, forums & StackOverflow & now latest fad is *** repos & youtube videos. Bottom line: people have copied each other for long time. That's not an issue. Never was. The only real issue is where does line go between copying & stealing. It's all in the details. If I put code to github with public domain license it means I don't give one single **** if somebody "steals" it. If I use MIT style license then go ahead, use it in your commercial product as long as you mention somewhere that it uses my code. And if I use AGPL, GPLv2,GPLv3 I am giving you a message that use it in anyway you like but if integrate it into your own codebase, you must then make your codebase public & accessible too. Only exception is LGPL that mostly libraries use & even then only if you don't statically link it into your product. Pro tip: If you are worried that somebody steals (again, details dammit!) your art or code, don't put it to Internet in the first place.

• 
  The Ramen Don (@RealRiddimHours) reported 35 minutes ago

  @GregoryGregman @rocksoverrocks @actualinc I guess that's true. I didn't really know what github did 9 months ago but through trial and error with ai assistance I'm able to make stuff now. Self teaching through AI has been doing wonders for me since 2023, its nuts

• 
  Leonardo Trapani (@leo_trapani) reported 36 minutes ago

  A state machine that manages agents in effect, with state layer github issues...

• 
  Harley Lewis Foote (@harleyfoote_) reported 36 minutes ago

  @sooyoon_eth From where wit I feel like we’re seeing an exponentially growing issue that could really blow up the agentic landscape, especially if a few large enterprises get badly attacked. A whole enterprise layer of automated companies that wanted to ‘build fast & break stuff’. Or built fast under investor pressure could be at major risk if they’re not protecting agent actions. Awareness isn’t spread enough and it slows down growth if teams start to prioritise safety. Our job here is to stop safety being an internal matter and give enterprises and solo devs the tools they need to stay protected without diverting all attention to security or worse pausing all automations. Opportunity is huge here. Few teams doing this to a standard that is 1. Trust worthy 2. Honest 3. Transparent. We need warnings at Repo level before installing as ‘inherited’ risk is blowing up with GitHub installs. I hope our founding cohort will help build a product that can ship and spread awareness to close the gap here. Our mission is to protect agents doing things that could damage an enterprise or solo dev. Our product works on our repo/its fixed real attack surfaces. Now we scale it out to others. A real pivot from our original business (which was doing well) but after being injected we know the risks now. We can’t turn away from it.

• 
  Ayhan Cicek (@CicekAyhan) reported 37 minutes ago

  @SatoshiGokumoto @ivanfioravanti @marcozerbato Twofold: I use github as a kanban board for a backlog and other lanes. Secondly I have a complete log of what I am doing and why. Never had an issue with gh.

• 
  Sudo su (@sudoingX) reported 38 minutes ago

  now i'm running the harness fight i've wanted to run for a month. hermes agent vs openclaw, same model, same tasks, both pointed at a 3.9gb bonsai on a single 3090. lean vs bloated, head to head, and i post whatever happens. disclosure first, i contribute to hermes agent, so i'm not pretending i'm neutral. what i can do is make it a fair fight. upstream versions of both, same local endpoint, no fork tricks, and let the receipts talk. here's what's actually in each box. > hermes agent. a one-file agent loop, around 25 direct dependencies. it parses and repairs tool calls off many model families natively, which is the whole reason it reads what a local model actually emits. built for open weights from day one. #1 on openrouter by daily usage. > openclaw. thousands of typescript files, roughly double the dependencies. for years it leaned on the server to parse tool calls and only shipped its own repair recently, for a single format. way more github stars than hermes. built for the big api models, and it shows. now let me tell you the honest part. i uninstalled openclaw months ago. my experience was that it was built for someone else's models, it choked on local, and the bloat made it slow just to start. but that was months ago and these things move fast. maybe they fixed the local story. maybe the parsers are there now. i'm not going to assume, i'm going to run it. that's the whole test. can either harness hold a tool-calling loop on a 3.9gb model without falling apart. one early tester says bonsai breaks on iteration, another says it tops agentic benchmarks. that split might not be the model at all. it might be the harness. this is what finds out. results coming. i'm not calling it early.