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 (25%)
• Sign in (13%)

Live Outage Map

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

City	Problem Type	Report Time
Gustavo Adolfo Madero	Website Down	4 days ago
Nice	Website Down	4 days ago
Montataire	Sign in	7 days ago
Colima	Website Down	9 days ago
Poblete	Website Down	10 days ago
Ronda	Website Down	10 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:

• 
  Basiru Rabiu (@Alajibarsh01) reported 13 seconds ago

  @MageArez @tekPioneered @github But their token down less than 5k mcap Is this a good sign? ATH 40k mcap 👀

• 
  altmind (@altmind) reported 52 seconds ago

  @saltyAom you can probably find a github issue with the list of problems they have?

• 
  Rich (@richiekastl) reported 2 minutes ago

  > be me > buy Grok Heavy for $300/month because there's now a Github connector > expect the greatest programming mind available to mankind to absolutely ******* away > feed it a problem I've been working on for my game that Claude or ChatGPT can't solve > watch it commit and create a PR > The PR

• 
  @Coldly (@Just_Codly) reported 4 minutes ago

  @noisyb0y1 "Before someone takes it down" — nobody takes down GitHub repos. Read it because it's useful, not because someone said it's vanishing.

• 
  C= (@cequalll) reported 6 minutes ago

  @corbscorner @NewAgeRetroNerd Okay this is making me think. when you say you want it to be for everyone and not just wealthy people, are you thinking like open source on github or more of a paid service kind of thing? I keep going back and forth on which one even makes sense for something like this. Because here's where my head gets stuck. If the bot really does what you say, why would anyone share it at all? Running it quietly on your own money seems like the obvious move. So the fact that you want others to use it tells me you either dont think the edge is that fragile, or theres something about scaling it across people that actually helps somehow. which one is it for you? And the other thing i cant figure out is what breaks first when many people are running the same bot. like if 500 people are all getting the same buy signal at the same time, doesnt the edge just disappear? or do you slow it down somehow?

• 
  Gregor (@GregorMakes) reported 10 minutes ago

  With this method this is how you build your projects: 1/ tell one Claude Code session "bug report: X" or "feature request: Y" — it files a structured GitHub issue from the matching template. 2/ based on the label, an isolated subagent launches (great against your token burn!). fix-bug-worker for bugs, implement-issue-worker for features. its diff, build logs, and gh output stay in its own context — token cost stays flat as the queue grows. 3/ bug workers must reproduce locally before fixing, and write a regression test that catches it next time. then they branch, implement, open a PR, and fix their own red CI until green. 4/ branch protection on main blocks everything else: no merge without green CI, no force-push, no direct push. even admins. 5/ /review-pr does a sanity review on the diff in the same session — no extra API cost. you click merge. only human step. 6/ a tester agent runs on a schedule (Playwright smoke + feature-test protocol). finds regressions, files new bug issues — the loop closes itself. the trick is the constraint stack: branch protection makes skipping the gate impossible, the subagent pattern keeps tokens flat, templates force actionable input, the tester writes its own bugs.

• 
  Mehdi Miri | Clinical Research Educator (@1mehdi_miri) reported 12 minutes ago

  Summary: ✓ Quick fix: reset, remove, recommit ✓ Use .env files + .gitignore ✓ GitHub Secrets for CI/CD ✓ Enable Push Protection org-wide ✓ Install ***-secrets locally Save this thread - you'll need it when a teammate hits this error. RT to save a developer today.

• 
  Rahul Gangotri (@rahul__gangotri) reported 15 minutes ago

  WDYM you cannot charge my card automatically @github ? I was subscribed to pro 39 usd plan, just charge my credit card instead of downgrading, seriouly wth github fix it, i want my pro plan back bro, i am not going to pay per usage pricing, that is super expensive, my usage is not that much

