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:

• 
  Dmytro Virych (@dmytrovirych) reported 13 minutes ago

  I’ve been shipping code for 10+ years and imposter syndrome still won’t leave me alone. You’d think it chills out with time. Nah. It just levels up. Early days it whispers “you’re not ready yet.” A decade in it hits harder: “bro you’ve been faking it this whole time, they’re about to catch on.” Mobile apps, web stuff, janky systems with too many moving parts, solo products I actually shipped… none of it matters when the voice kicks in. Thinking about speaking at a conference? Lol who do you think you are, those are the real pros. Want to drop an opinion in a thread? Better stay quiet before someone realizes you don’t actually know ****. Here’s the thing I’ve learned: the voice isn’t tracking your real skill. It’s just screaming about the fake gap between what you know and what you think everyone else knows. That second number is 100% made up. Your messy behind-the-scenes vs their perfect highlight reel. All those “professionals” I’m scared of? Half of them are up at 2am staring at a random GitHub issue, quietly praying someone else already solved this exact bug. It never fully disappears. You just get better at shipping anyway while it’s still yapping. If you’ve got way more years than your confidence shows, reply with the number. Curious how many of us are still out here waiting to get “found out.” 🚀

• 
  Proof of Voice (PoV) (@Proof_Of_Voice) reported 15 minutes ago

  $XDB @XDBchain is a @StellarOrg-fork L1 for branded coins and Web3 payments. PoV by @0xNeodallas:“GitHub has been frozen since 2021.” ✅ Explorer, Laboratory, Atlas dev tools ✅ Gate, Bitget, KuCoin, MEXC listings 🔍 Down 99.99% from ATH 🔍 No audit or bug bounty

• 
  Blake (@devwithblake) reported 15 minutes ago

  The rate limit issues im having with @Zai_org while paying the full 20x is very interesting, disappointing and obviously annoying lol 1 session can’t finish out a GitHub public write up repo without 6 API rate limit errors totaling to 297k tokens out of the 1m 2 sessions earlier, 1 doing research the other trying to deploy this repo, both hitting rate limits. How do I fix this? Seems like rate limit adjustments are only by request? @Zai_org

• 
  Jose (@SolutionsCay) reported 17 minutes ago

  @petergyang /goal make me app does not work for me 😰 but /goal complete GitHub issues #90, #91, #92 works very well

• 
  李新宝 (@lixinbao_X) reported 18 minutes ago

  Just watched KK's technique. Damn. Absolute game-changer. Install 7 skills in Codex. Writing, images, covers, PPTs. Full pipeline, done. The principle is dead simple. Break the workflow into 7 parts. One skill per part. Only do one thing. Step 1 Open GitHub, find a repo. Copy the link locally. Create a project folder to save it. Step 2 Write the skill description. Input three things. What it does. What the input is. Output and acceptance criteria. Step 3 Run it and find the bottlenecks. Where it stalls Create a new skill and break it down. Don't let one skill Do 7 things it's bad at. This works for writers, Xiaohongshu creators, WeChat pub runners, Video script writers. How many skills you got installed? Have you tried it yet?

• 
  YNWA🐦‍🔥 (@YNWAcrypto) reported 19 minutes ago

  The problem isn’t subtle. GitHub Sponsors has paid out ~$50M total since 2019. core-js: 9 billion downloads, running on half the top 10k sites on earth. Its maintainer was making ~$600/month when he called open source “fundamentally broken.”

• 
  nasuy (@n_asuy) reported 21 minutes ago

  i think @xai should be ADE. now they have a chat, cursor, enough coding models and harnesses, strong signal like bookmarks or down votes, video creatives, profile / chat / relationship contexts. if so, we don't have to depend on discord or any chat apps. easy to invite x people to cowork. there is no need to connect Linear, Slack, or GitHub to another platform and ask that platform to solve their problems. true AI chat is a SNS, not a single UI. there is a UX that only xAI can realistically build in the world.

