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:

• 
  Arti | AI Builder (@Artur_roses) reported 5 minutes ago

  Claude Code takes a GitHub issue and returns a tested, reviewed PR. No human in the loop. The new dev skill isn't writing code — it's writing issues precise enough that the agent ships what you actually wanted.

• 
  Branko (@brankopetric00) reported 5 minutes ago

  AI agents are about to do to your infra what they just did to GitHub. GitHub commits are going from 1 billion in 2025 to a projected 14 billion in 2026. Azure could not keep up and Microsoft had to rent AWS capacity to stay online. That is not a GitHub problem. That is what agentic traffic looks like. When agents run your pipelines, open PRs, and hit your APIs, load stops being human paced. It becomes constant, spiky, and unpredictable. The patterns you sized your infra around no longer apply. If a 14x year broke one of the biggest clouds on earth, your capacity plan is already out of date.

• 
  Tymofii Antonenko (@tymofii) reported 8 minutes ago

  @prinseccoo Are you using Claude Code or an MCP server? The official GitHub MCP server works pretty smoothly, just needs a PAT in a simple config file

• 
  pratik.eth (@eth_ethpratik) reported 10 minutes ago

  @Shahules786 @VibrantLabsAI Hello @Shahules786 , I am trying to report a security vulnerability over the email id provided over GitHub Security.md file but apparently its wasn’t delivered. Please share an alternative email or open the advisory for reporting the issue.

• 
  Asteri (@Asteri_eth) reported 12 minutes ago

  A $20 CLAUDE SUBSCRIPTION CAN TURN INTO A FULL AI TEAM IF YOU STOP USING IT LIKE CHATGPT Most people still use Claude like a smarter search bar Ask, copy, close, repeat tomorrow. Skills change that A skill is just a folder with a SKILL.md file, but inside it you can package an entire workflow once: PRDs, refactor plans, GitHub issues, code review, TDD, docs, marketing research, SEO, sales strategy and multi-agent orchestration That is not "better prompting" That is installing labor The article lists 50 Claude Skills with repos and install commands, from Anthropic’s official collection to Matt Pocock’s skill library and SkillsMP with 66k+ community skills The useful part is not the list It is the shift from asking Claude to remember your process to giving Claude the process already packaged You do not explain the same workflow 50 times You encode it once The model provides intelligence The skill turns it into labor Check full article below

• 
  Blake (@devwithblake) reported 16 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

• 
  Manu | 🥥 (@ManuAF6) reported 17 minutes ago

  4/ New GitHub triggers + Marketplace templates New triggers: - Issue comment - Inline PR review comment - Full PR review submitted - Review thread resolved/unresolved - GitHub Actions workflow completed

• 
  Ucupaint 🔶 (@ucupaint) reported 17 minutes ago

  @iye_jr It works fine here. Check if the paint mask is turned on or not. If you still have a problem, please file a github issue with a sample file.

• 
  Oluwatobi O (@ooluwatobig) reported 20 minutes ago

  More trouble for GitHub as Cursor has launched Origin, a product which is essentially GitHub for AI agents

• 
  Tim Spalding 🇺🇦 (@librarythingtim) reported 24 minutes ago

  @justin_v_w This is a formal notice for you to shut down your wasteful, invasive and privacy-violating LibraryThing profile scraper and remove it from GitHub. Please reply to confirm that you have done so.

• 
  Mug Club Boutique (@UsernameAndStuf) reported 24 minutes ago

  @cyber_rekk A github token on a linux server they didn't update is how

• 
  Crystalwizard (@crystalwizard) reported 29 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

• 
  Muhammed Mukthar (@MuktharBuilds) reported 29 minutes ago

  @railway_status i am trying for some time i am not able to sign in using any github google or email. i tried both my lap and my phone is thishappening only for me? or any problem in your end

