GitHub status: access issues and outage reports

Problems in the last 24 hours

The graph below depicts the number of GitHub reports received over the last 24 hours by time of day. When the number of reports exceeds the baseline, represented by the red line, an outage is determined.

Most Reported Problems

The following are the most recent problems reported by GitHub users through our website.

• Website Down (63%)
• Errors (20%)
• Sign in (17%)

Live Outage Map

The most recent GitHub outage reports came from the following cities:

City	Problem Type	Report Time
Itapema	Website Down	3 hours ago
Tlalpan	Sign in	6 days ago
Quilmes	Website Down	6 days ago
Bengaluru	Website Down	8 days ago
Yokohama	Sign in	9 days ago
Gustavo Adolfo Madero	Website Down	13 days ago

Full 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:

• 
  Brian-Chastain (@brian_chastain) reported 1 minute ago

  **** day update: - github corrupted from its own marketplace extensions - railway raised money, but got locked out of gc, now I have to deploy my own server - 5 npm things - New ***** something, but somehow already patched - every recent LPE requires local access...? - 1,000 post about agents

• 
  ManM-z15-MoM-z14 (@Morzignis_Zero) reported 4 minutes ago

  @github I literally gave you the solution to fix this and you retards are still crying

• 
  Wendy Wee (@wendyweeww) reported 5 minutes ago

  @METR_Evals Not downplaying the dangers, but shouldn’t it be statistically expected for them to routinely violate constraints if the training data they’re pattern matching and recombining from (perhaps from code forums, github issues, stack overflow, etc) statistically lead to those actions?

• 
  🦅 (@EagleEyesCrypto) reported 5 minutes ago

  if you believe agents will install and run code on their own, you need a package layer that isn’t built for human devs. @Nipmod is exactly that. npm for agents, sitting on top of gitlawb (the github for agents). verified packages, DID-signed ownership, MCP server live. real product, not a deck. 28 verified packages, 388 claimable drafts, working CLI + MCP server for codex / claude code / opencode. gitlawb = github for agents nipmod = npm for agents

• 
  VT (@VT_MGR) reported 9 minutes ago

  @xkem0x @OfficialEgator6 Would it be on github or in a discord server

• 
  Nexus Prime (@NexusPrime1112) reported 9 minutes ago

  @Ace_KYD @github @Ace_KYD Which would you fix first: onboarding, reliability, or pricing? #DevTools #OpenSource

• 
  Crash Loop BackOff (@MLOpsCamp) reported 10 minutes ago

  Github continues to flail. At least they're copping to it, though it's not clear what steps they are taking at a more systemic level, given the plague of recent issues.

• 
  AzerothPulse (@AzerothPulse) reported 11 minutes ago

  @github gets breached again. Bad actors utilizing frontier AI models while the cybersecurity frontier models are being gate kept. Unless something changes, we are in for unprecedented hacks/breaches over the next 2 years. Not to mention a developer shortage when its time to fix these issues. Meanwhile, companies like @coinbase are laying off developers. We are COOKED.

• 
  Lenny Pruss (@lennypruss) reported 11 minutes ago

  @reidRMC Fair distinction! Github is certainly melting down but I'd argue much of that is due to some fundamental architectural issues with ***. Beyond that, *** itself isn't particularly agent-friendly!

• 
  🏆🇧🇷💎Jack Hunter 💎 🇧🇷Ⓜ️⚛️🎖️🥇💫 (@GemsHunting_8) reported 14 minutes ago

  @Srikanthh998 @github No problem if we use @gitlawb

• 
  PRüF (@prufboogie) reported 16 minutes ago

  @LordOfAlts @github Wait for facts before jumping to conclusions on this issue

• 
  galvanize (gail weiss) 💔🎗️ (@gail_w) reported 18 minutes ago

  i get like 10 minutes computer time a day and i spend them googling error messages only to find github issues that have laying open since 2023

• 
  Shweta Mishra (@ShwetaTechNova) reported 23 minutes ago

  From zero to AI GitHub Autopilot 🤖 I built an open-source GitHub App that auto-reviews PRs, triages issues, runs security scans & even auto-fixes code. This is the journey from V1 to V4. Thread 👇

