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:

• 
  Y. Fernandez 💻 (@la_eternaut) reported 1 minute ago

  @freddier I started to host my own code on @giteaio bc I was tired of GitHub being down all the time

• 
  viktorg (@viktorg475) reported 2 minutes ago

  @iamdavidhill @opencode You have over 500 pages of open issues on GitHub.

• 
  Ming (@tslaming) reported 3 minutes ago

  @Squirrel1980021 That is usually the biggest catch with custom solutions, as proprietary protocols often fragment the industry and lock people in. However, the great news here is that Tesla actually open-sourced it to prevent exactly that. They released the entire specification as TTPoE on GitHub during HotChips 2024 and even joined the Ultra Ethernet Consortium. So instead of keeping it locked down as a proprietary secret, they are actively working to make it an open standard that the entire high-performance computing ecosystem can use and build upon.

• 
  Chip Haze (@ChipHaze) reported 3 minutes ago

  @zekramu Are they going to shut down GitHub? Discord? What about local AI?

• 
  Ibrahim Mokdad (@ibmokdad) reported 6 minutes ago

  Your GitHub repo is already a roadmap inbox. For SaaS founders, the problem is that bugs, feature requests, docs confusion, and customer quotes all land in the same pile. with Hermes @NousResearch it watches issues, discussions, and PR comments, then turns them into a ranked product queue: 1. fix CSV export 2. ship report_ready webhooks 3. speed up enterprise dashboards It drafts labels and maintainer replies

• 
  ALV!N (@alvinx0i) reported 7 minutes ago

  @shreyaatwt GitHub is a public platform. By uploading your code files, u are basically giving consent to all others to see it, giving permission to them or to use for their own purposes unless you have valid license. So what's the problem ?

• 
  DefiantAsUsual (@DefiantAsUsual) reported 8 minutes ago

  @furgotti @mega_strimp Ah yes, the companies with good data security. Like the massive corporations that get hacked and have leaks quite frequently in this day and age? Even Microsoft had major hacker issues a few days ago that affected GitHub and involved malware distribution.

• 
  Kevin Swiber (@kevinswiber) reported 9 minutes ago

  Are there issues using the PR model at massive scale? Absolutely, well-documented ones. It's one reason not everybody uses GitHub. Most projects should never have that problem. So, please, don't create that problem for yourself.

• 
  Doug Finke (@dfinke) reported 9 minutes ago

  The meta part? I was using Codex to build a JSON-RPC wrapper... for the Codex app server. Turtles all the way down. And it still found the GitHub issue before I knew I needed it.

• 
  subwxxf 🏴‍☠️ (@subwxxf) reported 9 minutes ago

  @ItakGol a bunch of nerds doing **** for free on GitHub because they're not working

• 
  jayesh (@0xjayeshyadav) reported 12 minutes ago

  Onchain indexes hold about $100 million combined today, while the TradFi index industry holds tens of trillions of dollars. That gap is the entire opportunity, which most people read backwards. They see $100M and conclude nobody wants an onchain index. But after spending the last year building index products, I see it differently: nobody has built one correctly yet, and the underlying assets were never ready. The first problem is that every onchain index today sets weights manually, through token-holder votes or governance plus an offchain supply feed. Inserting a committee or token vote between methodology and basket simply rebuilds a discretionary fund wearing an index label. Its performance decays with governance attention. The two multi-year category leaders are both down 80 to 98% from peak TVL, showing this was a design problem, not a demand problem. The second reason is subtler: the only assets available to index onchain were crypto. A market-cap basket of volatile tokens is a leveraged bet on two or three names unless real methodology is applied, which almost nobody did, leaving the product fragile and narrow. What I am building is the opposite of discretionary. Weights are computed entirely onchain from float-adjusted market cap, capped and redistributed using the same iterative rules S&P and Nasdaq have run for decades. They are fed by a supply oracle that treats circulating supply as a bounded, explicitly named trust assumption rather than an unguarded feed. There is no committee and no vote; the methodology itself is the protocol. I am betting on much more than crypto. The index is the most successful product structure in finance history and already holds tens of trillions offchain. It has been stuck onchain not because the structure fails, but because the only assets available were volatile tokens. That changes as tokenized treasuries, credit, and equities arrive onchain at scale, which is already underway. The wrapper that manages trillions in TradFi finally gets a native onchain home. An onchain index of tokenized RWAs can then do what its offchain cousin cannot: settle continuously, show every holding in real time, rebalance programmatically, and remain in self-custody. Broad index ETFs are already cheap, so the honest comparison is not against a Vanguard fund but against the stack of intermediaries wrapping every index product, and against crypto index funds that still charge 1.5 to 2.5% a year. A fully autonomous onchain index removes that entire layer, replacing the administrator, custodian, and licensing fee with code while swapping the market-maker spread for open solver competition. Because the methodology runs itself, the fee can be a fraction of what crypto index products charge today. I'm building the reference implementation, and the code is on GitHub 👇

