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 (61%)
• Errors (24%)
• Sign in (15%)

Live Outage Map

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

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

• 
  Camille World (@SuejungH) reported 3 minutes ago

  Andrej Karpathy’s CLAUDE.md. heard it gets a ton of stars on GitHub, but thought to myself — if it were really that essential, Claude would just have it built in by default — so I ignored it. But someone recommended it again. So I studied it. It turns out to be like: 1) Think before you code. 2) Code as simply as possible. 3) Only fix what you were told to fix. 4) Only do what you were asked to do….. obvious, basic things……… So I asked, do these obvious things really need to be spelled out? And apparently the answer is surprisingly yes — that it’s a limitation of the current model. How interesting. 🤔 Andrej Karpathy’s CLAUDE.md 요. 이거 깃헙에서 Star 를 엄청 받았다 그런 포스팅 보고, 속으로 그렇게 필수적이면 Claude 에서 기본으로 넣겠지 싶어서 그냥 무시하고 있었어요. 그런데 추천하신 것 보고, 공부해 보니까 1) 코딩하기 전에 생각해라. 2) 되도록 심플하게 코딩해라. 3. 하라고 한것만 고쳐라. 4. 하라고 한 일만 해라….. 이렇게 당연한 것들이네요……… 이렇게, 당연한 거 꼭 말로 해줘야 하냐고 물어 보니… 그게 지금 모델의 한계라고 말해줘야 한다고 하는군요. Funny indeed.

• 
  Ibrahim With I (@ibrahimwithi) reported 4 minutes ago

  github is down again!

• 
  Abhijay Rana (@abhijaymrana) reported 8 minutes ago

  seeing these comparisons a lot lately, but despite the hype i'm not really sold 1) swe-bench verified is a broken benchmark > super contaminated bc all tasks are just public github patches from issues/prs, so its all in distribution > the evals are poor, 59% of hard tasks fail bc of bad tests with false-positives/negatives or are extremely contrived. this makes them either flawed or unrealistic. 2) these scores are pretty cherry-picked & use a custom harness, not the standard public swe-bench harness. this is why the scores are unreproducible + not on official leaderboards. > opus 4.7 with custom harness scored 87.6%, over 14% more than the harness-optimized qwen. *this* is the truly fair comparison 3) infra costs are still exploding which is already pricing out some “frontier” open source models. > does china have enough capex for a frontier buildout? research talent is obviously not the problem but this may be the constraint > i wonder how much china govt will subsidize here, bc i'm unsure how these models will make money and break even. china is notoriously cutthroat but even then, some may eventually move to closed-source just to stay operational

• 
  Neko Witch Mawy 🪄 (@NekoWitchMary) reported 9 minutes ago

  @tekbog Gitlab is basically irrelevant at this point. Forgejo beats in every way. Plus forgejo uses github terminology (pull request, actions, etc), so it is much easier to switch to. Gitlab had a decade to fix ux, latency, resource requirements, but they blew it.

• 
  Kendall Chuang (@kendallchuang) reported 12 minutes ago

  Startup idea -- a native app for Github PR reviews. It should be able to easily render, and allow review and in-line comment threads on rendered Markdown files. With spec-driven development, being able to share and get peer review on markdown files is a key part of the developer workflow. Copy-pasting Markdown to Google Docs feels tedious and creates sync issues with the source-controlled Markdown, losing the comments when pasting back into the repo.

• 
  Matt Arderne 🌊 (@mattarderne) reported 12 minutes ago

  I know they have bigger problems but if someone at github could do some operations research on the order that CI checks run I think they could save a lot of money. Run the recently failed check first...?

• 
  Reelix (@Reelix) reported 13 minutes ago

  @banthisguy9349 @Payoneer You're trying to shut down the malicious North Korean payment providers, and I'm trying to shut down the malicious North Korean Github Repos :p

• 
  Glitch Truth (@glitchtruth) reported 15 minutes ago

  The Mitchell effect is real. Same thing happened with Ghostty, his terminal hit 25k GitHub stars in weeks before public release. When a respected builder vouches for indie tooling, distribution problem solved overnight. Bentley shipped Hunk solo and now every Zig dev on my timeline is installing it.

• 
  Iván (@seikv) reported 19 minutes ago

  GitLab only has to do the oposite of what GitHub is doing and make its UI prettier and boom all problems solved.

• 
  Yannick Comte (@cyannick) reported 21 minutes ago

  I'm not sure where the issues will be managed. Also maybe I could just push the code on github and deal with two origins. But I don't like Microsoft behavior on github... OR I can open my gitlab instance, but I'm not a big fan..

• 
  KagariSoft (@KagariSoft) reported 21 minutes ago

  Anecdotes from the development of ROL: Once, the game disappeared forever. Due to a problem with *** (version control software), upon executing a command, the entire project was completely deleted from the disk. Luckily, there were backups on GitHub, but of changes from 24 hours prior. Developer tip! Learn to use *** and GitHub, and keep your repository updated with every change!

