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:

• 
  Mihovil Ilakovac (@infomiho) reported 5 minutes ago

  I have a problem, I like to polish stuff I build too much even if there is 0 users 💀 I now realized that there is so much friction with CodeShot and people actually trying the bring your own agent experience when building your custom themes! It's so many steps: - login with Github - click "Your ambients" - click "Create a new ambient" - enter some random name just to get through - and only then you see the Copy prompt button Iterating on a new version that takes you straight from homepage to the Copy prompt screen

• 
  Sasha 🐑💨 Koss ✱ (@kossnocorp) reported 7 minutes ago

  When we just started talking about sponsorship, I was skeptical about AI-driven GitHub PR reviews. But then I gave it a shot, and @coderabbitai noticed a critical problem that I overlooked in the very first PR review I tried. There's just no better way to win a user.

• 
  Vijay Saran (@imvijaysaran) reported 9 minutes ago

  India just put FOSS (Free and Open Source Software) to the test. It passed. The Home Ministry's cybercrime unit ordered GitHub to take down BitChat, giving it three hours to comply or face legal action. BitChat runs on Bluetooth mesh, meaning it doesn't rely on the internet, a SIM, a phone number or a central server. While the government kept shutting the internet off, BitChat kept working, and protesters adopted it. By the time the notice reaches GitHub, the app is already sitting on thousands of phones, passing messages directly from device to device. And that's where it gets interesting. Within hours, copies started spreading beyond GitHub. Radicle, GitLab, community mirrors, personal archives. Every person who copied the code became another node in the network. Every new copy made the software more resilient. This is decentralisation doing exactly what it was designed to do. Takedown orders can say "remove repositories" or "ban code," but they mostly reshape distribution and add friction. This is exactly what open source infrastructure is built for. A company has a CEO, an office and a legal address. Open protocols have contributors, users, mirrors, forks and copies spread across the world. Once enough people hold a copy, the network keeps moving through the people. This is what decentralised thinking looks like when applied to communication.

• 
  Chinonso Vivian Ojeri (@vivian_ojeri) reported 10 minutes ago

  The pipeline didn’t work on the first try. Or the second. Or the third. I dealt with YAML indentation errors, GitHub Actions failures, SSH authentication issues, AWS security group problems, and more. Each failure taught me something new.

• 
  Mike Morton (@morteymike) reported 12 minutes ago

  One of the main issues digital companies suffer with is equating product with company. At the beginning, product == company helps you get something out the door at the expense of your company’s future ability to pivot, produce another product/service, and ultimately, succeed broadly. Apple, Google, and Microsoft are good examples of the opposite - the company provides the brand, the product provides a use case to a particular kind of customer. This allows these companies to scale well beyond something like Slack/Notion/Github, who made the mistake of equating product to company.

• 
  Gaston #BIP-110 (@hodlbtc_me) reported 13 minutes ago

  @dathon_ohm They never beat the objections. They buried them. Look at the first GitHub thread on removing the data limit: comments sitting there marked as abuse, off-topic and spam. Luke's 2023 fix is locked, reason "too heated". Which side had to close the room?

• 
  Sloemo (@Sloemo_dzn) reported 17 minutes ago

  told @NousResearch hermes agent to start a tab and introduce itself to chatgpt and then told it to go fork yourself 💔. browser automation lets me access my github too without actually making a token or running any code in the terminal. what makes it crazier is that i can tell it to read a few of the issues in there and then start a pr based off those issues

• 
  Vitor Pepicon (@vitorpepz) reported 20 minutes ago

  Today I wanted to spend the afternoon outside, but my ebook reader (based on a @karpathy GitHub project with a few changes of my own), was running locally on my desktop 3 or so prompts later, codex had adapted it to my specific server and database and made it more mobile-friendly. All in ~30min, while getting dressed and waiting for my wife I used to run a team of developers. Back then this would have taken at least a day (prob more) and cost me hundreds of dollars

• 
  Cory Parry (@coryparrry) reported 23 minutes ago

  If you are using Sol in Codex, I highly encourage you to add this temporarily to your global agents.md This was the result, running the same prompt in 2 different threads with and without the prompt. 38.6% fewer total tokens: 81,396 versus 132,607, saving 51,211 tokens—and about 41.7% faster: 41.8 seconds versus 71.8 seconds, saving roughly 30 seconds. Second image shows the comparison GitHub issue in 🧵

• 
  nassar (@nassarhayat) reported 24 minutes ago

  @konstiwohlwend cursor's game seems to be to keep existing workflow and add agentic flow to it, which is why building github clone feels natural and probably worthwhile for them agree that it actually needs to be reinvented, but that's a harder problem

• 
  3D Print Hashira. ☸️ (@the_Spartan_Dev) reported 32 minutes ago

  Am I the only one who can’t push to GitHub? Is GitHub down?

• 
  WorktreeWise (@worktreewise) reported 33 minutes ago

  If you are using AI tools like Cursor, Copilot, or Claude to generate code, run them in parallel *** worktrees. Agent 1: Refactor auth Agent 2: Write tests Agent 3: Fix UI bug All working on the same repo at the exact same time. #*** #GitHub #DevTools

• 
  WorktreeWise (@worktreewise) reported 34 minutes ago

  Branches are not the problem. Your branch-switching workflow is. Why discard your current runtime state just to review a PR? Keep your feature branch running in Worktree A and review the PR in Worktree B. #*** #GitHub #DevTools

• 
  Lain on the Blockchain (@CryptoCyberia) reported 35 minutes ago

  @piliponful They're trying to take the Github down, so I imagine they already got it removed from the stores

• 
  Scott Chacon (@chacon) reported 36 minutes ago

  How is GitHub Pages still Jekyll only? I'm glad they haven't deprecated it or shut it down, but this could have been a Vercel competitor (before Vercel existed) but instead it's just this weird limbo thing.