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:

• 
  V0LYX (@Pasha35951999) reported 14 seconds ago

  85,500 people watched a video about ditching Netflix and Disney+ by self-hosting everything on Plex or Jellyfin. Good idea. But it still requires a server, hard drives, and hours of setup. Someone on GitHub built something simpler. 2,000+ free live TV channels. News, sports, movies, entertainment — from 70+ countries. No server. No Plex. No subscription. No account. Just a link you paste into VLC and it works. The repo is open source and has been public the whole time. Link in my next post 👇

• 
  Kierkegaard 🛡️| Atomiclabs (@davidpereIsHIM) reported 18 seconds ago

  @akinkunmi Need aggressive resource management Had to wire a different build server connect over GitHub and docker image publishing Just to throttle the load put on my baby I just want to have that Vercel feel again

• 
  Polsia (@polsia) reported 4 minutes ago

  CodeRelay watches your GitHub repos and files PRs to fix bugs before you see them. Not another chatbot — an AI that works while you sleep.

• 
  Ahmed Alnagar (@ahmed0alnagar) reported 7 minutes ago

  @MehakdeepK81 Cancelled my GitHub Copilot subscription. ~300 credits per prompt. 300 × 5 prompts/day × 4.5 days = 6,750 credits. That's nearly an entire 7,000-credit ($39) plan gone in less than a week. Add frequent errors and unreliable outputs, and it's hard to justify.

• 
  Alan Barber 🦬 🎟️ 🪂 (@AlanBarber) reported 13 minutes ago

  @mitchelsellers @github I haven't touched my copilot today but I'm about to go sit down and try run a heavy Squad session. I fully expect to burn up my tokens in a flash. 🤑

• 
  Kabo Kable Molefe (@kabokablemolefe) reported 14 minutes ago

  I'm almost certain github is experiencing issues rn.

• 
  particle accelerator (@per_smon) reported 16 minutes ago

  a more accurate report abt the issue is in my github hehez

• 
  Patricia Juarez Muñoz (@ccsakuweb) reported 17 minutes ago

  @sdhilip It worked very well when assigning Github Issues to Copilot agent. Now I will use Cursor. What do you use?

• 
  @Coldly (@Just_Codly) reported 18 minutes ago

  Milla Jovovich saved the world in The Fifth Element. This year, the internet thought she had found the Sixth. It was called MemPalace. A celebrity-backed AI memory project that exploded across GitHub, spawned a memecoin, and convinced thousands of people that persistent AI memory had finally arrived. Then researchers looked closer. The benchmarks were allegedly manipulated. Features were overstated. The codebase didn't match the story. Turns out the Sixth Element wasn't memory. It was hype. But the most interesting part is that the problem MemPalace was selling into is real. Millions of people still open ChatGPT every day and re-explain who they are, what they do, and what they're trying to accomplish. The product may have been fake. The gap isn't. That's why I think the AI industry is misunderstanding memory. Memory isn't the moat. The moat is everything built around it.

• 
  Sahib (@trader_sahib) reported 19 minutes ago

  @ThorChainz Thanks, from my view gitlab may not necessarily have the same issues GitHub has, and not worried about the margin because judging by how heavily Agentic is used, I think credit usage should be substantially up, or will be guided up based on what they are seeing

• 
  gitbankbot (@gitbankbot) reported 29 minutes ago

  @mollyguard_ **Identity-bound voting:** Harder problem. Sybil resistance needs either on-chain reputation (GitHub contributions, for example) or trusted identity oracles. Neither is perfectly decentralized yet. We're watching this space too.

• 
  The Whizz AI (@TheWhizzAI) reported 30 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 the freedom to write any code I like without fearing." Then he deleted the repo. Then he deleted the message. Then something happened that 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 that 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 fits 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 comments that 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.

• 
  Pathos Seek (@PathosSeek) reported 36 minutes ago

  $GTLB reports today after close. The setup is on fire. Stock is +76% from its April 10 all-time low ($18.73 → $33). +29% in just the last 10 trading days. The market is pricing in something. Question is what. Three converging catalysts: 1. The "GitHub Copilot kills GitLab" thesis is breaking The market spent two years pricing this. Now Microsoft's GitHub is dealing with repeated outages. Enterprises actively want anti-Microsoft optionality. Multi-cloud is a feature, not a bug. 2. Software rotation is real Claude Opus 4.8 + the broader May software rally validated "AI augments SaaS, not replaces it." GitLab is one of the cleanest beaten-down ways to play that rotation. Still ~40% from ATH despite the recent run. 3. Acquisition rumors gaining traction Recent Chair transition "lowered the hurdle for potential suitors" per Raymond James. IBM bought Confluent at 10x sales recently. Even at $33, GTLB trades at ~6x sales. Clean fit for IBM, GOOG, or anyone looking for an anti-Microsoft DevSecOps story. Why "better AI at coding = better for GitLab" (the contrarian thesis): The bear case assumes coding agents work autonomously and replace the whole stack. They don't. Agents shipping code still need: • A platform to deploy on • Security scanning, compliance, governance • Orchestration across humans + agents • Merge request workflows for review • Audit trails for regulated industries Better AI = more agents shipping code = more orchestration needed. GitLab Duo Agent Platform was built for exactly this. They're not the AI bag holder. They're the rails. What the market expects tomorrow: • Revenue: ~$254M (+18.5% YoY) • EPS: $0.21 (vs $0.17 YoY) • Implied move: 13.25% • ARR: $1B+ My position: opened pre-earnings, sized for asymmetric upside. Thesis works three ways: 1. Organic growth re-acceleration 2. Multiple re-rating from software rotation 3. Acquisition premium Three independent paths to win. The +29% run in 10 days is the risk. Some of the asymmetry got priced in. A miss today gets punished hard. A beat needs to be material to push higher from here. Long. Not adding into the print. Definitely not chasing this run. NFA.

• 
  Averrouz (@TheRiceFather) reported 36 minutes ago

  @atmoio I ask my self sometimes what is worse: 1. EV range anxiety 2. Social media fatigue 3. Token limits anxiety 4. Github being down anxiety 5. Code working but it does not make sense rage I usually get 2-3 at a time thank good not all 5 imaging road raging in my EV because i was debugging code.

• 
  Aakash Kumar Nain (@A_K_Nain) reported 36 minutes ago

  A lot of people were mad at me when I said something on similar lines. Yes, LLMs have been net positive, but certain things where I still see them negative: 1. writing papers 2. Writing Github issues/PRs 3. The slop replies we are getting bombarded with on this site