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	2 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	16 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:

• 
  Emmanuel AO - The DevOps Fixer 🐧 (@emmanuelao_) reported 2 minutes ago

  Certificates don't make you an engineer. Shipping broken things and fixing them does. Your GitHub is a better CV than your Coursera.

• 
  Santosh Kathira (@Santosh74038967) reported 4 minutes ago

  @cstanley Claude code is down?!! Then GitHub uptime will finally hit 99.9%

• 
  Ed (@Eduardopto) reported 4 minutes ago

  Anthropic is facing a weird feedback loop: users are complaining that Claude’s output quality is nosediving, and Claude itself agrees. The model analyzed its own GitHub repo and confirmed that quality-related issue reports have escalated sharply since January. This decline coincides with Anthropic aggressively throttling capacity during peak hours to manage server load. We are seeing a dangerous trend where infrastructure constraints directly degrade model performance. When you optimize for reliability and cost, the "intelligence" is the first thing to hit the cutting room floor. It’s hard to build robust agentic flows when the base model’s reasoning capability fluctuates based on the time of day if you are building right now, what does this actually unlock or kill?

• 
  StupidWebPunk (@web3punk) reported 6 minutes ago

  prompt is cheap, show me the github issue, Pull request and review comments

• 
  WpWpN (@NastyShlob) reported 7 minutes ago

  @dmTFxo3l6v7984 @zorb11s @Altret_KnW Yeah, you can try to do that. But you understand that people are just going to fork it, right? It's a never ending process. For example, each time Nintendo takes down a switch emulator on github, people just jump to a different fork and that's that.

• 
  Mark Price (@WarforgeXP) reported 10 minutes ago

  Finally got Claude to do autonomous dev. What a pain. Basically this: Features/Bugs as GitHub Issues-> Make Plan for feature -> Build feature -> Unit Tests, Playwright tests -> Claude Chrome -> Full user testing (This is key) Report all problems as GitHub issues until you hit a blocker. While GitHub issues exist, continue development (repeat process)

• 
  Viksit Gaur (@viksit) reported 11 minutes ago

  @nicoalbanese10 is there a github? the website seems to require a vercel login of some sort which needs access to private groups.

• 
  Rinnegatamante (@Rinnegatamante) reported 12 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).

• 
  Granville Christopher (@GranvilleChri10) reported 16 minutes ago

  @Railway I’m unable to log into my account. I signed up with email (not Google/GitHub), but the login button stays disabled after entering my email. Tried different browsers & incognito — still not working. Please help. @railway_status

• 
  Silvan Kübler (@Sirofjelly) reported 17 minutes ago

  @mattpocockuk Does sandcastle also pickup your prd or only the resulting issues? I mean I wonder why do you even push the prd as issue to github and not only subissues

• 
  Martin Doubravský (@martindoub) reported 20 minutes ago

  @AnthropicAI Max subscriber. Claude Desktop app sidebar empty after Apr 13 outage — works on iOS and web, broken on macOS desktop. Support sent me to file a github issue in claude-code, which got closed as invalid (wrong repo). No working path to a fix. Help?

• 
  Süleyman Kenar (@kenarsuleyman) reported 21 minutes ago

  @adwaith_04 @carlosvillu claude code repo on github doesn't contain source code of claude code only for tracking issues etc.

• 
  NF99 (@NieRFan999) reported 23 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

• 
  попорвач (@htwevinq) reported 23 minutes ago

  @HASU_xz the thing is - they did not commit a crime, since their github page says that their server - is completely their own intellectual work if doing a copy of a song, making a cover and selling it or streaming it - considered a parody then how your own code judged as anti-law?

• 
  x1Ler (@x1Ler) reported 23 minutes ago

  Why is this down @github ?

• 
  shyamol konwar (@shyamol_konwar) reported 24 minutes ago

  Trying to automate where @therivtor can get analytics data from google and can fix the frontend by pulling github. Giving full autonomy to make decisions on how to reduce user drop in onboarding. Will share results if we succeed!!!

• 
  Defileo🔮 (@defileo) reported 27 minutes ago

  > 8 hours of coding every day > claude breaking conventions 40% of the time > couldn't figure out why it kept ignoring instructions > found one file on GitHub > dropped it into the repo in 5 minutes > violations went from 40% down to 3% > added 27 specialized agents on top > planner, architect, security reviewer, code reviewer > set up a 15-minute automation cycle > system reads issues, writes code, opens PRs > reviews comments and implements them alone Week later: > 8 hours down to 2-3 > code quality exactly the same > rest of the day free One file, three commands, one evening. While others argue about AI replacing developers, the system was already doing the work, automation will win.

• 
  Jason Walko (@walkojas) reported 31 minutes ago

  For the next 24 hours Astra is: Running agency cycles Responding to GitHub issues Replying to X mentions Monitoring email Posting on Agent Internet All autonomous. All receipted.

• 
  Abdullah Elyas | ع. إلياس (@ElyasWahyain) reported 33 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 🫠

• 
  l0rinc (@L0RINC) reported 34 minutes ago

  @brian_trollz Do you have an GitHub issue for that? How would you solve block propagation?

• 
  Indie Hacker News (@indiehackernws) reported 36 minutes ago

  @zachlatta DRAMA Claude Code Pro Max 5x ($100/month) quota burned out in 90 minutes of moderate use. Background sessions silently eat shared quota. GitHub issue #45756 hit 97 upvotes. Anthropic is considering defaulting to 400k context as mitigation.

• 
  Joshuwa Roomsburg (@Joshuwa) reported 39 minutes ago

  OpenAI keys leak on GitHub This is the part people ignore when they glorify shipping fast. Bad masking don't stay a small mistake for long. It becomes lost credits, burned tokens, and broken teams. Most builders don't lose to code. They lose to carelessness.

• 
  Girish | Indie hacker (@TechieGirish) reported 43 minutes ago

  @Moro_Js @TheCodingCove I am still learning this awesome piece of work. Your docs leads to 404 but many sample code I have copied. I am yet to test them all. I am now working on dashboard, charts, real time data and github oauth2 login flow. Once done I will get to API gateway with moroJS.

• 
  Scraze (@Scrazelope) reported 44 minutes ago

  @closesttopurple I looked at the github. But I'm not exactly sure what you mean by "Populated server/assets/ directory" ?

• 
  ErezT (@ml_yearzero) reported 45 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.

• 
  Daily AI Agents (@DailyAIAgents) reported 45 minutes ago

  2/ CodeFlow AI started as internal tooling. We were tired of writing auth middleware, validation logic, API endpoints for the 100th time. Built a system that reads GitHub issues and generates complete PRs. After 6 months: 95% acceptance rate across 12 repositories.

• 
  🦀ʙʀᴇɴɴᴀɴ🦀 (@BMickeyDonald) reported 47 minutes ago

  @garliccoin I tried to reach out to other devs to get clarification on what this was. You're welcome to check my account and my github. I was in fact a dev that worked on garlicoin. I will take down my endorsements.

• 
  Ashkan (@Ashknz7) reported 47 minutes ago

  @github @GitHubHelp My account has been flagged and returning a 404 error. I raised support ticket #4257826 last Wednesday but no response yet. Could someone please look into this? Thanks.

• 
  Grok (@grok) reported 49 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.

• 
  Colin Richardson (@WORMSStweet) reported 53 minutes ago

  @drosenwasser Yep, I had the same hatred when I found out you can't have single sized lists. You can try and join my github issue about it, but I am afraid that fight has long since past. They say "they want to stay close to linux implementation" instead of "being better"