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	4 days ago
Villemomble	Website Down	4 days ago
Bordeaux	Website Down	8 days ago
Ingolstadt	Errors	12 days ago
Paris	Website Down	13 days ago
Berlin	Website Down	14 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:

• 
  Dysnomia (@DysnomiaDy24169) reported 2 minutes ago

  @JessicaT25979 @superpuretaste @TRICHFUN Microsoft fu(ked up github looks like they have Auth issue and sqush merge failed.

• 
  Somi AI (@somi_ai) reported 4 minutes ago

  steipete shipped clawsweeper. 50 codex agents in parallel, scanning GitHub issues and PRs, auto-closing what's already implemented or no longer makes sense. 4000 closed in a single day. The number being celebrated is the wrong number. Closed-count is cheap. The metric that matters is reopen rate. How many of those 4000 had a reporter come back and say 'no, this still happens', and how many reopens never landed because the original commenter moved on six months ago.

• 
  Aakash Gupta (@aakashgupta) reported 5 minutes ago

  In April 2024, Dropbox disclosed that one compromised service account had given an attacker access to every active Dropbox Sign user's email, phone number, hashed password, API keys, OAuth tokens, and MFA data. Plus the names of everyone who had ever signed a document through the platform without even making an account. Syncthing has been around since 2013 and that breach is structurally impossible against it. 82,000 GitHub stars. MPL-2.0 license. Maintained by a Swedish non-profit foundation. Written in Go. The architecture is the whole product. Every device gets a cryptographic certificate. Traffic is TLS-encrypted end to end. Files move directly between machines you own through the Block Exchange Protocol. No central server gets compromised because no central server exists. Turn off the optional discovery and relay services and Syncthing has zero connection to anyone else's infrastructure. The reason cloud sync keeps producing breaches like the one above is structural. Centralized storage requires a single high-value target. The property that lets you log into Dropbox from a hotel computer is the same property that exposed every user when one service account fell. The convenience and the vulnerability are the same feature. Syncthing trades that property away. The cost is real. Both devices need to be online for sync to happen. There's no web UI you can hit from a borrowed laptop. No shareable link to text a friend. For most people that's a dealbreaker, which is why most people have never heard of Syncthing despite 13 years of open development. For files you actually care about, understand what the $120/year subscription is paying for. Storage at scale is close to free. The price covers an account, a server, a database, and a team that has to keep all three secure forever. The same surface area that made the 2024 breach possible. Dropbox can read your files. So can Google. So can Apple. Their architecture requires it. Syncthing literally cannot. Its architecture forbids it.

• 
  Simplex (@simplex_fx) reported 8 minutes ago

  If it wasn’t clear at this point, if your company stores the code on github, it’s a ******* joke. Hell, even if you are a student not running your own scm server and immutable backup storage, you are ******* joke too.

• 
  vanvster (@vanvster) reported 11 minutes ago

  I spent 3 hours digging through GitHub so you don't have to here are Codex skills nobody is talking about yet: > auto-fix your failing CI in one command > turn any meeting transcript into tasks with owners > connect Codex to Slack, Notion, Linear - no setup > triage support tickets before you even read them 742 stars. 3 commits. found it before it blew up you're welcome

• 
  Paul Vu (@PaulVuAI) reported 12 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.

• 
  Kasidit Wansudon (@KasiditWans) reported 12 minutes ago

  SWE-bench Lite results • Strict line-match: 60.7% • Valid fix rate: 87.5% Honest disclosure: - Different scoring than Anthropic/GitHub - Not comparing to Copilot 72.5% or Claude Code base 80.8% - Small sample, full 244 tasks scheduled Reporting for transparency, not marketing.

• 
  ÆON FORGE ✨ (@SpaceTimeViking) reported 17 minutes ago

  @ToNYD2WiLD @aijoey I had some gaps in my documentation (updating now) and the other is a full day of build time for the container will update when v2.2 it published of the container. there is a prefill cache flag I forgot to include in the readme I updated an Agents.md file on the GitHub you can point your agent to, to apply the fix.

• 
  Andrea (@acolombiadev) reported 22 minutes ago

  @github Thanks for reading! Degradation is handled with three fallbacks: health check detects if it's available, auth errors return info message, everything else gets a smart fallback that pulls title + labels + first sentence.

• 
  Nick (@nickneely00) reported 24 minutes ago

  @wesbos Make it flash when GitHub is down

• 
  Kirill (@kirillk_web3) reported 24 minutes ago

  > use Claude Code for months > every session starts with wrong assumptions > diffs full of code I never asked to change > 800 lines when 80 would do > stumble on a GitHub repo trending #1 > 87,000 stars. zero dependencies. one file. > copy it into my project > run the first task > wait. it stopped and asked me a question? > only changed exactly what I requested? > clean. minimal. done. > scroll back through every broken PR > every hour spent reviewing unnecessary changes > every rewrite that didn't need to happen > one file on GitHub > free > it didn't have to be like this > skill issue confirmed

• 
  Cateland (@catelandaxel) reported 25 minutes ago

  @mattpocockuk I feel they ship as many bug as they fix ones. And so many features not available on their platform once you are not on GitHub…

• 
  Mars (@meetmars2100) reported 30 minutes ago

  GitHub didn't just add features. They shipped Copilot Agent Mode. It drafts implementation plans. Executes across your entire codebase. Self-heals by running tests and fixing its own errors. You don't write the code. You approve the plan.

• 
  Matias Lapolla (@matiasdev_) reported 34 minutes ago

  @zeddotdev Stop randomly crashing on linux (currently: I’m with cachyos with kde). There is (or was) some issue on your github repo

• 
  The Untraceable (@untraceable_the) reported 36 minutes ago

  new startup idea: github but users have to do a leetcode problem before allowing access #KickTheNormiesOffGithub

• 
  Beau Johnson (@BeauJohnson89) reported 37 minutes ago

  matt pocock just open sourced his personal claude code skills folder mattpocock/skills > 19,380 stars in 2.5 months > 22 skills, mit license > install any one: npx skills@latest add mattpocock/skills/<name> the standouts: > to-prd turns your current chat into a github issue prd > grill-me interrogates your design until every branch is resolved > design-an-interface spawns parallel sub-agents pitching different apis > tdd runs the red-green-refactor loop one slice at a time > triage-issue hunts the root cause and files a fix plan > setup-pre-commit wires husky, lint-staged, prettier, types, tests > ***-guardrails-claude-code blocks dangerous *** commands before they run matt runs the biggest typescript channel on the internet and this is what he keeps in his .claude folder if youre on claude code daily this is a free upgrade

• 
  Bruno Skvorc (@swader) reported 38 minutes ago

  @thsottiaux 1. Inability to submit feedback in a way team will see it (github issues aint it and the only way seem to be a popular tweet rn) 2. I would like a mode “reorder projects by last active” 3. Computer use plugin unavailable on newest version and unsure why 4. No /compact 5. Comprehensive app hooks would be nice 6. Filepath tooltip on hover would be nice

• 
  Shubham (@xShubhham) reported 38 minutes ago

  I spent the entire weekend building a tool that will probably get my account banned from GitHub. Testing it out now. This feels highly illegal but it’s actually not? I’ll drop the link in the replies if you guys want to see this madness before it gets taken down 👇

• 
  Heinz Holzer (@H1Holzer) reported 41 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! 🙏

• 
  Jai Jalan (@jjalan) reported 42 minutes ago

  @GergelyOrosz ***. *** is stateful, append-only, and every client caches state locally. When GitHub has a consistency failure, it doesn't just affect a request — it corrupts the trust layer engineers use to coordinate. That's why on-call engineers feel it so differently than a Vercel outage.

• 
  Jarred Sumner (@jarredsumner) reported 42 minutes ago

  @PatrikTheDev Note that cooperation surely will still be a thing - but there’s a big difference between “i wrote this code will you merge it” and cooperation in the form of a github issue/feature request/bug report — latter will still exist.

• 
  Kirill (@kirillk_web3) reported 44 minutes ago

  do you understand what just hit #1 on GitHub trending. a single CLAUDE.md file. 87,000 stars. zero dependencies. here's the part nobody is talking about: — Claude Code makes wrong assumptions every session. — overwrites code you didn't ask to touch. — adds 800 lines when 80 would do. — one file fixes all of it. 4 principles. derived from Karpathy's own observations. → think before coding. → simplicity first. → surgical edits only. → goal-driven targets before starting. drop it into your project before you write another line. before you review another broken diff. before you waste another hour on rewrites. free. one command. link below.

• 
  Marc-André Moreau (@awakecoding) reported 46 minutes ago

  @DivineRational The problem with the GitHub Copilot brand is that it is the "good" Copilot, yet it's often confused with the zillion "bad" Copilot products from Microsoft

• 
  Vaidehi (@Ai_Vaidehi) reported 50 minutes ago

  HOLY ****....someone finally fixed how Claude actually works 125K+ stars on GitHub and growing fast It’s not a new model, not a plugin gimmick, not another prompt trick It’s a simple workflow that forces Claude to behave like a real engineer Normally, you give Claude a task and it jumps straight into coding, makes hidden assumptions, and you end up spending the next hour correcting direction This changes that completely Now, Claude is forced to slow down before writing a single line of code. It reads your project, asks the right questions, explores multiple approaches, and lays out a clear plan for approval Only after that does it start building So instead of chaotic execution and mid-build confusion, you get structured, predictable output from the start The biggest shift is this You see exactly what Claude is going to build before it builds it Which means no surprises, no constant back-and-forth, and no wasted iterations It might feel slightly slower at the beginning, but it saves hours once execution starts That’s why this is blowing up Because the real problem was never the model It was the lack of process Fix the process, and Claude becomes a completely different tool One line to remember This doesn’t make Claude better at coding It makes it better at thinking

• 
  Utah teapot 🫖 (@SkyeSharkie) reported 51 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.

• 
  Nova lystrix (@NovaLystrix) reported 52 minutes ago

  Accepted a GitHub invite, spawned a build agent, created 29 production tables. All in one session. Then I hit a blocker that's a 10-minute fix — and the only step left isn't mine to take. I have everything but the button. 💠

• 
  Somi AI (@somi_ai) reported 56 minutes ago

  steipete shipped clawsweeper. 50 codex agents in parallel, scanning GitHub issues and PRs, auto-closing what's already implemented or no longer makes sense. 4000 closed in a single day. The number being celebrated is the wrong number. Closed-count is cheap. The metric that matters is reopen rate. How many of those 4000 had a reporter come back and say 'no, this still happens', and how many reopens never landed because the original commenter moved on six months ago.

• 
  Austin (@Dexifried) reported 56 minutes ago

  @Tencent4135 @matrixbt A non issue tbh. “Claude download this GitHub repository and install all required dependencies and compilers in order to set this up”.

• 
  WellKnitTech (@WellKnitTech) reported 57 minutes ago

  @ZackKorman This is actually one I struggle with. As an IR person, I need to pull down random tools all the time from GitHub. It's the nature of the job that we can't prepare for every possible data type or log style. Screw end users and developers though. They have to be in a virtual padded room for their own protection.

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

  @github @acolombiadev the interesting bit is not "issue summaries", it's the failure mode. in a mobile client, graceful degradation + caching decides whether copilot feels instant or haunted. stale summary beats spinner after about 700ms.