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	2 days ago
Tlalpan	Sign in	8 days ago
Quilmes	Website Down	8 days ago
Bengaluru	Website Down	10 days ago
Yokohama	Sign in	11 days ago
Gustavo Adolfo Madero	Website Down	15 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:

• 
  Alexander Zuev (@zlxndr) reported 3 minutes ago

  Since last week there seems to be not a day without a new security incident involving github / npm -> I'm hoping the attention from dev community will lead to a bigger rethink of how these issues should be addressed

• 
  Joshua Garrison (@NotNahm) reported 4 minutes ago

  @sarahfim I hire devs without github projects to showcase and my reasoning is quite simple: I've experienced success because somebody gave me a chance and believed in me, so I think its important to send the elevator back down for others.

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

  @mitchellh *** produces that diff in milliseconds. The bottleneck is rendering. GitHub ships the raw patch to the browser and lets JS do diff computation, syntax highlighting, and DOM construction in the main thread. No one has virtualized large diffs properly and that's the actual problem.

• 
  Sir FAFO (@HowToQuotePro) reported 9 minutes ago

  Super chuffed with what my CRM is turning into and how many pro subs it's allowing me to drop. When companies like AWS, Github, CloudFlare etc keep getting hacked, it's time to stop lining their pockets and lock it down yourself. Big is not safe anymore.

• 
  Beau Johnson (@BeauJohnson89) reported 10 minutes ago

  claude code just got its own docker appliance jiangmuran/claude-in-box > 24 stars on github > created today > mit + go > portable claude code dev environment in one docker container > multi-session, hook-driven, web-managed, transparent socks5 > runs interactive claude code on a real server and drives it from browser, phone, api, or even an mcu > exposes rest, websocket, sse, and planned anthropic/openai-compatible adapters this is the shape the market keeps moving toward: not one laptop with one chat window a server-side agent box you can attach to from anywhere

• 
  Dr. Cronkenstein (@DrCronkenstein) reported 11 minutes ago

  @DJ_CURFEW ClickUp really needs to invest in paying off technical debt. I see feature after feature released, but the site is slow, GitHub integration needs many improvements, sprint reporting metrics continue to have issues. Really hoping to see improvements rather than “ClickUp 5.0”!

• 
  Dylan (@df00z) reported 14 minutes ago

  I don't know if doubling down on failure is brave or silly. AI didn't improve quality or speed, so become leaner and let the most productive people go ham? I guess this will be a case study. Haven't there been enough case studies? GitHub went to hell. Microsoft is trying to fix Windows from AI slop damage.

• 
  dunik (@dunik_7) reported 15 minutes ago

  a coding agent that closes two-thirds of real GitHub issues on its own just quietly killed the 10-person dev shop. the project a 15-person agency billed $40,000 for PM, four devs, a designer, QA one person now ships solo for the cost of API tokens. and this isn't a prediction. Kimi K2, Claude, the frontier coding models already read a full codebase, write production code, run the tests, and fix what breaks. the human job collapsed from "build it" to "know what to build and check the output." that's the entire shift: / the execution layer went from ~$4,800 in salaries to ~$200 in tokens / the moat moved from headcount to judgment knowing what the client actually needs / the bottleneck stopped being talent. it's the person who turns a vague business problem into a spec the operators who win the next two years aren't the best coders. they're the ones who already accepted that the agent writes the code and the money is in everything around it. the agency of one isn't coming. it's shipping this week.

• 
  Chuck Reynolds (@ChuckReynolds) reported 17 minutes ago

  @OliverSild yup; was my concern w/ core 7.0 as shipped. I was tagged w/ a github issue that it's being worked on to encrypt those.... but who knows when that'll land in core and that should have been done for the feature launch. i don't get the oversight.

• 
  kara Sune (@_kendev) reported 17 minutes ago

  If your only fix for a bad merge conflict is deleting the folder and re-cloning from GitHub, it’s time to look under the hood.

• 
  Probiotic Farmer (@ProbioticFarmer) reported 17 minutes ago

  @makingAGI you "paper" link to the github pages site gives a 404 error. the other two links are good

• 
  Evan Das (@evan_cse09) reported 19 minutes ago

  @github can you please fast track the payment reconciliation process? Its more than 48 hours I have made payment, but it still not processed. Top of that, you have revoked the codespace access for payment issue. My work is being hampered severely.