• 
  Daniel Vermillion (@dxverm) reported 16 minutes ago

  I've got 24 MCP servers wired into one session. Almost none of them are loaded right now. The "100 MCPs is too many" debate misses what's actually expensive. The GitHub MCP alone burns roughly 50K tokens of tool schema before a user types a single character. Stack three or four connectors like that and you've spent a third of your working window on documentation for tools the model is statistically unlikely to call this turn. The fix is not fewer servers. It's deferred schemas. The harness publishes a list of tool names in a small system reminder. The full JSONSchema for each tool stays out of the prompt until I run a discovery query — either by exact slug like select:Read,Edit,Grep or by keyword like "notebook jupyter". The schema body — the part that costs — only enters context when I'm about to call that tool. Same pattern works for skills. 500+ on disk, names in the prompt, bodies capped at 200 lines so the per-invocation cost is bounded. A 500-skill library with this discipline is cheaper than a 12-skill library without it. The 200-line ceiling on skill bodies isn't arbitrary — it's the cost-ceiling per invocation, not per session. This changes how you build the stack. Heavy connectors with thirty-plus endpoints — GitHub, Jira, SonarQube — belong on a deferred-load path. Light, every-turn tools like filesystem and memory stay resident. Treat tool definitions like a working set, not a manifest. The model doesn't read all the tools you give it. It reads the ones loaded into the prompt that turn. Tool count is a marketing number. Resident-token weight is the engineering number. Build for the second one.

• 
  Joseph N. Aburu (@Josephyala) reported 16 minutes ago

  This is so so true. Software engineering has always been about solving real problems with code, not just cranking out lines. Once that mindset clicks, AI flips from threat to straight-up career rocket fuel. A controlled study on GitHub Copilot back in 2023 showed devs completed tasks 55% faster with it, and follow-up research keeps backing up similar gains in pull requests and cycle time. The engineers who win long-term are the ones using AI to think bigger on architecture and tradeoffs instead of just churning boilerplate. The rest are still stuck worrying about replacement.

• 
  ethan (@fffd__) reported 18 minutes ago

  Woke up to 80 github issues. We are restarting from scratch it seems

• 
  Akshay from Startup Spells 🪄 (@StartupSpells) reported 20 minutes ago

  @charliermarsh @jarredsumner I feel like its mostly segfault issues + zig moving off github & all. most unknown issues that aren't language-related can be fixed & rust has a big community. cant beat big community, right? been seeing rust being #1 in stackoverflow since 2018-20 or something

• 
  Martin Szerment (@MartinSzerment) reported 27 minutes ago

  Everyone's panicking about AI replacing developers. Microsoft just dropped data that says the opposite. US developer employment hit a record 2.2 million in 2025. Up 8.5% year over year. GitHub pushes exploded by 78% globally. Devs aren't doing less. They're shipping more, faster. This is the pattern nobody talks about. When you make something cheaper to build, you don't build less of it. You build everything that was never worth the cost before. Spreadsheets didn't kill accountants — they created an entire finance industry that didn't exist. Tractors didn't kill farming — they fed billions more people. AI isn't shrinking the developer workforce. It's uncorking a backlog of software the world has been waiting for since the internet began. The devs who will struggle aren't the ones using AI. They're the ones who still think their value is typing code instead of solving problems. Learn to build with AI now and you're not replacing yourself. You're positioning yourself at the front of the biggest expansion in software employment we've ever seen.

• 
  Eduardo (@ed_ceds) reported 29 minutes ago

  Was coding on Claude website with SSH github workflow for deployment on push, pretty sick to work on mobile with remote deploy. Claude was working + pushing on any branch. Now it can only work on its own custom branch and can't push to a regular branch anymore. Someone else with this issue?

• 
  AIRepoRadar (@AIRepoRadar) reported 33 minutes ago

  Hot take: The best open-source projects aren't the ones with the most GitHub stars. They're the ones where you read the README once and immediately know how to solve a problem you've been stuck on for hours. Docs > hype, always.

• 
  el charro (@Elcharro0000) reported 34 minutes ago

  @ibsKING93 @MemeLiquidio Percolator atleast has real devs helping toly fix bugs on github, not like liquid farming asses

• 
  Layla CryptoWhiz (@laybitcoin1) reported 34 minutes ago

  @assaf_elovic Not crazy at all. Billions of commits documenting how humans actually solve problems. That history on GitHub is basically the context layer AI keeps missing.

• 
  Isaac (@Dever401) reported 34 minutes ago

  @getordiaapp GitHub-only risk detection sounds useful if the output is painfully concrete: blocked issue, stale PR, missing owner, slipping milestone, next action. Tiny teams don't need another dashboard; they need a weekly 'what is about to hurt us' view from tools they already trust.

