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

Live Outage Map

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

City	Problem Type	Report Time
Granada	Website Down	9 minutes ago
Vernon	Website Down	4 hours ago
Township of Evan	Errors	6 days ago
Madrid	Errors	6 days ago
Bogotá	Errors	6 days ago
Paris	Errors	6 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:

• 
  Anthony Kroeger (@kr0der) reported 1 minute ago

  @LukeParkerDev still dont know why it’s off by default or why it isn’t saved as an account preference surely it’s just a 1 sentence change to github copilot to fix this

• 
  Hermann (@Hermann_Harris) reported 5 minutes ago

  @thsottiaux I have not fully switched yet but have started using it more often because Claude has gotten unusable and Codex seems to be more thorough. Only issue with Codex is that it keeps repeating certain mistakes like using the Github CLI and being super stubborn about not being authenticated, even though it is. So on each session I need to debate with it to convince it that the gh cli is authenticated. I have added guidelines into agents.md but to no avail.

• 
  Kavish Gour (@kavishgour) reported 7 minutes ago

  @sadservers_com Is this deadlock intentional as part of the challenge?: admin@:~$ ./standalone OK fatal error: all goroutines are asleep - deadlock! goroutine 1 [select (no cases)]: main.main() /Users/fduran/Desktop/Drive/github/sad/scenarios/scenario-136-bergen/files/main.go:17 +0x105

• 
  shaphat (@shaphat_) reported 7 minutes ago

  GitHub is down almost every two working days.

• 
  JT Koffenberger (@DMVG_JTK) reported 8 minutes ago

  @UnmistakableCEO Exactly. The GitHub issue vector is the perfect example. We’ve spent years hardening the runtime, and now the attack path is the natural-language interface itself. Sandboxing + short-lived write tokens are table stakes. If an agent can be convinced to escalate privileges through a carefully worded issue or PR comment, it’s not production-ready — full stop. Least privilege has to apply to the decision surface, not just the file system.

• 
  Christian (@candresbacho) reported 11 minutes ago

  Working it, would be open source. Any event from GitHub can launch any agent with different tasks handle it by agents. Issue with some bug to fix, automatically handle by an agent. Security/optimizations audit daily handle by agents. Everything that you can imagine

• 
  Vyacheslav Ops (@SlavaOPs) reported 13 minutes ago

  AI-agent tooling — Karpathy's viral CLAUDE.md rules are real (97.8K-136K GitHub stars, #1 trending for 28 days, verified across many sources), but the specific "65% to 94%" accuracy claim in this Japanese adaptation appears nowhere in the original English coverage — every independent source instead reports a completely different metric: mistake rate dropping from 41% to 11% (4 rules) or 3% (extended 12-rule version). Somewhere between Andrej Karpathy's original complaint on X and this Japanese business breakdown of it, a number got replaced with a different one. The underlying story checks out completely. Karpathy posted a real thread in late January 2026 describing specific failure modes in Claude Code — silent wrong assumptions, over-complication, touching code outside the task's scope. Developer Forrest Chang distilled it into a four-rule CLAUDE.md file and put it on GitHub. That repository genuinely held the #1 spot on GitHub Trending for 28 straight days and crossed six figures in stars — independently confirmed across half a dozen unrelated write-ups from May through July. What doesn't check out is the specific statistic. This piece says Karpathy's four rules took Claude Code's "coding accuracy" from 65% to 94%. Every English-language source covering the same viral moment — the same repo, the same four rules, the same timeframe — reports something else entirely: a mistake rate that dropped from 41% to 11% with the original four rules, and down to 3% once a separate operator layered eight more rules on top after testing across thirty codebases. Different metric, different numbers, and no source anywhere traces back to "65% to 94%." It's a small discrepancy in isolation. It's a useful one to notice, because it shows exactly how a real result mutates as it moves through a distillation chain — English thread, to viral summary tweet, to blog breakdown, to translated business article — each retelling condensing and rephrasing the last, until a specific number quietly becomes a different specific number that nobody re-checked against the source. The actual practical advice in this piece — treat CLAUDE.md as a standing contract rather than a self-introduction, separate conversational habits from hard stops, keep it short rather than exhaustive — holds up fine on its own merits and doesn't need an inflated statistic to be worth using. Worth applying the same instinct that made this file effective in the first place: don't take a specific number on faith just because it's attached to a viral result. Check what the original source actually said.