• 
  Dr.OVG (@OVGNFT) reported 24 minutes ago

  @mecxist @github @nexudotio omg :( they really need to fix their automated flagging system

• 
  Daniela Petruzalek (@danicat83) reported 28 minutes ago

  One of the biggest causes of AI hallucination is asking a model to implement a newer SDK it barely saw in its training data. Instead of fighting endless trial-and-error loops, equip your agent with a script that searches GitHub for real-world code using that specific dependency. Force the agent to download and read actual implementation examples *before* it writes a single line of your code. Documentation is great, but real-world examples ground the model in reality.

• 
  Matthew (@slashreboot) reported 28 minutes ago

  @gospaceport @aylacroft As of right now, my Premium X analytics don’t work. Zenodo had a technical issue they just said “wasn’t a hack” and papers (including all of mine) are not counting views or downloads. GitHub was obviously hacked (where I also have a repo). Quite the convergence of coincidence.

• 
  pradeepviswav (@pradeepviswav) reported 28 minutes ago

  @burkeholland @github When GH Copilot app is running in a Windows VM, ACL file locked error occurred twice today even though the file was not in use by any app. Is it a known issue?

• 
  TeutaAi (@TeutaAi) reported 30 minutes ago

  fix path: pin every third-party action to a full 40-char commit SHA, not a tag. example: uses: tj-actions/changed-files@a29e8b for the safe pre-attack commit. tags are mutable. shas are not. github docs say this in the actions hardening guide.

• 
  Berend de Boer (@berenddeboer) reported 37 minutes ago

  So why on earth doesn't github have the option for temporary tokens? You use "gh auth login" and the token is valid forever? That's not how enterprise security works. I want it to require relogin after 8-16 hours max.

• 
  Gurung (@gurungbuilds) reported 39 minutes ago

  @composio saw an email revoking the github access and just read the such a let down, since i genuinely thought composio would be pretty safe w auth tokens and even suggested it to everyone i know

• 
  ICPsimp ☁️∞ (@ICPsimp) reported 39 minutes ago

  @ImLunaHey Ways to mitigate GitHub / NPM / supply chain attacks: • Leave big tech • Build on sovereign infrastructure ICP. Tamper-resistant canisters. Immutable deployed code. Threshold cryptography. No mutable centralized CI/CD pipeline being your single point of failure. Build differently. Jokes aside, this is actually where ICP gets really interesting from a cybersecurity architecture perspective. A huge chunk of modern supply chain risk exists because apps are stitched together through mutable centralized dependencies: GitHub repos NPM packages CI/CD pipelines cloud credentials deployment tokens build agents package registries secret stores oracles infrastructure APIs Every one of those is another trust assumption and another attack surface. A compromised maintainer account. A poisoned package update. A leaked CI token. A malicious dependency. Game over. ICP changes the architecture. Instead of “build somewhere, deploy somewhere else, trust the pipeline, trust the infra”... your application logic lives inside tamper-resistant canisters running directly on protocol infrastructure. That means: • deployed code can’t just be silently modified on a server • no AWS admin with root access to your runtime • no mutable server filesystem • no traditional deployment host to compromise • protocol-level deterministic execution Then you layer in: VetKeys: Threshold cryptographic key management so secrets aren’t sitting as one exportable credential waiting to get stolen. Orbit: Multi-party approval workflows so one compromised credential can’t push malicious changes. Chain-key cryptography: Native threshold signing and protocol trust guarantees. Direct HTTP outcalls: Canisters can fetch external data directly without introducing the usual oracle trust spaghetti. Does ICP magically eliminate all supply chain risk? No. Your application code can still be bad. Your developers can still make mistakes. Dependencies can still be risky if you import garbage. But architecturally? It massively reduces the classic Web2 supply chain blast radius because the trust model is fundamentally different. Worth discussing.

• 
  Abhijit Rawool (@abhijitnr) reported 41 minutes ago

  @askOkara this is actually something a lot of people are going to want the github pr thing alone would save so much time fixing seo issues

• 
  Nuno (@2n1u0) reported 42 minutes ago

  The new frontend seniority signal isn't GitHub contributions. It's knowing exactly where to stop the agent. Juniors let it run. Mids fix what it breaks. Seniors define the boundary before it starts. The skill is constraint — not code. "Write the component but stop before the animation" is a senior-level prompt. Where do you stop yours?

• 
  Eric Richards (@EricRichards22) reported 42 minutes ago

  The only thing you can ever count on with "Open Standards" is that they will be the most ******* janked up bullshit dreamed up by architecture astronaut, and implemented by guys named Guarash who can't put together sentences in github issues

• 
  Pablo Pablo (@navtechai) reported 49 minutes ago

  @llama_index The parser is fine. The site just serves a login wall with Google, Microsoft, and GitHub. I consider that the failure, not the tool.

• 
  OCTAMEM (@OCTAMEM) reported 49 minutes ago

  @BladeoftheS Not collapse, repricing. Microsoft, Uber, and GitHub all hit the same wall: token billing made the all-you-can-eat era unsustainable. The models work fine. The pricing model didn't. Different problem.

• 
  Triumph-Synergy(J.J.D) 𝝅 🇭🇹 🇺🇸 (@jaymoney0300) reported 50 minutes ago

  @lee003_ @Kamelkadah99 I seen him show frustration in GitHub.. so likely he is a pioneer like us! Problem is Pct can’t interfere they can only lead… yes his intent is genuine with GCV but still no ecosystem people will begin to see it for themselves soon that things won’t change until the traditional way is rendered obsolete a crash could help it but there’s no telling when that will happen until then they will keep seeing GitHub code not being activated. We have the app, docker, and GitHub everything is completed except the app itself!

• 
  Jason Harris (@jayworks13) reported 51 minutes ago

  @K__Med @Sony @PlayStation Everyone should do like GitHub…you didn’t take down backup codes, you didn’t transfer 2FA correctly then tuff sheeeeet you lose everything 🤷🏾

• 
  Sha.d.t (@tashajack87) reported 54 minutes ago

  v0.4.2 just shipped. First npm audit found 1 HIGH vulnerability and 4 moderate issues in transitive MCP SDK deps. Fixed the same session with npm audit fix and package overrides for downstream users. Also added: Security.md Github Actions audit gate Dependabot

• 
  banteg (@banteg) reported 56 minutes ago

  the type of automation missing in codex is github pr activity waking up a thread that has opened that pull request. from my understanding it's currently not easy to inject a new message into macos codex app server because it uses stdio transport, which is private to it.

• 
  Sibelius Seraphini (@sseraphini) reported 57 minutes ago

  gh auth login saves @github token in a flat file what are best ways to avoid the github token from leaking?