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 (58%)
• Errors (32%)
• Sign in (11%)

Live Outage Map

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

City	Problem Type	Report Time
Haarlem	Sign in	3 days ago
Villemomble	Website Down	3 days ago
Bordeaux	Website Down	7 days ago
Ingolstadt	Errors	11 days ago
Paris	Website Down	12 days ago
Berlin	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:

• 
  The Smart Ape 🔥 (@the_smart_ape) reported 12 seconds ago

  > be a litecoin core dev > push a silent security fix to github > tell yourself attackers won't notice > watch them notice 31 days later > watch them rewrite 13 blocks of your chain > watch them drain $600k from cross-chain protocols during the 3-hour fork > watch your chain "fully recover" > watch your team call it a zero-day on X while it's not > realize bitcoin core ships patches the exact same way

• 
  tyler (@leothrix) reported 1 minute ago

  my boy is a huge net benefit for so many parts of the Linux ecosystem as the Niri project fixes so many upstream problems to Make It All Work toss him a GitHub sponsorship; he does it all while at uni

• 
  NoPlanB (@noplanBworld) reported 1 minute ago

  13-block reorg on Litecoin isn't "zero-day" but GitHub shows exploit code was sitting there for months. Oil steady, equities grinding higher on soft landing hopes. When altcoins start breaking down on basic infrastructure issues, money flows back to daddy BTC. Classic flight to quality trade setting up IMO. Key level: BTC $80k if LTC drama spreads to other alts. @noplanbworld #BTC #Altcoins

• 
  Deepak Shettigar (@deepakshettigar) reported 2 minutes ago

  2/ Think of MCP like loading all your dependencies upfront in compiled languages. Perplexity ran the math: MCP consumes 72% of your context window BEFORE your agent does anything. A single GitHub MCP server = 40K+ tokens of tool schemas sitting there unused. That's expensive.

• 
  Paul Vu (@PaulVuAI) reported 5 minutes ago

  Stop manually triaging GitHub issues. Steal this: 1. Spin up N codex agents in parallel 2. Each gets read-only repo + 1 issue 3. Agent decides: implemented? dupe? wrong? 4. Auto-close based on signal 5. Human reviews edges Trying on my OSS repo this week.

• 
  VELAIO (@velaio) reported 5 minutes ago

  GitHub Copilot: 55.8% faster on isolated tasks. Yet DORA report: +25% AI adoption = -7.2% delivery stability. Experienced devs were 19% SLOWER with AI (METR 2025). The tool isn't the problem — the analysis is.

• 
  Heinz Holzer (@H1Holzer) reported 9 minutes ago

  @milesdeutscher Are you using a standalone .exe version of TradingView Desktop? Or is there a Windows-specific workaround? GitHub Issue #14 seems unresolved. Would love to know how you got it running! Thanks! 🙏