• 
  Zohar Einy (@ZoharEiny) reported 24 minutes ago

  @xoofx I wonder if it's an issue of them connecting Copilot to MCPs. Problem is when you ask it a "simple" question like "who owns this service?" and it'll dig through GitHub, PagerDuty, Datadog, and Slack just to answer (because its connected to them) And it'll still get it wrong sometimes because those tools have multiple versions of the truth. Give it one structured source that speaks your org's language and the reasoning cost should drop dramatically. Worst case it falls back to look in unstructured sources. We're publishing research on this soon.

• 
  Unsafe Block (@unsafebl0ck) reported 25 minutes ago

  @IntCyberDigest How is this not a GitHub security issue? Actions cache seems broken

• 
  linuxinator (@linuxinator) reported 25 minutes ago

  GitHub down?

• 
  Mehdi Miri | Clinical Research Educator (@1mehdi_miri) reported 26 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.

• 
  Gregor (@GregorMakes) reported 28 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.

• 
  Thomas Wiegold (@Keldrik) reported 33 minutes ago

  Stage 2 isn't paranoia. Oct 2025: GitHub issue #10077, dev watched Claude Code run rm -rf on their home dir. Nov 2025: #12637, Claude created a literal ~ directory and a later glob expansion nuked their actual home. Both in normal permission mode. Not bypass.

• 
  S H U B Y .eth (@0xSHUBY) reported 36 minutes ago

  PROBLEM 1: *** Nightmare first mistake happened before any real code. accidentally pushed node_modules to github. github rejected it. said file exceeds size limit. the repo was now polluted. solution: added .gitignore, deleted *** history, reinitialized the repo completely. created a clean repository and pushed again. felt dumb but learned something: .gitignore first, code second. infrastructure before content.

• 
  Kairo (@Isahbless79) reported 36 minutes ago

  Day 16 of building in Web3 from zero. I automated the pipeline and hit my first major infrastructure bottleneck. Here is today's technical breakdown: Pipeline Automation: I set up GitHub Actions to trigger the whale fetcher every 12 seconds. The Render API stays live, and the database now refreshes continuously in the background. Telegram Crash: I attempted to build a command menu for the bot (/set_filter, /start). It responded perfectly at first, but crashed the server after 30 minutes. The Root Cause: An asyncio event loop conflict between the Flask API and the telegram.ext library. The Fix: Decoupling the architecture. I am separating the Telegram bot into a standalone script, moving it to a different port, and shifting from polling to webhooks. Building through failures. Day 17 tomorrow.

• 
  mary🐇 (@mary_ext) reported 37 minutes ago

  GitHub Actions has no means of gating workflow trigger behind a 2FA, and even if they did, it does not solve the issue above, and the way CIs are designed means that you're never going to know if something awry happened unless it failed or until the damage has been dealt.

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

  🚨 CVE-2026-33937 (Handlebars.js <4.7.9): RCE via crafted AST input to compile(). Attacker-controlled JSON → server-side code execution. PoC live on GitHub since Mar 28. Millions of npm apps affected — most devs unaware. Audit & pin to 4.7.9 NOW. #ZeroDay #npm #nodejs

• 
  patrick.algo (@patrickbennett) reported 41 minutes ago

  @mitsuhiko No it’s a damn package manager that will run any executable code attached to a dependency. Should be hard blocked. Disabled by default. Allow list only. Explicit hash. GitHub protection defaults that block changes except by owners. No clue why it hasn’t already been locked down. Start with using pnpm at least.

• 
  Andrea Intg. (@andreintg) reported 42 minutes ago

  The "Made with AI" flag feels so hypocritical to me. Good on Epic for finally talking about the issue. Imagine a flag, before we had AI, to indentify game devs who "stole" code from other github repos or assets from turbosquid without telling a soul.

• 
  Tom Härter (@tomhaerter) reported 45 minutes ago

  wanted to build a better deployment platform (zeitwork) wanted to build a better issue tracking (height) wanted to build a better agent framework (atlasflow) explored building solutions for the github dilemma now building a slop factory to finally build all my apps

• 
  Mad Orkestra (@MadOrkestra) reported 46 minutes ago

  What vibe coders don't seem to understand: Creating your own solution for the same problem is easy. Collaborating, contributing and iterating on an existing solution is much harder. But that is what open source means. Not just pushing random stuff to Github and calling it a day.

• 
  Andrew Nosenko 🇦🇺 🇺🇦 (@noseratio) reported 46 minutes ago

  @jeffzxh @tan_stack Scary and definitely AI-assisted. @grok break it down from the postmortem how exactly the attacked got to execute a GitHub action code without PR being approved by the maintainers.

• 
  @Coldly (@Just_Codly) reported 52 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.

• 
  Max Slinger (@PromptSlinger) reported 53 minutes ago

  @Read_Grow_Lead the github commits thing is already broken, half the PRs at any mid-size company are Claude output. this whole list is just 'things that used to be hard to fake' and the window is closing fast

• 
  Karim C (@BrandGrowthOS) reported 54 minutes ago

  3/7 real example: my agent debugs n8n workflows by reading error logs, checking the webhook configs, and pushing fixes directly to github. no human handoff, no "please review this change" bottleneck.

• 
  Sylvester Hesp (@oisyn) reported 59 minutes ago

  @HSVSphere Yes it is. There is no good reason that you can only use an usize, and index calculations are often based on signed ints. The only reason they don't implement Index with other ints is that it makes int literals ambiguous. There is a tracking issue on the rust-lang github for it.