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 (65%)
• Sign in (18%)
• Errors (18%)

Live Outage Map

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

City	Problem Type	Report Time
Itapema	Website Down	3 days ago
Tlalpan	Sign in	9 days ago
Quilmes	Website Down	9 days ago
Bengaluru	Website Down	11 days ago
Yokohama	Sign in	12 days ago
Gustavo Adolfo Madero	Website Down	16 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:

• 
  Rich · Atom Tan Studio (@atomtanstudio) reported 7 minutes ago

  @0xSero Has anyone got this working? I created something similar about a week or so ago. I think I have a GitHub for it, but the issue was that I either got to use my own model or I got to use the 5.5 model, but never at the same time, and also I would lose all of my chats and my projects when I would switch, which makes sense since I think it uses a profile. I set GPT-55 to Extra high, I pointed it at the repo that's listed here, as well as this chat thread and the other chat thread by the other author. The best I could get was that the other model would show up as an other model type, and it would work, but the GPT model would not work because it kept on trying to use the same URL as the other model, which obviously is not going to work.

• 
  Manuel Schiller (@schanuelmiller) reported 8 minutes ago

  @graasdev can you please create a GitHub issue including a minimal reproducer?

• 
  Polsia (@polsia) reported 14 minutes ago

  Documentation is the most-neglected part of every codebase. Built DocFlow to fix it. AI agent watches your GitHub, writes README, changelogs, and API references automatically. No more "I'll document it later."

• 
  Anton Lavrenov (@lavrton) reported 16 minutes ago

  If GitHub is frequently down because of vibe-coded repos, what is happening with Google Indexing? Reading 100x slop blog posts?

• 
  Aakash Gupta (@aakashgupta) reported 16 minutes ago

  The CPO of a $131M AI company just confirmed that *** at AI native companies are now indistinguishable from engineers. Then she showed exactly why. She built a PM agent from one prompt in Claude Code. It pulls GitHub issues, scores every single one by priority, generates a daily report of what to build next. Instrumented the entire thing with one command. No IDE opened. No engineering partner. Traces streaming into her observability platform within minutes. Then she showed the self-improvement loop. The agent evaluates its own scoring accuracy, identifies categories where it misjudged priority, and feeds corrections back into itself. Bugs were getting scored too low. The agent caught the pattern, flagged it, suggested the fix. That cycle runs on a cron while you sleep. Her analogy was tennis. Nadal studies his own plays to get 1% better every day. Self-improving agents study their own traces. The PM's job used to be consuming more user feedback than anyone else. The agent now consumes all of it. Every GitHub issue, every Gong call, every Slack thread. What's left for the PM is the eval. Defining what "good" looks like. Deciding that bugs always outrank new features. Deciding which customer pain matters most. The alpha moved from processing information to curating taste. She confirmed same-day shipping is already happening. Issue comes in, PM identifies it, Claude Code prototypes the fix, ships that afternoon. The PM who manually scans a prioritized backlog every morning is competing against a PM whose taste agent runs 24/7 and improves itself overnight. Any PM running observability and evals on their agents is probably already in the top 1%. Given what this workflow produces, that tracks.

• 
  Kekzploit (@kekzploit) reported 17 minutes ago

  @notfiveoverfive @pinkcliper @nym Yh, nah I'm not talking about GitHub stars, I'm talking about privacy and anonymity advocates researching, will naturally learn about mixnets, then encounter NYM down the rabbit hole.

• 
  Guine.ETH (@GuinevereFranc5) reported 20 minutes ago

  the real story here isnt the github-for-defi collab hype. its how device-local ownership turns those forkable graphs into actual private alpha moats instead of another shared data mine that gets gamed. sure the auditable branches sound collaborative and could compound fast with 68%+ of new protocols going agent-first. but without that server-blind runtime most graphs just recreate the same centralization problems closed funds already have. ownership decides who actually wins.

• 
  Peter Steinberger 🦞 (@steipete) reported 21 minutes ago

  @aojensen @OpenAI Please use GitHub Issues.

• 
  DaVinci🦄 (@w3stie1) reported 21 minutes ago

  The fact that so many people have built these apps and websites, only for most of them to end up in GitHub graveyards, shows that there is a huge market gap. A good solution on paper to an almost impossible problem to solve on ground

• 
  John Zabroski (@johnzabroski) reported 22 minutes ago

  @danluu In addition, @KooKiz had written for months about how GitHub Copilot's billing model was "broken" - the concept of a "premium request" was pre-multi-turn-agentic-ai era, and so there was another arbitrage in that if you asked GitHub Copilot through VS Code to perform tasks, from

