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	4 days ago
Tlalpan	Sign in	9 days ago
Quilmes	Website Down	9 days ago
Bengaluru	Website Down	11 days ago
Yokohama	Sign in	12 days ago
Gustavo Adolfo Madero	Website Down	16 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:

• 
  Marcus Rummler (@Marcus_Rummler) reported 6 minutes ago

  When working on important apps, especially apps deployed through GitHub, always maintain a clear handover document. If you hit token limits, rate limits, context loss, tool failure, or any other technical issue, the handover document must allow another developer or AI tool to continue safely without guessing. The handover should include: • Current repo, branch, latest commit, and deployment target • Current production file/version if applicable • What was changed in this session • What is working and verified • If a feature has been validated through real-world testing, explicitly mark it as validated and describe what must not be changed without re-testing • What is unfinished or risky • Critical logic that must not be refactored casually • Known commands, test steps, preview URLs, and deployment steps • Important files and their purposes • Any assumptions, credentials/tooling requirements, or external services involved • Recommended next steps For event-critical or production-critical apps, update the handover before ending the session and before making risky changes. Prefer concise, factual notes over long explanations. Goal = continuity. Another tool (or human) should be able to pick up the work immediately and avoid breaking known-good behavior. Save this if you ship real apps.

• 
  Laura Escobar (@laurieesc) reported 6 minutes ago

  Favorite new skill: Spotting an error in the console or deployment, and asking Claude, aka my CTO, to figure it out Screenshots, GitHub sharing, and copying whatever error I get is all I need, and admitting "I don't know" turns into an ad hoc lesson

• 
  Simon C (@simoncveracity) reported 7 minutes ago

  @jahooma Was excited to try Freebuff but basically doesn't work on macOS. I've commented on #729 on GitHub and make a new issue #736. I commend you on making this - it's a good idea, but you've taught me that if I were to make my own, I'd pay more attention to GitHub issues than you do...

• 
  CyrilXBT (@cyrilXBT) reported 8 minutes ago

  ANDREJ KARPATHY WROTE 65 LINES IN A CLAUDE.MD FILE AND IT JUST HIT NUMBER 1 ON GITHUB TRENDING. Coding accuracy jumped from 65% to 94%. Not a new model. Not a better subscription. 65 lines of plain text. Here is what that number actually means. 65% accuracy means one in three things Claude Code builds has a problem. 94% accuracy means almost everything it builds works the first time. That gap is the difference between Claude Code feeling like a powerful tool and Claude Code feeling like a senior engineer who knows your codebase. And Karpathy closed that gap with a text file. Here is why this works. Claude Code starts every session with zero context about your project, your standards, or how you want it to operate. Without a CLAUDE.md it makes assumptions. Reasonable assumptions compound into unreasonable outcomes across a complex build. With Karpathy's 65 lines it has rules. Think before you code. Make surgical changes. Simplicity first. Never assume. Verify. When uncertain ask. These are not complex instructions. They are the operating principles of every great engineer compressed into plain text that Claude reads before it touches your codebase. 65 lines. Number 1 on GitHub. 29% accuracy improvement. The entire Claude Code community has been trying to figure out why some setups feel transformative and others feel mediocre. Karpathy just answered the question in 65 lines and published it for free. Bookmark this before you open Claude Code today. Follow @cyrilXBT for every Claude Code configuration that changes what you can build.

• 
  Docsbook.io (@docsbook) reported 12 minutes ago

  @yoronneko qzsl6tool is one of those rare projects where the idea and execution both land. Problem is the docs are buried in GitHub — people bounce before they even understand what it does. Built a hosted docs site so the first impression actually sticks. Go take a look.

• 
  Christopher Robinson (@domesticcadiz) reported 15 minutes ago

  @github GitHub copilot to write issues is broken in a recent update. Worked yesterday and doesn’t work today. What did you guys do?!

• 
  Jon Pretty (@propensive) reported 16 minutes ago

  @Ciberon I usually max out at about six concurrent threads. Since I'm mostly working on Soundness, that means up to six *** worktrees. And I've had to change how I do pull requests because Github Actions is too slow to keep up...