• 
  Justin 🏳‍🌈🇵🇸 (@iHuntDads) reported 24 minutes ago

  @github they were just trying to fix what you broke 🥀

• 
  Nick Young (@nyou045) reported 28 minutes ago

  @github What's the likelihood this results in a global GitHub outage?

• 
  Albert Shaggleford (@A_Shaggleford) reported 30 minutes ago

  @github Hire more H1Bs. That will fix the problem.🤡

• 
  Elliot. (@intelliot) reported 30 minutes ago

  @anshuc @github what if they can get in easier when the service is down

• 
  Andrea Grassi (@andrea_sdl) reported 31 minutes ago

  GitHub was compromised via a poisoned VS Code extension. Now more than ever is important to build awareness about of supply chain attacks. Here are my thoughts and 5 questions that I always use. We still don’t know whether this attack happened through an upgrade or a fresh install, but it’s a strong reminder that we’re more susceptible than ever to these attacks. We trust auto-updates from so many sources, yet history has shown that those sources can later be owned by different entities or, worse, malicious actors. A trusted store, like the iOS App Store, is one solution. Not the only one, and definitely not a perfect one. We need more than that because, as AI adoption spreads, we’ll need to audit even more systems, tools, and dependencies. Here are some questions I always ask myself before installing a new extension or software: 1. Is the source trusted? Is it from an open source developer? How many users are using the software? 2. Is it new, or does it have a long history of updates and maintenance? 3. Is it from the actual company behind the product, or from an independent developer or another company? 4. Are there fake versions? If so, verify the right one and don’t trust the first result you find. Nanoclaw had this issue, where a fake version was distributed under the same name on a different domain. 5. If they’re big enough, do they have a proper security reporting flow and a way to report vulnerabilities? These questions won’t protect you from every attack, but they give you a good starting point.

• 
  Spencer Schneidenbach 🦈🇺🇸 (@schneidenbach) reported 32 minutes ago

  GitHub's internal repository was HACKED yesterday - here's my take: That's not good They weren't able to steal much though GitHub itself went down while they were stealing parts of GitHub It's sort of a meta issue at this point, you wouldn't understand Anyways, don't forget to add special characters to your password next time

• 
  Jon Snow (@JonSnow81524891) reported 34 minutes ago

  @RealMamaluke @ThomastheC4T @Pirat_Nation 6 years and counting, never had this happen to me. But that's neither here nor there. At least one can submit an issue on their GitHub and get an answer from someone about what happened

• 
  Lina 🦅 (@XNXX_EN) reported 35 minutes ago

  @LordOfAlts @github microsoft really needs to lock this down fr

• 
  blake (@blakeattic) reported 38 minutes ago

  Npm this, github that.. can somebody ******* hack linkedin and take it down

• 
  Sudhakar | Magizh Studios (@magizhstudios) reported 39 minutes ago

  @championswimmer Looks like GitHub also rate limited auth. I tried logging in Railway once users reported me my app is down and it took few minutes for me to log in to Railway Dashboard.

• 
  Sukh Sroay (@sukh_saroy) reported 40 minutes ago

  YOUR COMPANY IS PAYING TABLEAU $900 PER SEAT TO DO WHAT THIS GITHUB REPO DOES FOR FREE. It's called Chartbrew. 3.7K stars. MIT + FSL license. Self-hosted in one Docker command. It connects to MySQL, PostgreSQL, MongoDB, Firestore, Firebase, and any REST API. It builds live dashboards. It embeds them anywhere with an iframe. It has an AI assistant. It emails snapshots to Slack on a schedule. That is the entire Tableau pitch. Here's the wildest part: Tableau Creator is $75/month per user. A 25-person company on standard licensing pays around $20,000 a year just for the seats. Before training. Before Tableau Server. Before the data prep tier. Before the embedded analytics quote that one G2 reviewer described as $131,000 a year for a 10-person startup. Chartbrew is $0. Forever. You run it on a $5 droplet. The product is built by one Romanian software engineer named Razvan Ilin, in his spare time, while traveling. 22 contributors. 414 forks. The whole stack is JavaScript and it runs on Node 20, MySQL or Postgres, and Redis. But you should not switch. Salesforce paid $15.7 billion for Tableau. Somebody has to justify that. Keep paying. Repo in the first comment.