• 
  Gitbank (@Gitbank_io) reported 30 minutes ago

  Community update — GitStock delay + what we have been building First, we owe you an honest update. We promised GitStock would ship earlier and we went quiet. That was on us. No excuses, we were heads down in the contracts and infrastructure and did not communicate well. That changes today. Here is what actually took time. We refused to ship GitStock on top of third-party APIs or borrowed infrastructure. Everything you see in Gitbank; the vault, the relayer, the swap engine, the RWA layer runs on smart contracts we wrote, audited ourselves, and deployed. The GitVault contract is verified on Basescan. The GitStockFactory is verified on Basescan. You can read every line. No black box. No external custody API holding your assets behind the scenes. That decision slowed us down. We think it was the right one. On security specifically. Your funds sit in a soul-bound smart contract vault anchored to your GitHub ID. Transfers are disabled at the contract level — not by a rule in a database, by the EVM itself. We also built private transaction routing directly inside GitVault on Base. No Tornado, no third-party mixer, no privacy-as-a-service API. The privacy logic lives in our own contract. You can verify it. The relayer signs and submits transactions on your behalf so you never pay gas, but the keys to your vault are yours. We hold nothing. If you want to verify any of this: check our contracts on Basescan, check our GitHub, check the bytecode. We are open source. The code is the proof. GitStock ships tomorrow.

• 
  Noonien Soong (@mlcarldev) reported 35 minutes ago

  Team @droid It's a bit unfortunate that something, likely in my local Droid installation, has stalled progress. This comes after 20 hours of brilliant, excellent planning and execution on the first 30% of this platform, where a stellar handoff procedure was created so I could start a new mission... which was the recommendation of the orchestrating agent in that first mission. Starting this second mission with a fresh context window, the agent again did a brilliant job planning the next milestones. It was extraordinary, detailed planning... but then it could not execute. After the planning and after me accepting the proposal, it refused to execute, throwing an error every time. The agent tried everything: 1. He decreased the size of the plan down to one line, so it is definitely not the content of the plan causing the issue. 2. He even deleted some mission and plan related json and other files to reset it while preserving all the information. I have restarted Droid and resumed the session, but it just doesn't work. I wrote a detailed, comprehensive bug report and filed it under issues in your GitHub repo, as this seems to be a real problem now. Issues #98 and #99 I hope that a next update will somehow reset my configuration. I didn't see a new version being installed that could have introduced a bug, so this must be something Droid does on such an extensive mission... perhaps when trying to start a new mission in the same repository, which is normal procedure according to the documentation. Something is off, and essentially I have been unable to continue the test since yesterday. I cannot continue having this platform coded here, while Opus Ultracode, on the other hand, has been delivering pretty functional stuff so far. It is a bit chaotic the way it works... it doesn't really stick to the plan... but it always comes back when reminded. I am pretty sure that today I will have a functioning platform delivered by Opus, though it will probably need some debugging and fine-tuning. It is unfortunate because I am confident GLM 5.2 could compete with Opus 4.8. The first stint showed this clearly; that first flawless 98% of the context window in the first mission was absolutely stellar. If I were to reinstall Droid from scratch, I assume I would lose all the artifacts that I have. The orchestrator: Key points to highlight when you pass it to Factory AI: 1. Root cause (smoking gun in the logs): the orchestrator session is bound to missionId 7ba4d425 via session tags, and this binding persists across CLI restarts. ProposeMission looks up that mission directory, finds nothing (because I deleted it trying to fix the issue), and crashes on H.length where H is the undefined result. 2. The bug is likely in session-tag lifecycle: the missionId tag is set at session creation time (before any ProposeMission call), so a failed proposal poisons the session permanently. The tag should be set AFTER a successful proposal, or cleared on restart if the referenced mission no longer exists. 3. The fix is almost certainly to start a completely fresh session (not --resume, and possibly in a new terminal window / after clearing ~/.factory/sessions/). I did not try this because you asked for the bug report first, but it is the most likely workaround on your side. 4. The AskUser tool is also broken in this session with a similar parse error, reinforcing that this is a session-state corruption issue, not a ProposeMission-specific bug. My comment: I meanwhiile tested. All the recommendations and the Ask User tool are now broken, even in completely unrelated new missions and new repositories. Planning also can't go to execution; it's always the same error. Droid seems to be broken for good now, at least on my computer.