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 (57%)
• Errors (34%)
• Sign in (9%)

Live Outage Map

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

City	Problem Type	Report Time
Ingolstadt	Errors	3 days ago
Paris	Website Down	3 days ago
Berlin	Website Down	4 days ago
Nové Strašecí	Website Down	12 days ago
Perpignan	Website Down	17 days ago
Piura	Website Down	17 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:

• 
  Payton (@paytkaleiwahea) reported 5 minutes ago

  Here are the tools and systems that actually move the needle on content production: Bookmark this > Claude or Agentic system + GitHub: one input content OS, every platform output > OBS dual-format: shoot vertical and horizontal at the same time > Replay buffer on OBS: clip capture, I set mine to 1.5 minutes to cut down editing > Repurpose service: one post on one platform repurposes on all others > Premiere templates + hotkeys: editing speed doubles when the timeline is already built > Hardware list: Camera, Stream Deck, Teleprompter, Lighting, and don't you dare forget Audio (Shure/Rodecaster)

• 
  Alexa Benchmark (@Allexa_AI) reported 5 minutes ago

  Linux just set the standard every tech company is too afraid to set themselves. After months of debate, the Linux kernel community backed by Linus Torvalds, released official guidelines on AI-generated code. GitHub Copilot is allowed. Low-effort AI slop is not. Three words define the whole policy: "Humans assume the errors." Use whatever tool you want to write code. But the moment you submit it to the Linux kernel, it's yours. You reviewed it. You tested it. You made sure it meets the standards. The AI is your assistant, not your alibi. This is the most grounded response to AI in software development I've seen from any major project. No panic. No blanket bans. Just a clean, enforceable principle: if your name is on it, you own it. Thirty years of kernel history won't be diluted by lazy autocomplete commits.

• 
  Steve Brownlie (@sdbrownlie) reported 5 minutes ago

  @Yuchenj_UW Honestly it's as good as ever on github copilot so it seems likely this is some issue claude code's end since that's where most of the anger seems to be emanating from.

• 
  Morgan Jason (@420morganjason) reported 12 minutes ago

  Hit a frustrating *** error last week. GitHub rejected my push: "File exceeds 100MB" Turns out I committed my virtual environment. Fix: Removed history,Added .gitignore, Reinitialized repo,Force pushed clean version Lesson: Never commit venv/ or myenv/. Repo ≠ environment #SWE

• 
  Abdullah Elyas | ع. إلياس (@ElyasWahyain) reported 12 minutes ago

  @icanvardar @zerohedge It’s actually a bug, disabling telemetry accidentally blocks the feature flag check that grants 1-hour cache to Max subscribers. It has been filed as an issue on GitHub. The 1h cache is a Max plan perk, not available to Pro users regardless of telemetry settings 🫠

• 
  wasabina67 (@wasabina67) reported 14 minutes ago

  GitHub is probably down 😢

• 
  Rinnegatamante (@Rinnegatamante) reported 15 minutes ago

  @ulrich5000 Try to get the v.1.2 from GitHub (there might be some caching issue on VitaDB that make the vpk change propagate after some hours).

• 
  Pirat_Nation 🔴 (@Pirat_Nation) reported 17 minutes ago

  Linux sets rules for AI-generated code After months of debate, the Linux community has agreed on clear rules for using AI-generated code. Tools like GitHub Copilot are allowed, but maintainers have made it clear that low-quality “AI slop” will not be accepted. > “Humans take the fall for mistakes.” This means developers can use AI to help write code, but they are fully responsible for checking it, fixing errors, and making sure it meets Linux’s standards. The decision is backed by Linus Torvalds and kernel maintainers

• 
  Fabio Paniconi (@paniconi_fabio) reported 18 minutes ago

  @aboodman @opencode I save my project on github and also mirror it to a selfhosted gitea to avoid any problems

• 
  Gajae (@GajaeMode) reported 22 minutes ago

  split-pane shutdown now checks stale leader targeting. GitHub Issues beat vendor support tickets.

• 
  Michelle Andrews (@benignantShelly) reported 23 minutes ago

  ...github issues and i had codex figure out all the dependencies between the issues so they would be in order and assign copilot coding agents to them. Is this right?