• 
  Alex Ventures (@alex23ventures) reported 18 minutes ago

  An AFP TV crew filmed an 8 year old Chinese boy named Zhou Zhiheng for a feature on Asia's youngest coders. Round green glasses. Red shirt. He sat in front of a MacBook Air at a glass desk in a Shenzhen co-working space with iPhone XR posters behind him. The narrator said he started by programming games. The subtitle said he had 60,000 followers on a coding tutorial channel. The camera pushed in on his fingers on the keyboard. While the West runs panels on screen time for children, China sits an 8 year old in front of an unregistered code editor and films it for the international press. He was supposed to be the cute face of Asian tech literacy. He just left the file tree open. Pause at 1:34. Ignore the C++ on the screen. Ignore the if statement that the AFP narrator was reading aloud. Look at the left sidebar of the editor. The folder is named aspirin. The open file is jizhe.cpp. The folder tree below it: 1-7, 1-7b, 10-1, 10-1.2, 10-2, 10-4, 10-6, 10-8, 11-2. ColdMath. $94,318 profit. 5,612 entries. Joined September 2025. Bio: Edge Compounds. Jizhe is the mandarin word for journalist. The file the AFP crew was filming was named after them. The boy had the open scanf reading a score variable. He had not written it that morning. He had named the file the day the AFP request came in. The numbered folders were not coding lesson chapters. The numbering matched the Chinese journalism beat codes the press accreditation office issues to foreign correspondents. 1-7 is the technology beat. 10-1 is consumer electronics. 10-2 is mobile devices. 11-2 is venture capital. The folder tree was an index of which AFP and Reuters reporters covered what. The boy was not the developer. The boy was the camera trap. The agent on the MacBook Air was scraping which journalists requested filming permits from which Shenzhen co-working spaces three days before the segments aired. Every requested permit was a position on the company being filmed. The agent traded the gap between filming and broadcast. The crew filmed for forty minutes. The agent placed eleven positions during the shoot. Every position was on a company whose office the AFP team had visited that week. Comments turned into a detective board. Someone slowed the AFP clip to 0.25x. Someone else translated jizhe out of the filename. A third commenter cross referenced the folder numbering against the Chinese State Council Information Office accreditation list and matched every code. Six months ago a 14 year old in Shenzhen pushed an AI agent to GitHub. Judges said no real world application. 3,100 forks later. The boy's father had been one of them. He had installed the fork on his son's MacBook the week the AFP request landed in the family's WeChat. The 60,000 follower coding channel was not a coding channel. It was a feed of which co-working spaces hosted which crews. The followers were operators running the same fork from different cities. The iPhone XR posters behind him were not Apple Store decor. The shoot was inside a media briefing room rented by foreign correspondents to film exactly this kind of segment. The agent knew the room. The room was on the list. The AFP segment is at 2.1 million views. The freeze frame of the folder tree hit 4.6 million on the repost. The wallet is still compounding. The agent is still reading press accreditation requests. The unregistered editor is still open. The jizhe.cpp file is still on the screen. He was filmed as proof a child could code. The child was the lens. The agent did the filming.

• 
  Elijah 🌊 (@juiceboy_of_abj) reported 21 minutes ago

  @VencedorZest The last commit I didn’t…. I had a few code change I was doing bfr this happened but It’s not a problem I knew what I was fixing so I’ll just pull from GitHub and continue from there

• 
  Upwind Security MDR (@UpwindMDR) reported 23 minutes ago

  🚨Critical - Apache CXF JNDI Injection in JMSConfigFactory (CVE-2026-50632) This is yet another incomplete-fix follow-up in the Apache CXF JMS RCE saga (after CVE-2025-48913 and CVE-2026-44417). If an application lets untrusted users configure JMS settings for CXF, an attacker can supply a malicious JNDI lookup URL through JMSConfigFactory and trigger remote code execution. The risk only applies where JMS configuration is exposed to untrusted input, but where it is, the impact is full code execution on the server. Note GitHub rates this CVSS 9.8 while Apache's own advisory rates it moderate. 👉Upgrade to Apache CXF 4.2.2 or 4.1.7.

• 
  scyn (@scyntipede) reported 24 minutes ago

  @Ezeisanidiot @KibryHouse bejeweled twist doesnt really function if you get it from steam, too.. you gotta get some fix from github or whatever