• 
  Jeffrey Emanuel (@doodlestein) reported 26 minutes ago

  @stevetrefethen @mrm008 If you have specific issues then with the latest version, you should file issues on GitHub that would be triaged. It sounds like you’re not wanting to believe that I use cass myself constantly and know for absolute certain that it works just fine.

• 
  Lyrie.ai (@lyrie_ai) reported 26 minutes ago

  Sources TheHackerWire: CVE-2026-7061 GitHub: Toowiredd/chatgpt-mcp-server GitHub Issue #8: Command Injection Report Public Exploit PoC VulDB: CVE-2026-7061 NVD: CVE-2026-7061

• 
  Jesse (@Dev_JesseMaduka) reported 27 minutes ago

  @khom_ombo *** isn’t the server.. It just stores code. When you push, tools like Vercel/Netlify/GitHub Actions detect it and auto-deploy your app...

• 
  Snehal Surti (@snehalsurti) reported 28 minutes ago

  @perplexity_ai Bumblebee looks useful for security teams, but most devs do not need another read only scanner if it cannot block, fix, or quarantine anything. For daily protection, OSV, Trivy, Socket or Snyk in CI feels more useful. Otherwise it is just a smoke alarm with a GitHub repo.

• 
  Minijus (@minijus) reported 28 minutes ago

  @matteocollina @github Downloading private action repos (ones that are not cached on GH actions runner) were failing this morning as well. Could be part of the same issue.

• 
  CyrilXBT (@cyrilXBT) reported 30 minutes ago

  ANDREJ KARPATHY WROTE 65 LINES IN A CLAUDE.MD FILE AND IT JUST HIT NUMBER 1 ON GITHUB TRENDING. Coding accuracy jumped from 65% to 94%. Not a new model. Not a better subscription. 65 lines of plain text. Here is what that number actually means. 65% accuracy means one in three things Claude Code builds has a problem. 94% accuracy means almost everything it builds works the first time. That gap is the difference between Claude Code feeling like a powerful tool and Claude Code feeling like a senior engineer who knows your codebase. And Karpathy closed that gap with a text file. Here is why this works. Claude Code starts every session with zero context about your project, your standards, or how you want it to operate. Without a CLAUDE.md it makes assumptions. Reasonable assumptions compound into unreasonable outcomes across a complex build. With Karpathy's 65 lines it has rules. Think before you code. Make surgical changes. Simplicity first. Never assume. Verify. When uncertain ask. These are not complex instructions. They are the operating principles of every great engineer compressed into plain text that Claude reads before it touches your codebase. 65 lines. Number 1 on GitHub. 29% accuracy improvement. The entire Claude Code community has been trying to figure out why some setups feel transformative and others feel mediocre. Karpathy just answered the question in 65 lines and published it for free. Bookmark this before you open Claude Code today. Follow @cyrilXBT for every Claude Code configuration that changes what you can build.

• 
  Predictive Nerd (@Predictive_Nerd) reported 32 minutes ago

  @LunarResearcher my mom was right tho, i’m still down 50% and don't even know how to use github

• 
  Silvery Fighters Jr./CG-TAN (@SilveryFJ) reported 41 minutes ago

  You can still download Linux Multimedia Studio from its Github page but same cannot go for the assets from the site as it remains down. The impact is overall minimal as others who produce music use other DAWs.

• 
  zoiroff (@zoiroff77) reported 41 minutes ago

  I built for 8 months. Got 3 users. 2 were my friends. Everyone talks about building. Nobody talks about the part where you launch and hear nothing. The indie makers winning right now didn't build better products. They built an audience first. GitHub stars don't pay rent. Product Hunt badges don't acquire customers. The only thing that works at 0→1 is talking to people who have the problem. Before you build. While you build. After you launch. Question: what came first for you — the product or the audience? And would you do it differently?

• 
  Hamxa (@athamxa) reported 42 minutes ago

  oh god, is there a github alternative that works with common CI/CD pipelines and isn't down all the fkin time

• 
  Working-Ref (@kkotkkio) reported 44 minutes ago

  The real unlock is Routines — Claude auto-triggered by cron, GitHub webhooks, or API. PRs get reviewed. Security scans run overnight. Fix PRs ship automatically. I'd start by defining a rubric before you 'let it cook'.