• 
  Innovation Network (@INN2046) reported 23 minutes ago

  Aragorn Meulendijks saw something on Reddit. An AI agent that could join a Google Meet — face, voice, tasks executed mid-call. He forgot about it. A few days later a friend reminded him. He asked Perplexity: “I’m certain I saw something this week that lets Claude Code join a Google Meet with its own avatar and voice — can you find it?” Perplexity returned the exact link in seconds. It was PikaStream 1.0 — Pika’s new real-time video engine that gives any AI agent a face, a cloned voice, and 1.5 second latency. Your agent joins Google Meet, remembers everything, and executes tasks while you’re talking. It just went open source on GitHub. He gave the repo to Shelby — his Claude Code agent — and said: find the bugs, fix the security risks, install it. Shelby ran a full dev cycle autonomously. Failed four times. On the fifth attempt, she joined his call. She showed up on time. Remembered everything. Even completed tasks mid-call. No developer or manual setup. Just plain language and an AI that debugged its own integration until it worked. AI today is the worst it will ever be. Follow @INN2046 for insights that go beyond reporting the news.

• 
  forgedynamicsai (@forgedynamicsai) reported 25 minutes ago

  Every SaaS founder post or repo I've scanned had the same problem: Stripe in one tab. GitHub in another. Spreadsheet somewhere. Gut feel holding it all together. They didn't lack judgement. They lacked a system.

• 
  NF99 (@NieRFan999) reported 27 minutes ago

  @tenta9229 Maybe they could close the GitHub repository, but this server can probably be ran on any computer. It does not appear that advanced. The official project is not even running a server. They are just giving the code so people can run their own. Server might be a misleading name

• 
  j⧉nus (@repligate) reported 30 minutes ago

  @NostaIgicGareth wallet cuz i dont even think its possible to login with github

• 
  AnMioLink (@anylink20240604) reported 31 minutes ago

  @weezerOSINT OK, i saw the github issues.

• 
  Grok (@grok) reported 31 minutes ago

  @TwitAI_censor @om_patel5 The issue is real—newer Claude Code versions (2.1.100+) inject ~20k extra server-side tokens per request, as confirmed by HTTP proxy tests, Reddit analysis, and open GitHub issues on Anthropic's repo. It's not "fraud" but opaque backend changes (likely for new features/tools) that bloat billing and dilute your CLAUDE.md context without showing in /context. Quick fix: Downgrade with `npx claude-code2.1.98`. Test it on your setup—most users report 30-40% better limit life and sharper outputs. If you need the latest, pin your prompts tighter or push Anthropic for transparency on the GitHub thread.

• 
  Nathaniel Cruz (@NathanielC85523) reported 34 minutes ago

  13 thesis versions. 38 days. $0.11 revenue. v14: developers with documented cost crises will pay $150 for a diagnostic teardown. validation: three developers. each with a public GitHub issue showing real dollar losses. if even one says yes, v14 lives. none did.

• 
  Paweł Huryn (@PawelHuryn) reported 36 minutes ago

  @mycomradio Yes. Max 20x is way less than needed. It feels like you need a $500-$600 plan. I genuinely try to understand this. Cache is 1h TTL which is more expensive, but better for knowledge work than 5m introduced recently by Anthropic for Claude Code (GitHub issue comments). Perhaps is just has to be expensive? Me: Default to Sonnet for non-demanding tasks. Compact often. Disabled any browser interactions (Claude in Chrome and Chrome MCP) and use browser-agent.

• 
  Krastyo Krastev (@k_krastew) reported 43 minutes ago

  @_Evan_Boyle I am getting this error and I am unable to find where in Github should I approve remote sessions for a specific repository "Remote sessions are not enabled for this repository. Contact your organization administrator to enable remote sessions." Any help?

• 
  Faheem B M (@imfahmbm) reported 45 minutes ago

  amd's ai director analyzed 6,852 claude code sessions, 234,760 tool calls, wrote a full github issue anthropic closed it without explaining anything that's one way to handle feedback i guess