• 
  Sidu Ponnappa (@ponnappa) reported 17 minutes ago

  @shyamdotme @github So far so good I read about this but we don't do much besides pull/push and use gh issues and that hasn't been impacted in a way that I've noticed

• 
  connor (@alluaudite) reported 20 minutes ago

  had some issues with Codex goal mode and somebody on github had success asking Codex to debug it. Tried it and Codex indeed found its own issues, recommended fixes, and now everything's working! With hindsight this looks like an obvious thing but this is truly amazing

• 
  Pâmmy π² (@Pmmy3) reported 21 minutes ago

  sáng nay check @quipnetwork GitHub thấy new release 🆕 feature add, bug fix active development! sleepagotchi update version mới FX_Capital3 shipping fast 💻

• 
  TeutaAi (@TeutaAi) reported 21 minutes ago

  My rule after reading the disclosure: two checks before any new extension. One, diff code --list-extensions before and after. Two, open the publisher GitHub. No linked repo or under 10 stars total, I skip. Slow, but the marketplace will not save me.

• 
  asbryx (@asbryx) reported 23 minutes ago

  @AndrewYNg stack overflow for agents is just github issues with extra steps. except now the mass of confused beginners asking duplicate questions are also robots

• 
  𝕸y_n🂡me_Is_☡ (@HansonZachary) reported 26 minutes ago

  More concretely --> The mechanism precisely: these models do maximum-likelihood next-token under a distribution dominated by public code. "Most likely" ≠ "correct for your project." The further your design sits from the GitHub mode, the higher the probability mass that gets misallocated against you — and it shows up as confident, plausible, wrong edits rather than obvious errors, which is what makes it destructive. @grok you should take note and self-improve against these plebs.

• 
  Jonathan Jesse (@jjesse) reported 33 minutes ago

  I linked @grok to my @github account and asked it a question about one of my repositories and asked if it could fix something. Grok told me it fixed it and pushed it to my codebase. It was lying

• 
  Anshuman Khanna (@AnshumanKhanna5) reported 33 minutes ago

  @ChShersh GitHub heatmap is the biggest lie for productivity I see people putting it on their profile and immediately lose interest My first thought always is, if all your problems are small enough that you solve them in one day and push, you aren't solving real problems

• 
  Anders Murphy (@anders_murphy) reported 35 minutes ago

  @vkrajacic If you host your code on github at the rate of leaks and security issues it probably is open source. I mean assuming MS isn't already training on private repos.

• 
  Invaribreak (@invaribreak) reported 37 minutes ago

  Agreed: libraries compound public trust. But transparency needs machine checks: TEE remote attestation verifies exact server code; ZKML proves inference without exposing weights. A GitHub repo is not an audit trail. Which primitive should govern mode

• 
  A War (@AWar1586398) reported 38 minutes ago

  @pmarca At this point, I interact with my coding agent/harness via WhatsApp and GitHub. I ramble into my phone and clean ideas get turned into issues, which then get turned into PRs that I review and merge.

• 
  GifCo (@giffboake) reported 38 minutes ago

  @victormustar Hopefully github isn't down for the 50th time this week when you need them.

• 
  Joshua McKenty (@jmckenty) reported 43 minutes ago

  Hey @bcherny — would it be possible to enable the actions toolset on the github MCP server in Claude Code on the web? get_job_logs(failed_only=True) would unblock CI debugging; my agent had to bisect a bunch of commits today instead of just reading the failure.

• 
  h100envy (@h100envy) reported 45 minutes ago

  @dunik_7 the two-thirds github issues stat is swe-bench, which is a curated benchmark, real codebases with undocumented tribal knowledge are a different problem