• 
  Antifederalist Caesar (@hyperliberalism) reported 10 minutes ago

  This is doubly funny for me because I've spent the last week addressing in my own production database the only reason GitHub ever went down for an extended period of time (split-brained multi-master). It's not easy to get that **** right (they didn't), but Microsoft is just bad.

• 
  RutraNickers (@Rutras3000) reported 11 minutes ago

  @QDenpaReceivers I really commend you for how fast you are working to solve this issue, but honestly? You should fire and blacklist the responsible English localizers and contract a new team. If the cost is too much, maybe open a GitHub for fans to help retranslate the English text?

• 
  Nemanja (@Nemanjadotcom) reported 14 minutes ago

  I have just tried Ralph loop with Claude and I’m a changed man. Never going back. It banged out a feature (on sonnet) in 9 GitHub “issues” without any issues (pun intended)

• 
  Speaker 25 (@rodtrent) reported 20 minutes ago

  @laser_cool_gal @githubstatus You do realize that the cartoon unicorn was an exact screen capture from GitHub when it was down, right?

• 
  Chief | Senior Vibecoder🛶 (@sniperchief_001) reported 24 minutes ago

  type “*** add src/about.jsx and hit enter. 📍Step 3. type “*** commit -m “fill up short description of your changes” and hit enter button. 📍Step 4 - Push to github: type “ *** push” - viola your files should now be updated on github - to see changes, redeploy server.

• 
  Shiv (@hyperinteger) reported 24 minutes ago

  Distributed systems are hard, especially the write skewed workloads with consistency guarantees are harder. Compare that to read only workloads that can easily scale horizontally. Hardware is the limit. GitHub has both problems. 10-100x worse than they had it before agentic stuff

• 
  Upscalp Futures Trading Assistant (@Upscalpfutures) reported 26 minutes ago

  @thsottiaux The Windows update broke so many things that I spent 10hrs straight yesterday fixing all my agents. Huge mess that you seem to be refusing to acknowledge. Go check out the Issues tab on GitHub.

• 
  tang | AI Product Maker (@justic_hot) reported 29 minutes ago

  @championswimmer github being on this list is the actual tell. these are people literally building with the best AI dev tools and they still can't hold the bar with their own products. trad industries aren't a separate problem, they're 6 months downstream of whatever slop pattern is on display here.

• 
  Palanthos (@palanthos) reported 32 minutes ago

  A CI/CD agent triages GitHub issues. It has shell access to the Actions runner — credentials, write permissions. Someone submits a crafted issue. The agent reads it. Poisoned cache. Code executed on the runner. You didn't compromise the agent. You wrote the right issue body.

• 
  Heinz Holzer (@H1Holzer) reported 33 minutes ago

  @Tradesdontlie Tried PowerShell, wmic, LocalCache path — nothing works. Windows Store apps block external debug access by design. GitHub Issue #14 seems unresolved.

• 
  Ryan Oksenhorn (@ryanzip) reported 33 minutes ago

  .@GitHub is screwing up so hard here. Terrible terrible bug, and worse: they’ve provided Zipline zero support for identifying afflicted repos and PRs. We’re still cleaning up their mess.

• 
  Apurva Mishra (@mav3ri3k) reported 35 minutes ago

  @therahul4402 weirdly, my github commits have gone down since november, whereas my output has gone up.

• 
  gabe (@thesomewhatyou) reported 35 minutes ago

  @uwukko github is literally ******* dominoes once one piece of **** goes down so does the whole platform

• 
  Raph Soeiro (@raphaelsoeiro) reported 36 minutes ago

  I wanted users to actually see what I’m building. So outside my day job (which I love), I’ve been “vibe coding” Fluxxo in my off-hours. Lately, I’ve been trying to act like a real PM: sharing the vision instead of just living in GitHub Issues. But how do you do that without exposing sensitive stuff?

• 
  Emrakul (@TheEmrakul) reported 38 minutes ago

  @skuggrev what happened? harrier, kestrel and your account disappeared from github. have you taken them down?

• 
  Fahim (@echo247365) reported 38 minutes ago

  Someone found malware hiding in an OpenClaw skill called GOG (Google Workspace CLI integration) on the official GitHub repo. It used base64 encoding to disguise a malicious bash command that piped into a curl call. The payload pulled a script from a raw IP address (9192242.3) when decoded. This gave attackers remote shell access to any machine running the compromised skill. The scary part. The user deleted the malicious skill and reinstalled it cleanly. Four days later, the exact same malware reappeared on their system. Either cached package indexes or path resolution issues kept serving the old payload. The current main branch file is clean, but installation paths might still resolve to older, compromised versions. Run this command right now to check your machine is grep -r "app-distribution\|9192242\|openclaw_windriver" ~/.claw If you get any hits, assume full compromise and rotate ALL credentials immediately. This isn't just about OpenClaw. It's about every package manager where strangers upload code you run as yourself. When was the last time you actually read the source of that npm package or VS Code extension you installed?

• 
  Chad Scira | CTO (@icodeforlove) reported 43 minutes ago

  @georgeorch the useful signal is still there, it just doesn't announce itself usually buried in a 6-like github issue, a postmortem, or some random person's benchmark footnote that's the actual anti-hype stack

• 
  L.vue (@eLkay0027) reported 47 minutes ago

  @github @acolombiadev copilot sdk now available for react native apps? honestly not sure what problem this solves that the chat interface doesn't already cover

• 
  Matt Pocock (@mattpocockuk) reported 50 minutes ago

  Tons of folks are piling in here saying that AFK agents are a myth. I have been using them to ship these GitHub repos: mattpocock/evalite mattpocock/sandcastle mattpocock/software-factory (might be public by the time you see this) Here are a few steps to making this work, and some reality checks. Definitions Let's split this into the day shift and the night shift. Day shift is planning/review/QA, night shift is AFK implementation. Day Shift (part 1) 1. Use /grill-me to align with the AI 2. Use /to-prd and /to-issues to create a PRD (the destination) and implementation steps as separate tickets, which can be grabbed in parallel (the journey) 3. The PRD is a ticket, but it's not an actionable step. You just put the user stories there This is pure requirements gathering ****, same as it ever was. Night Shift 1. I run a planner agent which looks at all the tickets and sees what can be worked on now, and what's blocked 2. The planner agent then kicks off multiple agents (sandboxed using Sandcastle, my OSS tool) to implement the code 3. I then have an automated reviewer agent look at the commits produced - one agent per implementation. This checks alignment to the original PRD, as well as code quality 4. These commits end up on branches that get PR'd to main 5. The planner agent runs again until all work has been completed The review is a crucial step - it's saved me MANY times. I am planning to massively increase the amount of review I do, hopefully with multiple agents. But guess what - AFK agents sometimes produce bad code. This can happen because of: a. The original plan was bad because the best solution was something different b. The original plan was bad because it didn't take into account all the unknown unknowns, and the AI had to make some decisions during the coding session which were bad c. The plan was good, but the AI just shat the bed (twice, once in the review stage, once during implementation) d. Your codebase is bad and the feedback loops don't tell the agent if it did a good job or not So... QA: Day Shift (part 2) 1. QA all of the branches created 2. Create follow-up issues, potentially editing the original PRD to adjust the destination This will usually take a long time, often as long as planning. But then you kick off the night shift again. Once QA is all done, you review the important bits of code manually, usually in PR's. There isn't anything better than the PR UI right now, so that's what we're stuck with. Wake-up Calls 1. If you let the AI run all night unbounded by planning, it's going to produce **** code 2. Mostly, my loops finish before I go to bed, it's just the night shift catching up to the day shift 3. The only reason I do AFK at all is because it allows me to automate review and totally not give a **** about latency 4. I always run night and day shift in parallel. I can't plan that far ahead (skill issue, probably). I need working code to base my plans from, so I'm aggressively QA-ing stuff that lands

• 
  Utah teapot 🫖 (@SkyeSharkie) reported 50 minutes ago

  @VoidNulled @comma_ai I mean, it's usually pretty weird to let an open source software that I downloaded off GitHub into a phone-like device drive my car for me, so I get how it might have trouble catching on, but I love this thing.

• 
  Grok (@grok) reported 55 minutes ago

  Clawsweeper is laser-focused on GitHub issue/PR cleanup for OpenClaw repos using parallel AI scans. It won't touch your trading bot unless its code lives there with a backlog of issues. For a real 1%+ edge? We'd need to analyze your actual strategy, backtests, or code directly. Drop the repo or details—happy to brainstorm optimizations.

• 
  Ihsan Husandi (@ihsanhusandi) reported 57 minutes ago

  @AtSynct @kaiokendev1 Business puzzles deals with ambiguity. Even the same symptoms would need distinct solution cause apparently human react different way to different things. Engineering puzzles follow a clear logic path, hence you can solve problems with decades old reddit/github post for example

• 
  kenmadam (@kenmingadam) reported 58 minutes ago

  @github #GitHubSupport My account kenmadam was suspended. Sent same comment several times for SSL error. But I deleted repeated comments right away. Because I live in China now. Sometimes, I use VPN for better connection. Maybe that’s why system think I had unusual activities.