• 
  Krish Subramanian (@krishnan) reported 22 minutes ago

  Software engineers got automated first. Not because the work was hard. Because it was easy to grade. Everyone blames the missing union. Coders never organized; doctors, lawyers, and electricians did. That is half the story, and the wrong half. Two things get mashed together here: how easy a job is to automate, and who sets the terms when it happens. Take the first. Code is text. The training data sat on GitHub, free. And code grades itself. A compiler and a test suite tell a model in seconds if it was right. That feedback loop is rocket fuel for machine learning, and almost no other job has one. A nurse does not come with a test suite. The result shows. On SWE-bench Verified, a set of real GitHub issues, top agents went from about 20 percent in August 2024 to near 90 percent by early 2026. Human developers score around 67 to 70 percent. The machines have passed us. And the people who built these systems aimed at their own jobs first. The damage is not a prediction. Stanford's payroll data shows employment for developers aged 22 to 25 down nearly 20 percent from its 2022 peak. Now the comfortable read: seniors are fine. Workers over 30 are holding steady. For now, AI writes the code and seniors supply the judgment. "For now" is carrying that whole sentence. Seniors feel safe because the tools write code but cannot yet own messy, ambiguous, system-level problems. That is a line moving up, not a wall. Every benchmark shows models climbing toward harder, multi-file work. Senior judgment is the next rung, not a different ladder. Kill the bottom rung and you kill the pipeline that makes seniors at all. So, the union question, framed properly. A union could not have stopped this. A picket line does not repeal a capability. What it changes is the terms. In 2023 the Writers Guild cut the first real AI deal in any industry. They did not ban the tech. They won this: a studio cannot force you to use AI, AI output cannot take your credit or pay, and the company must give notice first. Engineers won none of that. So the capability landed on the employer's schedule. No warning. No floor. No severance. No seat. Exposure and protection are different levers. Most of us have neither. The juniors already know this. The seniors are next.

• 
  rapaya (@rapaya) reported 29 minutes ago

  OpenCode connects to LSP so the AI gets your actual compiler diagnostics in real time — type errors, warnings, the full signal your editor sees. Terminal-based, 75+ model providers, 160K GitHub stars, open source.

• 
  0xstack (@eth0xzar) reported 29 minutes ago

  DON'T BUILD A COMPANY. BUILD SOMETHING PEOPLE CAN PAY FOR THIS WEEK. This girl started in February. A few months later, her product had already processed over $6,000 in payments. Just a cheat Claude project she decided to turn into a real product. Here's the process: > Build something useful for yourself. > Tell Claude to push it to GitHub. > Connect Supabase so multiple users can use it. > Deploy it with Vercel. > Connect Stripe. Now people can actually pay you. You don't need a revolutionary idea. You need: > GitHub > Supabase > Vercel > Stripe > guide from Anthropic And a problem worth solving. This article will help you build it 👇

• 
  Mathieu A. (@zoontek) reported 31 minutes ago

  What are the most annoying bugs you still encounter with React Native? 👀 Please share GitHub issue links 👇

• 
  Programmers.App (@programmers_app) reported 32 minutes ago

  @Lovable @claudeai One very big fix is the Claude Github connection which fails many times, now #Lovable MCP solves that, great job! 🚀🚀🚀

• 
  Romano Roth (@RomanoRoth) reported 32 minutes ago

  2/ CodeRabbit (Dec 2025), 470 GitHub PRs analysed. AI-co-authored code: 1.7x more issues per PR, 75% more logic and correctness errors, 2.74x more XSS vulnerabilities. Velocity up. Quality down.

• 
  Crystalwizard (@crystalwizard) reported 33 minutes ago

  how about you now fix the false positive triggers - i put in an issue about this on github yesterday, and discovered there were already a number of other identical issues - from other people, that had been opened for a while now and that are being 100% ignored

• 
  ˚₊‧꒰ა ☆ Kira ☆ ໒꒱ ‧₊˚ (@sheriffmongoose) reported 34 minutes ago

  the problem with jumping from github to gitlab is constantly having to retrain your brain to call it "merge request" instead of "pull request" 🥲