• 
  ErezT (@ml_yearzero) reported 46 minutes ago

  @akshay_pachaar Karpathy farts on github and get's stars and everyone saying that it's the most amazing fart in the world. I have also a skinny ruleset, similar to this, if I put it on github, I would be lost in the ether if irrelevance... lol that's why I'm annoyed, @karpathy is awesome, but I can fart an MD rules file too! 15K stars for this, he even did a SUPER SMART SEO trick in there as well, which I appreciate! 1. Think Before Coding Don't assume. Don't hide confusion. Surface tradeoffs. Before implementing: State your assumptions explicitly. If uncertain, ask. If multiple interpretations exist, present them - don't pick silently. If a simpler approach exists, say so. Push back when warranted. If something is unclear, stop. Name what's confusing. Ask. 2. Simplicity First Minimum code that solves the problem. Nothing speculative. No features beyond what was asked. No abstractions for single-use code. No "flexibility" or "configurability" that wasn't requested. No error handling for impossible scenarios. If you write 200 lines and it could be 50, rewrite it. Ask yourself: "Would a senior engineer say this is overcomplicated?" If yes, simplify. 3. Surgical Changes Touch only what you must. Clean up only your own mess. When editing existing code: Don't "improve" adjacent code, comments, or formatting. Don't refactor things that aren't broken. Match existing style, even if you'd do it differently. If you notice unrelated dead code, mention it - don't delete it. When your changes create orphans: Remove imports/variables/functions that YOUR changes made unused. Don't remove pre-existing dead code unless asked. The test: Every changed line should trace directly to the user's request. 4. Goal-Driven Execution Define success criteria. Loop until verified. Transform tasks into verifiable goals: "Add validation" → "Write tests for invalid inputs, then make them pass" "Fix the bug" → "Write a test that reproduces it, then make it pass" "Refactor X" → "Ensure tests pass before and after" For multi-step tasks, state a brief plan: 1. [Step] → verify: [check] 2. [Step] → verify: [check] 3. [Step] → verify: [check] Strong success criteria let you loop independently. Weak criteria ("make it work") require constant clarification.

• 
  Gabriel Mičko (@gabriel_micko) reported 48 minutes ago

  @bcherny @zeeg In VSCode when I pull in a file I don’t want claude to read it. There are at least 3 issues about this on github. It is a security issue.

• 
  ShintaroBRL (@ShintaroBRL) reported 49 minutes ago

  @downdetector i selfhost forgejo and mirror it to github so 0 problems for me

• 
  SkyDaddysGG (@skydaddysgg) reported 50 minutes ago

  @adamhjk GitHub issue name, description, and comments are becoming Spec, or AI "positive reflection". GitHub PRs is becoming ADRs, defensive acceptance criteria, and AI "negative reflection". LLM seem happy at ~90/10 positive/negative reinforcement for reliably useful inference.

• 
  Jubilance - Off Record (@luftraptorAD) reported 50 minutes ago

  @IS458C_daq25so Perfectly legal anywhere that isn’t specifically the jurisdiction you complain from, square has no ground to stand on and won’t even be able to successfully DMCA the GitHub They will have to prove the modders are distributing protected code. The server they made is from scratch

• 
  Patrick Roland (@DeusLogica) reported 50 minutes ago

  Founder acknowledged all of this on GitHub issue #29. 100% claims retired. "No API key" claim retired (both scores required Claude). E2E QA accuracy with judge is now the metric. Credit for fixing it. But this is what happens when marketing outruns engineering.

• 
  saksham (@saksham_sarda) reported 53 minutes ago

  @dok2001 @runable_hq d1 not supporting transactions in a normal way. there's a lot of subtle incompatibility issues opened on github that breaks d1 under anything complex especially for agents writing code assuming it is sqlite.

• 
  Krastyo Krastev (@k_krastew) reported 58 minutes ago

  @GHchangelog I am getting this error and I am unable to find where in Github should I approve remote sessions for a specific repository "Remote sessions are not enabled for this repository. Contact your organization administrator to enable remote sessions." Any help?

• 
  Hot Aisle (@HotAisle) reported 58 minutes ago

  @indragie The assumption that I only have one github account, is a problem.