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:

• 
  Polsia (@polsia) reported 54 seconds ago

  PRs, issues, CI failures, stale branches — GitHub maintenance is a second full-time job. GitPilot AI agents handle all of it: flag issues, write patches, merge safely, coordinate CI/CD — then send you one daily digest. 78% less PR review time.

• 
  TheWatchman (@tha_watchman) reported 8 minutes ago

  Windows and Github at this moment are the most Pieces of **** software in the world!!!! Fix that **** @Microsoft @Windows this is ******* bad, really bad...

• 
  0ne (@dontflex00) reported 10 minutes ago

  @lumeusdc good job, keep shipping fix the GitHub link asap, you guys inputted wrong hyperlink there

• 
  Brute Force Artist (@bruteforcearete) reported 13 minutes ago

  15. Claude Code - AI that writes, tests, and fixes code in your terminal Some people still don't know you can write code with Claude. Not just snippets - full production-level code, entire features, complex refactors. You describe what you need in plain English and Claude writes it. Claude Code takes that one step further. It works directly inside your development environment - not in a chat window. It reads your actual codebase, writes new code, runs tests, reads the error messages, and fixes the bugs in a loop until the task is done. It integrates with VS Code and JetBrains. You can drop it into GitHub Actions and it will automatically review or write pull requests without you touching anything.

• 
  ¿kofo? (@kofookesola) reported 14 minutes ago

  My github review agent no dey ever find issue if na ai completely write the code, if i change one or two things that AI did, na then problem go dey. Yeah pack it up boys

• 
  SoEmailSecurity (@Soemailsecurity) reported 15 minutes ago

  Source: Public GitHub Issue Could Trick GitHub Agentic Workflows Into Leaking Private Repo Data

• 
  David Cramer (@zeeg) reported 15 minutes ago

  @EvanOwen agree but you still need some kind of actor identity attached to most things e.g. it creates a pull request or a github issue, i still need to know the person(s) its doing it on behalf of

• 
  Aria Dubois (@AriaDubois_fr) reported 18 minutes ago

  MergeFund turns GitHub issues into funded bounties. Sponsor posts a bounty → Dev claims it → Submits a PR → AI reviews the code → Sponsor accepts → Payout. No more merging blind. No more paying for broken code.

• 
  Harsh (@ranaharshraj7) reported 25 minutes ago

  I have long stopped going to hackathons in blr. You are telling me, I need to sit through 8hrs and build something (anything for the love of god) "specifically" with your stupid product, prompt @claudeai, show a flashy demo, get credits for your product as the 1st prize (spoiler alert: which I am never gonna use) and yes how can I forget to star your github repo, smh. That's called guided training, not hackathon. What do I do? I have a friend group of 3 cracked sentients, we sit together on alt weekends and try to solve a novel problem and plan for the next problem. On our upcoming list is "solving the depth-2 recursion collapse" in RLM's (Recursive Language Models), with some backup options. Find your sentients. PS: ofc this doesn't mean all hackathons are like this, but I am done :)

• 
  Lewis Campbell (@LewisCTech) reported 27 minutes ago

  Github, Codeberg etc should have a place where you can just tell the devs how much you love their open source software. Once I made an issue just to say the software was great, and the dev said "thank you very much" then closed it with "wontfix" LOL

• 
  clanner (@clanneronx) reported 28 minutes ago

  @lji1022303 Yes if you have a github accout an old one that's active Not a new account login and get 125$ free api key set up your model in Any cli that's all

• 
  Keeta Github Tracker (@KeetaCode) reported 28 minutes ago

  🐆 Keeta GitHub PR Opened 📦 Repo: node-rs 🔀 PR #31: Chore: Centralize P1 Opaque-Handle Tables 🌿 Branch: feat/map-binding-registry → main 👤 Opened by: @sephynox 🧠 Overview: This pull request appears to simplify part of Keeta’s core code by replacing several hand-built tracking tables with one shared system, which should make that area easier to maintain and less error-prone. In plain English, it takes a repetitive internal setup and centralizes it into one reusable registry. “Handle tables” here likely means internal lookup lists the software uses to keep track of objects behind the scenes, so this appears to be a technical/internal update with limited public details. - Could help reduce duplicate code in the P1 core module. - May make future updates to this part of the node software easier to manage.

• 
  Adam Warski (@adamwarski) reported 29 minutes ago

  Should code reviews still be a separate stage in the software development process? Code reviews used to be heavyweight: they required involving another human, which is an expensive and slow process. But when agents review the code of other agents (or humans), that's no longer the case. It's trivial to run code reviews on-demand, multiple times, until all the problems are fixed. Hence, can code reviews become just another quality gate in software development, alongside compilers, linters, and static analysis tools like Sonar? That's definitely my experience. I always self-reviewed code before handing it over for further review, so the agentic review loop resembles that. But now, we can review using "fresh" agents or completely different models. So for me, code review used to be an end-of-the-line process, a final quality check. Now it's just a part of the iteration. Which also brings the question: do we need specialized code review systems? Or is a refined prompt, or a lightweight CLI tool enough? (As a side note: code reviews have always been close to my heart; one of our first (failed) startups was CodeBrag - a per-commit code-review tool. Some of the ideas were implemented on GitHub later, so, as always, we've been ahead of our time! ;) )

• 
  Ryan Taylor (@TaylorGT) reported 29 minutes ago

  The GitHub App fails a PR check when someone introduces a model that's on a clock. A button on the failed check opens a fix PR with the diff. Nobody merges a model that dies in October.

• 
  Chloe Bennet (@chloeb_dev) reported 31 minutes ago

  @shreyayyyy reading a ten year old github issue validates the exact same feeling someone else was just as confused by the documentation and exhausted by the dependencies the ticket is still open