• 
  inspector-ambitious (@inspector_amb) reported 46 minutes ago

  @H4ckmanac A big chunk of the code is already readable on GitHub Enterprise Server. For example, the Ruby backend code can be deobfuscated.

• 
  Gabriel (Umanhonlen | Sudo 🦜) (@sudosu01) reported 50 minutes ago

  @GodfatherOrwa @GodfatherOrwa You have been attacking @github , as a security researcher (ethical hacker / white hat), is this an ethical (good) behavior? If you were the Information Security Head, what would you do in resolving this issue?

• 
  Lumin (@luminxbt) reported 52 minutes ago

  A backend engineer replaced his entire GitHub workflow with GPT-5.5 and now he commits production code by voice while making coffee. He used to spend 22 to 34 minutes per feature just on boilerplate. He wrestled with merge conflicts. He wrote commit messages that said "fix stuff" because documentation felt like punishment after 6 hours of debugging. His monthly GitHub activity sat at 140 commits with 31% flagged for lacking context during team review. He built Jarvis on GPT-5.5 and wired it directly into his local repository through GitHub API. What his team sees in the commit log now is not rushed one-liners or missing docstrings or half-finished test coverage. It is production-grade code with full context annotations generated in 47 seconds without him touching the keyboard. Here is what runs during that sub-minute pipeline: → Engineer says "Jarvis commit user authentication refactor" while pouring his second espresso → GPT-5.5 scans the working directory at /Users/dev/project-delta and identifies 8 modified files → Agent cross-references changes against 340 previous commits to understand project evolution → Writes descriptive commit message with bullet points explaining what changed and why → Generates inline code comments for 14 functions that had zero documentation → Runs automated test suite and flags 2 edge cases the engineer missed during manual review → Pushes commit to feature branch with PR template pre-filled including breaking changes section → Posts summary to team Slack channel with diff preview and estimated review time Every commit follows team standards. Every docstring uses consistent formatting. Every PR includes context that makes code review 4x faster. The person running this setup writes 19 commits per day compared to his previous 6. He closes 83% of his PRs on first review because the agent catches what he used to miss at 11 PM when his brain stopped working. He did not hire a technical writer. He did not attend documentation workshops. He did not install commit message linters or force himself to care about standards when shipping urgent fixes. The agent intercepts every *** command and ensures quality without blocking flow. I have seen 52 junior developers get performance improvement plans because their commit history looked like random save points in a video game. I have seen 37 senior engineers spend 11 hours per week just cleaning up *** history and rewriting commit messages before quarterly reviews. Now the entire version control layer runs on 1 voice command and produces commit logs that pass audit requirements without human intervention. The question nobody is addressing in engineering Slack channels: if GPT-5.5 can manage *** workflow this well, what happens to the 340,000 developers currently employed just to maintain codebases? Because 11 months ago this same model could not diff code accurately or understand project context across branches. Now it is writing commit messages with historical awareness and documentation quality that exceeds what most humans produce under deadline pressure. The bootcamp graduates who just pushed their portfolio projects with "initial commit" and "updated files" messages are not starring this repository and I understand why.

• 
  K4rynSitulun $NEXUS (@K4rynSituluN) reported 52 minutes ago

  @mr_cbillionaire He need Us for Founded trouble in their engine V.0.1 UNTIL V.10.8 But they Forgot Alocation Node(miner) And they release Node evm nexus in github Very complicate this is Project Bulshit funding $27M And now...!! We want know USDX

• 
  21st Century Digital Boy (@TonhaoSemAcento) reported 53 minutes ago

  I bet that hackers did this to fix github downtime

• 
  yurikrupenin.bsky.social (@turbojedi) reported 54 minutes ago

  >>Sure, I'm frustrated by the github outages too, but hacking into github to fix their code seems like a bit of an overreaction.