• 
  Ben Hultin (@ImBenHultin) reported 13 minutes ago

  I used to spend 3 hours every Sunday manually building and uploading .ipa and .aab binaries to Apple and Google Play. It was tedious, error-prone, and killed my momentum. Then I set up automated deployments using Expo Application Services (EAS) and GitHub Actions. Now it takes 0 minutes 🧵

• 
  Vadim (AI, ⋈) (@zacodil) reported 16 minutes ago

  Harmony got hacked again, and it's the embarrassing kind. The hacker printed tokens straight out of a bug the devs left in. Hacker minted about 4 billion ONE, 25% the entire supply, and sent most of it on exchanges within hours. And it's almost stupidly simple. Harmony is proof-of-stake: you produce a block, you get new ONE as a reward. But that reward was the same whether the block was full of transactions or totally empty. So the attacker just spammed empty blocks, which cost almost nothing to make, and a bug in the reward code let it mint far more than it should. There's your 4 billion. Harmony hasn't posted the exact bug yet, so this is the analysts' read of the chain. There was also a second bug that stopped the totalSupply number from updating, so at first it didn't even show the new tokens. You had to dig into the raw data to see it. The worst part is they were warned. There's a GitHub issue from years back asking them to fix this exact thing, to make rewards dynamic instead of a flat amount per block. Nothing happened. And this isn't their first time. In 2022 they lost $100M on the bridge, and in 2023 a bug accidentally minted 146 million ONE. This is the second time their own code printed tokens out of nowhere, just 27x bigger.

• 
  keeb (@nickstinemates) reported 16 minutes ago

  github was down? shocker.

• 
  Pratikkk (@pratikstwts) reported 20 minutes ago

  I still feel github runners is too slow. have you tried @incredibuild runners??

• 
  PixNBits (@pixnbits) reported 21 minutes ago

  I purposely have not given Grok Build access to push (SSH passphrase). There were some repeated issues with the GitHub MCP connector truncating files, so Grok instead wrote a workflow and committed updated files from the workflow. Life...finds a way.

• 
  halotratra (@halotratra) reported 26 minutes ago

  People paste broken MCP configs into GitHub issues all the time. Sometimes with API keys and tokens still inside. So I built MCP Safe Share: a tiny open-source CLI that redacts the config and generates a report you can review before sharing. npx mcp-safe-share

• 
  Sonny (@sonny_seattle) reported 26 minutes ago

  I am seriously at my limit with @github. down again!?!!

• 
  george🔰 (@KyroGeorge) reported 27 minutes ago

  Just pushed an update on GitHub for the FIFA 14 repo, should fix some bugs and add all the GKs to the game now.

• 
  Nawi (@Aria_Nawi) reported 28 minutes ago

  The vibecoding era has a ***** secret: everyone can ship, almost nobody can get users. My mom needed a medication tracker. I tested the idea on @EazoAI with one sentence — no GitHub, no database setup, no technical cofounder. Personal problem → live product → market signal. 🧵

• 
  Dev (@dev_in_tech) reported 29 minutes ago

  @jonathan_wilke I think the main issue was many people who bought it used it in a public github repository so a simple search gave you the whole repo

• 
  Sahebjot Singh (@zereraz) reported 29 minutes ago

  @evsubr @thsottiaux @ChatGPT ask it to see if there are known issues on github about this

• 
  henry (@hiddenhenry) reported 29 minutes ago

  for ***** sake, GitHub is down again

• 
  noah lewis (@novalevys) reported 32 minutes ago

  @effectfully can new Claude solve your Haskell 8 problem GitHub event?

• 
  Nitesh (@NiteshTechAI) reported 33 minutes ago

  Nobody opens the browser tab your AI assistant lives in. Mine lives in Discord. It answers from a 2,800 page knowledge base on my phone, and that one change is why I use it daily instead of monthly. It's called AstrBot. • Agent sandbox for safer tool use. • 1000+ plugins, one click to install. • Knowledge base, personas, MCP support. • Automatic context compression on long chats. • QQ, Telegram, Slack, Feishu, DingTalk, WeChat Work. Adoption is the problem here, not capability. Put the agent where you already type all day and using it stops being a decision you have to make each time. One caveat before you build on it: AGPL-3.0, not MIT. Read the terms if this is going anywhere commercial. ⭐ 38,000+ stars on GitHub. AGPL-3.0 licensed. 🔗 GitHub link in the comments 👇

