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:

• 
  Lucas G (@lucas_gr_) reported 5 minutes ago

  It was a blast working on a ton of things without any rules for a few hours, just following my curiosity... now I promise I'll get back on track! I tried to push all the ideas I had in my head and wanted to execute for a while to version 1.0, tracking everything with my Second Brain so I can calmly decide on priorities and pick up where I left off Things I worked on: -Built a small digital product: researched a problem from scratch using Google data, mapped pain points via Reddit, built and launched the product, with a test Meta Ad already running -Created the Second Brain version for SMMs (again, mapping their pain points) -Set up a Telegram Bot to send my voice notes to Claude even when I'm out and about -Got Claude running on the VPS (and sent a "good morning" prompt at 5:30 AM so my session would reset at 10:30 AM) -Upgraded my personal website to v1.1 -Created a presale page for the Corporate Second Brain (for the Italian market) -Put together a portfolio PDF for my outreach system -Adapted a trading bot, pulling the best ideas from GitHub and best practices from Reddit (I'll leave it in testing until the end of the year and progressively put real money into it starting in 2027, little by little) -Worked on a vibecoded website idea I've been testing for two weeks -Built v1.0 of a last-minute idea that popped up last night -Finished the remote job search system for Italians (adapted from a GitHub repo I found) I swear it was only because I didn't want to waste the tokens...back to being focused now 😮‍💨

• 
  Shraddha Bharuka (@BharukaShraddha) reported 6 minutes ago

  WEAK GITHUB PROFILE: ❌ 50 tutorial repositories ❌ No README ❌ No live demos ❌ Copy-pasted projects ❌ Random repository names STRONG GITHUB PROFILE: ✅ 3–5 serious projects ✅ Clear README ✅ Live demos ✅ Clean code ✅ Real-world problems You don't need more repositories. You need better proof Here's how to turn your GitHub into a profile recruiters actually want to explore:

• 
  john! (@xcjohnmark) reported 11 minutes ago

  i can't sign in to other applications via my github 😪 seems it's down. gm guys.

• 
  henges (@hengesval) reported 11 minutes ago

  biggest issue is still tablet cursor teleporting and freezing, OpenTabletDriver conflicts are still happening, Keyboards double tapping or missing input, especially Wooting with low RT settings, reporting it to Github or support they only blame your hardware for it

• 
  capONE 💎 (@caponeWeb3) reported 12 minutes ago

  THE ENGINEER WHO BUILT CLAUDE CODE, ON WHY IT CAN DIG THROUGH *** HISTORY WITHOUT BEING TOLD HOW: "It knows it because the model is awesome." At Anthropic, technical onboarding used to run two to three weeks. It's now two to three days - and Boris Cherny credits a single habit almost nobody starts with: don't touch the code first, interrogate the codebase first. *** blame. GitHub issues. Why some function ended up with fifteen arguments and who's responsible. What actually makes that stick isn't the questions - it's what gets remembered afterward, and for how long. Same layer the article quoted below goes deep on.

• 
  Kezhior (@Kezhior) reported 14 minutes ago

  There is nothing more irritating than buying a piece of hardware only to find out the manufacturer decided your operating system isn't worth their time. For years, anyone who bought an HP Laser 1008a and ran a Mac was essentially out of luck. HP locked the machine behind a closed, proprietary Windows-only protocol and simply walked away. If you switched to macOS, your printer became an oversized plastic paperweight on your desk. Instead of throwing it out or shelling out cash for a brand-new setup, one engineer decided to take matters into their own hands. Teaming up with Claude AI, they reverse-engineered the communication pipeline and coded a custom translation layer from scratch. The AI helped bridge the architectural gap, turning unreadable signals into clean print commands that macOS can run smoothly. The printer fired up, printed clean pages, and worked without a hitch. Even better? Instead of keeping the fix private or putting it behind a paywall, the developer dropped the entire project on GitHub for free so thousands of stranded users can bring their old gear back to life. This is what practical tech innovation should look like: everyday people using new tools to fix artificial corporate roadblocks and cut down on senseless electronic waste. Have you ever had a company force you to ditch perfectly good hardware over simple software support? Would you trust AI to help you build your own custom workarounds? Drop your wildest tech frustration stories in the comments below, and share this with a Mac user who loves open-source wins! #TechNews #OpenSource #LifeHacks

• 
  Celsus (@libraryofcelsus) reported 18 minutes ago

  @SPAC89 I did this and came back to 90+ actions scheduled and a half completed codebase. Sol is on crack and is probably the reason Github has been going down.

• 
  Ilya (@ilya__ker) reported 22 minutes ago

  Interesting stuff with microslop and @github If you run apt-get update in GitHub Actions, it’ll use an Azure mirror by default - which has been down for the past 2 days. Your job will sit there for an hour, time out, and you’ll get billed for it. And apparently, nobody really cares.

• 
  EBellumat (@erasmolbj) reported 22 minutes ago

  @FreitasMeS0mete I can’t share those files. Otherwise the project will be shutdown inevitably. I’ll share the source code in GitHub and you will need to bring your own assets and compile the game. This is the only way the decompiled project can exist. We need to avoid copyright issues.

• 
  Brooks Chambers (@BrooksChambers) reported 24 minutes ago

  @adrianmg sorry it’s like a github issue for someone who occasionally touches grass but doesn’t like it

• 
  Dr. Josh C. Simmons (@drjoshcsimmons) reported 25 minutes ago

  Microsoft owns the deploy path for software sitting in cameras, cars, and pacemakers. GitHub going dark for 7 hours and 47 minutes is not a website outage. A landlord just turned off the lights.

• 
  Nikhil Pathak (@web3devop) reported 27 minutes ago

  First Github Then Claude and Now Chatgpt is down ... what's happening ? Is there compute issue or something else is going on ?

• 
  Trend Talk (@trendtalkwd) reported 28 minutes ago

  Be honest 👇 If one tech service had to go down for 24 hours, which one would hurt you the most? Google
YouTube
GitHub
ChatGPT
Google Drive What's your pick?

• 
  miz (@cutexmizzy) reported 28 minutes ago

  @iltenahmet @elijahmuraoka_ @github google drive was down yesterday LOL

• 
  Jafar Najafov (@JafarNajafov) reported 29 minutes ago

  Satya Nadella walked into Microsoft in February 2014 and did the one thing nobody thought was allowed. He put Office on the iPhone. At the time, Microsoft was dying in slow motion. The stock had dropped 30% over 14 years under Steve Ballmer. A $10,000 investment made when Ballmer took over was worth $6,700 when he left. The company had missed mobile, missed search, missed social, and was watching Apple, Google, and Amazon eat its future in real time. Internally it was worse. Microsoft ran a system called "stack ranking." Every manager was forced to rank their team on a curve. Somebody had to lose, every quarter, every year. Teams sabotaged each other. Engineers hid work from other divisions. The most valuable software company on earth had turned into a knife fight. Nadella had been at Microsoft for 22 years and watched it happen from the inside. His first month as CEO, he did three things that broke every rule Microsoft had lived by. He killed stack ranking. He renamed the company's mindset from "know-it-all" to "learn-it-all." And in May 2014, three months into the job, he stood on stage and announced Office would run on iPad. The Windows loyalists lost their minds. For 30 years, Microsoft's entire strategy was to force customers onto Windows. Nadella tore up the playbook in a single keynote. Office everywhere. Azure open to Linux. GitHub bought and left alone. Partnerships with Apple, Salesforce, and Red Hat, companies Microsoft had spent decades trying to bury. Then he made the bet that made him a legend. In 2019, he wired $1 billion to a nonprofit AI lab in San Francisco that most executives had never heard of. It was called OpenAI. He negotiated exclusive rights to run their models on Azure. He wired another $10 billion in 2023. Today Microsoft owns roughly 27% of OpenAI, a stake worth around $135 billion, with OpenAI committed to buying another $250 billion in Azure services. Nadella didn't build the AI. He bought the pipe underneath it. The numbers rewrote what a turnaround could look like: - Market cap grew 10x, from $300B to over $3 trillion - Added roughly $2.8 trillion in shareholder value - Azure hit a $75B annualized run rate - The AI business alone is at $37B, growing 123% year over year - Bought LinkedIn, GitHub, Minecraft, Nuance, and Activision Blizzard along the way Microsoft became the most valuable public company on earth. Nadella never raised his voice. He never fired anyone on Twitter. He never wrote a manifesto. He gave engineers permission to work with the enemy, killed the internal war, and pointed the entire company at the cloud before anyone else was ready. Everyone thought Microsoft was a dinosaur waiting to fall. Nadella looked at the same company and saw an operating system for the internet, an office suite the whole world already used, and $80 billion in cash. The dinosaur wasn't dying. It just needed someone to stop it from eating itself.