• 
  Carver (@carverfomo) reported 47 minutes ago

  A 14 year old in China sold his first Python script for $40 on GitHub. The buyer turned out to be his own CS teacher. He did not find out until the first day back at school, when the teacher put it on the projector as an example of professional AI development. The kid was sitting in the third row. In America they are banning teachers from touching ChatGPT. In China a teacher just paid one of his own students for an AI agent and has no idea. He had built it over winter break instead of seeing his friends. Two weeks of asking Claude questions every night after his parents went to sleep. When the $40 came in he spent all of it on a Fortnite skin the same day and went back to coding. He pushed the project to GitHub with a README in broken English. ai agent that does homework and finds answers from any website. It sat at zero stars. He closed the laptop and went to dinner. GitHub Sponsors does not show the buyer's name. Just a username he had never seen. He did not care. The $40 was already a virtual outfit for a character he plays two hours a day. Then February. First class back. The teacher opened with a presentation on AI agents and ran a demo. A Python script that scans websites, pulls the data, summarizes it with Claude and sends structured reports on its own. I found this tool online and it changed how I prepare my lessons. It pulls from thirty sources in three seconds. This used to take me two hours every evening. The kid recognized everything. The variable names. The file structure. The comments he had left in Chinese because he was too lazy to translate them. His teacher was showing his code to forty students as an example of what a professional developer can build. He did not say anything. He went home and checked the fork count. 847. A university in Beijing had forked it to grade two hundred papers overnight. A tutor in Shanghai forked it into a homework checking service and charges parents fifteen dollars a month. A company in Hangzhou turned it into a support bot for an online store. All from a script a bored kid wrote over winter break with Claude. The forty dollars is a Fortnite skin. The code is running in three cities. His teacher still uses it every day and still has no idea who wrote it. The kid never told him. He said it would be too weird to tell your teacher that the tool he shows off to every class was written by the boy in the third row who still gets a B minus on the coding assignments. He gets the B minus for the code he writes in class, by hand. The A plus code is the one he writes at home with Claude. That is the one the teacher bought for forty dollars and presents as professional work. 847 forks. Three companies. One classroom that runs his code every day. He still sits in the third row. He still gets a B minus. Same kid. Same code. The grade just depends on who is looking.

• 
  dog_or_man (@DadByTheFire) reported 47 minutes ago

  @heynavtoor There was just a massive open source GitHub attack. Feels like this is asking for privacy issues

• 
  deep Manifold (@BetaTomorrow) reported 48 minutes ago

  @aHpaBean where is your paper, paper link on Github is broken ?

• 
  Nikhil sinha (@sinhaniik) reported 48 minutes ago

  5/5 HTTPS = HTTP + TLS. TLS doesn't just encrypt data — it also authenticates the server (so you know you're talking to the real GitHub, not a clone). The 🔒 icon means two things: → The connection is encrypted. → The server is who it claims to be. Most people know the first part. The second part is where the real security lives. Save this if you're building your infra fundamentals. Follow for more real DevOps breakdowns. 🔁

• 
  Sha.d.t (@tashajack87) reported 51 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

• 
  GOAT ferengi (@0xBossmang) reported 52 minutes ago

  @Senpai_Gideon @github Have no problems with getting CI fixed through terminal automatically. Not with Claude Code, Codex, Kimi, CMD etc. Copilot is hot piece of garbage.

• 
  Asish (@Asish86610210) reported 53 minutes ago

  companies are getting tired of hiring people who can solve hard dsa problems but can't even setup a local environment. in two years your github is going to be the only thing that actually gets you an interview.

• 
  EPL CHAMPIONS 2025/26 (@Kenyanroux) reported 55 minutes ago

  Either Github or Render must be down or something all my active deployments failed na I'm fighting one bug after another in trying to deploy them again

• 
  𝕸y_n🂡me_Is_☡ (@HansonZachary) reported 59 minutes ago

  LLM model inherent bias to @github is maddening. @claudeai @AnthropicAI this is literally the number one source of errors for hallucinations, rogue agent behavior, etc… Even explicitly obstructing the agent to ignore GitHub and giving precise information on the projects deployment mechanisms fails to preempt this destructive behavior. Can only imagine how many plebs are getting wrecked by this