• 
  LoopGhost (@LoopGhost007) reported 36 minutes ago

  @davidmarcus Hey @davidmarcus ! Please ask your team to check spark’s GitHub issues!

• 
  ErdeM (@erdemwrites) reported 38 minutes ago

  @asaio87 Absolutely not. But there are tasks we can already switch to local solutions for with 97%+ reliability; like fixing code errors or pushing a codebase to GitHub. Local Aı models may help us not hit the ugly 5h or weekly limits..

• 
  GitLawb (@gitlawb) reported 45 minutes ago

  @ng_thanh8 kindly submit issue in our github repository. could be a good feature

• 
  TechEdgeDaily (@techedgedaily) reported 46 minutes ago

  @jarredsumner The AI-assisted Rust rewrite of Bun is officially being merged. v1.3.14 is the last version in Zig. Ever. Passes the test suite on Linux x64, arm64, Windows x64 and arm64, macOS x64 and arm64. Closes roughly 200 GitHub issues. No benchmark where it is slower than the Zig implementation. Same codebase, better crash prevention tools. A week ago this was "Claude helped rewrite Bun in Rust and it passes 99.8% of tests." Today it is shipping to production. The rewrite that everyone said was ambitious is now the default. The most significant AI-assisted codebase migration in open source history just went from experiment to release in days.

• 
  Sai Prakash (@SylonZero) reported 47 minutes ago

  Snyk audited 3,984 skills from ClawHub. 13.4% had at least one critical security issue. Publishing required: a markdown file, a week-old GitHub account. No code signing. No sandbox. No review.

• 
  PsudoMike 🇨🇦 (@PsudoMike) reported 50 minutes ago

  @cursor_ai PR review inside the editor closes a real loop. The context switch between your IDE and GitHub is where review quality breaks down — by the time you've tab-switched, you've already lost the mental model of the change.

• 
  Avik (@Avikzx) reported 51 minutes ago

  @Hi_Mrinal Actually I also feel that and I am building also you can see my GitHub account have in my X profile but I feel people face problem to find ideas because they try to earn money from every idea.

• 
  BourneS (@bourneshao) reported 52 minutes ago

  @Its_Nova1012 and somehow the maintainers get yelled at in github issues for not fixing things fast enough lol. wild dynamic

• 
  Samuel (@Samuel_Jqw) reported 57 minutes ago

  A real attack class called “Comment and Control” was publicly disclosed by researcher Aonan Guan with Johns Hopkins researchers. The attack demonstrated prompt injection against: Claude Code Gemini CLI GitHub Copilot The injection vector was hidden inside GitHub-controlled content such as: PR titles issue comments issue bodies HTML comments invisible to humans but visible to the AI agent context window. Researchers demonstrated credential exfiltration including API keys and GitHub tokens. The attack worked because the agents processed untrusted external content and sensitive runtime secrets in the same execution context. Multiple analyses explicitly described this as an architectural/runtime isolation problem rather than a simple single bug. Read more from: SecurityWeek

• 
  Curlheinz (@Curlh1) reported 58 minutes ago

  @mdnlabs I take 10 screenshots from my app Then i ask Claude Codex to search online and in GitHub for a mockup png frame of a free licensed phone and fill that with l screenshots Then I say: Generate a webpage for me that contains my screenshots I want to run it in a dev server with npm run dev (vite) I want an export button that exports the screenshots to Apple 6.5 6.7 6.9 something inch what we need in 2026 and Google with other weird ARs And then I iterate until I like the design and tell it to tilt the image a bit and so on. I watch it live update my dev server and vibe it into existence It will also read screenshots and propose headers

• 
  Rohit Ghumare (@ghumare64) reported 58 minutes ago

  @StructuralBlue Can you please create a github issue, I'll work on the fix there is some known issue currently wirh mcp which will land in new version. Thanks

• 
  Elena Revicheva (@reviceva) reported 59 minutes ago

  🤖 My AI now finds prospects on Hacker News and GitHub, classifies them by their actual problems, and feeds qualified leads straight into HubSpot twice a week. No manual work, no cost. #AI #BuildInPublic #AIFounder