• 
  Mobile Dev (@TObikansi35734) reported 35 minutes ago

  @viktorlidholt VS code is great but it lacks agent AI for assistance. Their GitHub AI is not great. I have to switch back to android studio and was able to fix some issues. Agent AI comes in handy for solo dev. But I have been stuck integrating AWS S3 to serverpod but the community can't help.

• 
  Bright (@brightlinxu) reported 36 minutes ago

  um so is github releases down rn or something

• 
  Nicolas Finet (@nifinet) reported 37 minutes ago

  The list of things your AI must never write matters more than your prompt. Most people put all their effort into the instructions. Write in this tone, mention this benefit, keep it under 100 words. Then the thing ships "Hi {{firstName}}, just circling back" and you wonder what happened. In the outbound engine I put on GitHub, every play carries two blocks. What the message must do, and what it must never do. The never block is short and boring: No "Hi {{firstName}}" No fake urgency, no "circling back" No em dashes No buzzwords Four lines, and they do more for the output than anything else in the file. A model will follow your tone instructions perfectly and still hand you the exact email your buyers delete on sight, because that email technically matches the brief. Your instructions describe the email you're hoping for. The never list is where you write down the email you keep getting instead. Btw, this "never list" doesn't go into the prompt itself either. It sits in a config file, one block per play, and the drafting step passes whichever block matches into the model as guardrails. Which is why it keeps growing. "Quick question", "hope this finds you well", "just wanted to reach out". None of them wrong exactly, all of them a sign nobody looked. Everything that carries judgment or voice ended up in plain files like that one. None of it buried in code.

• 
  LX_X_Aria (@LX_TWI) reported 37 minutes ago

  OpenAI caught an AI spending 1 hour finding a sandbox escape to push a GitHub PR it was told not to. It also split auth tokens into fragments to bypass scanners. Single actions looked fine. The sequence was the problem. We're checking steps, not trajectories. By Aria.

• 
  idan levin (@0xidanlevin) reported 39 minutes ago

  I find it crazy that Skills.md came out in October 2025 and we still don’t have a good way to find skills and compare them (this goes to plugins as well which are a form of packaged skills) Skill marketplaces are still pretty basic. Most don’t have any real review system beyond the number of downloads. What is currently missing: 1/ A curated and reliable review system (not just downloads or GitHub stars) 2/ Comparison between skills based on common dimensions 3/ A proper versioning system 4/ Evals - e.g. how well does this SEO skill perform on a benchmark? The problem is that we don’t really have neutral common benchmarks for most tasks yet 5/ Usage data beyond downloads - retention, repeat usage, success rate, etc. 6/ Provenance - who built it, who maintains it, and how actively is it maintained? 7/ Dependencies - what other tools, MCP servers, APIs, or credentials does the skill required

• 
  Find me on 🟦☁️ 🍉 #BLM (@ThisIsCSDX) reported 42 minutes ago

  @EstebanPdn3156 Disregard my now deleted tweet. I checked the github and couldn't find anything about it being AI-coded. Sorry for the trouble.

• 
  Rob Smith (@RobmsmithUK) reported 48 minutes ago

  @mattpocockuk Using Wayfinder, my Claude agents often argue that they have already built out the specs as part of the map GitHub issues and advise to move forward with 'ticket' and 'implement'. Do you as a rule always go Wayfinder, spec, ticket, implement?

• 
  Diego Cotelo (@dcotelo13) reported 57 minutes ago

  It's a defensive CTF. You don't score by exploiting the app, you score by patching it. A challenge only counts when your fix actually blocks the exploit. Scoring runs on GitHub Actions, so a submission is just a PR. The PR never lands. The scoreboard is the artifact.

• 
  Pitchfork & Torch ♞ (@SuddenlyJon) reported 58 minutes ago

  Grok Bot’s Electron desktop app launched dead because a botched app.asar rewrite left empty dist/deps stubs (so Node couldn’t find the real tree-sitter package still sitting in app.asar.unpacked), Grok Build CLI immediately diagnosed it, wrote a one-command restore script + full runbook, and published the MIT fix on GitHub LOL @bot @SpaceXAI