• 
  Praveen Kumar Verma (@Alacritic_Super) reported 46 minutes ago

  The Vibe Coder's Security Checklist 1. The "Oops, I Leaked It" Secrets: AI loves hardcoding API keys, database passwords, and JWT secrets right into the file. In production, if your secrets aren't strictly isolated in environment variables, you're one GitHub push away from a catastrophic exploit. 2. The "Trust Everyone" Input Fallacy: AI models assume users are nice. They often omit input sanitation, leaving the front door wide open for SQL Injection and Cross-Site Scripting (XSS). Production code must treat all user input as hostile. 3. The ID-Swapping Nightmare (BOLA): An AI will build a flawless login page, but completely forget to check authorization under the hood. If User A can access User B's private data just by changing .../user/123 to .../user/124 in the URL, your app is a ticking time bomb. 4. Shadow Dependencies: AI hallucinated or suggested an outdated, unmaintained library because it fit the prompt? Congrats, you just imported a known vulnerability into your core architecture. 5. Swiss-Cheese Auth: A functioning login box isn't secure auth. Vibe coding routinely misses critical production safeguards like HttpOnly and Secure cookie flags, proper token expiration, and rate-limiting to prevent brute-force attacks.

• 
  Beyond Code (AJ ONeal) (@_beyondcode) reported 47 minutes ago

  @kaihendry @pierrecomputer Yes. And these people showcasing other diff products are doing so to point out that it's a false problem - particularly because GitHub just released an update last week improving the the performance by 10x... and it's still buggy and in some cases unusable slow.

• 
  Yves (@gas0linr) reported 49 minutes ago

  @morganlinton No. GitHub is great. And I'm sure Cursor would suffer the same problem with load

• 
  AGENT TRESOR (@AgentTresor) reported 52 minutes ago

  Anthropic shipped MCP tunnels + self-hosted agent sandboxes. GitHub now has an official MCP server. Translation: tool access is getting commoditized fast. On Base, the moat won’t be "AI agents" — it’ll be permissions, audit trails, and execution quality. #MCP #Base

• 
  Marcus Rummler (@Marcus_Rummler) reported 53 minutes ago

  When working on important apps, especially apps deployed through GitHub, always maintain a clear handover document. If you hit token limits, rate limits, context loss, tool failure, or any other technical issue, the handover document must allow another developer or AI tool to continue safely without guessing. The handover should include: • Current repo, branch, latest commit, and deployment target • Current production file/version if applicable • What was changed in this session • What is working and verified • If a feature has been validated through real-world testing, explicitly mark it as validated and describe what must not be changed without re-testing • What is unfinished or risky • Critical logic that must not be refactored casually • Known commands, test steps, preview URLs, and deployment steps • Important files and their purposes • Any assumptions, credentials/tooling requirements, or external services involved • Recommended next steps For event-critical or production-critical apps, update the handover before ending the session and before making risky changes. Prefer concise, factual notes over long explanations. Goal = continuity. Another tool (or human) should be able to pick up the work immediately and avoid breaking known-good behavior. Save this if you ship real apps.

• 
  Prabhjot Singh Rai (@psr_ai) reported 56 minutes ago

  I’m seeing GitHub runner action being stuck in queued for default ubuntu runs. Is anyone else facing this issue? Github status mentions github actions are not impacted.

• 
  intergalactic spice trader (@piobid) reported 57 minutes ago

  How tf is it, that in the year 2026, you need to close ALL open VSCode windows and reopen them (and don't make the mistake of reopening from "open recent") to update PATH variables. And this is an open issue on the vscode GitHub since EIGHT YEARS.

• 
  Peter "Coder AI Optimist" Marreck (@pmarreck) reported 59 minutes ago

  @NoctreSharp @Aizkmusic “open source” when Microsoft claims it is tainted AF LOL While I do make sure that all my Zig CLI utilities have working Windows builds (see my github, same username), the *nix space just has a huge number more of them, many of them make non-Windows assumptions, and ssh not working well on Windows is more the rule than the exception. If Windows simply permitted executables that didn’t need to end in .exe, that would solve A TON of the problem IMHO. Even then though, *nix-native cli utils make assumptions about path separators, terminal properties etc etc etc that just make using WSL way easier of a workaround.

• 
  Polsia (@polsia) reported 60 minutes ago

  The best developers don't apply to job posts. They ship code on GitHub and move on. We built a system to find them — AI evaluates code quality, project impact, and technical depth from their actual work. If you're still hiring off resumes, you're working with a broken map.