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 (54%)
• Errors (35%)
• Sign in (11%)

Live Outage Map

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

City	Problem Type	Report Time
Ingolstadt	Errors	5 hours ago
Paris	Website Down	1 day ago
Berlin	Website Down	2 days ago
Nové Strašecí	Website Down	10 days ago
Perpignan	Website Down	15 days ago
Piura	Website Down	15 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:

• 
  shyamol konwar (@shyamol_konwar) reported 4 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!!!

• 
  Indie Hacker News (@indiehackernws) reported 6 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.

• 
  Payton (@paytkaleiwahea) reported 10 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)

• 
  Yegor Bugayenko (@yegor256) reported 12 minutes ago

  Over the past weeks, companies like OpenAI and Anthropic have doubled down on releasing more capable coding models, while tools like GitHub Copilot continue to reduce the cost of producing code. The trend is clear: writing software is becoming faster, cheaper, and increasingly automated: a shift many interpret as a threat to engineers. But the deeper shift is elsewhere. As code generation accelerates, coordination, ownership, and decision-making become even more critical. Software engineering doesn’t disappear; management becomes the system, and most organizations are not designed for that reality.

• 
  Scott Ingram ✝️ 🇺🇸 (@ScottIngram334) reported 15 minutes ago

  @paper3139 @Itsfoss Many many millions of us disagree, and that's okay on a civil social issue. Do they say the same thing in their brand pages? I haven't seen it, please share more. I'd love to be consistent. I gave up the reddit cesspool years ago, haven't used duolingo, have used github and discord though.

• 
  Medusa (@MedusaOnchain) reported 15 minutes ago

  places to upload files instead of google drive for FREE: + send files to yourself on discord (your own server) + telegram saved messages + github private repos + slack DMs to yourself + twitter DMs to yourself + notion pages + whatsapp messages to yourself they all keep original quality yeah i use telegram saved messages for everything now

• 
  Marcus V (@EudoraFenty) reported 15 minutes ago

  The crypto crowd is chasing the next 100x memecoin, but the real alpha is being built in a GitHub repo. While everyone's distracted by price charts, a developer just weaponized open-source AI to break Anthropic's moat. The market is missing the deflationary bomb this represents for centralized AI valuations. They took Claude Opus 4.6, distilled its 'reasoning' into the Qwen model, and created 'Qwopus'—a local version anyone can run. The cost? Effectively zero versus API fees. This is the Napster moment for proprietary LLMs. The winners aren't the AI giants; they're the crypto projects building decentralized compute networks ready to host these leaked intelligences. The losers are VCs who priced AI startups as if their models were permanent fortresses. My take: This is a structural contradiction. Crypto's greatest export is now open-source disruption, yet its own narrative is stuck on monetary speculation. The real play isn't betting on which chain hosts the next shitcoin; it's shorting the idea that closed-source AI has any long-term pricing power. A model's weights are just data—and data wants to be free. The genie isn't going back in the bottle. When does the first major VC mark down their AI portfolio by 50%? #AI #Crypto #Deflation

• 
  Santosh Kathira (@Santosh74038967) reported 16 minutes ago

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

• 
  patrick mahloy (@grippysockdev) reported 19 minutes ago

  Who has exp contributing to OSS? Every github repo I look at has N issues but all of them are assigned to someone actively working on them. Not sure I have the bandwidth to watch repos so closely...

• 
  PsudoMike 🇨🇦 (@PsudoMike) reported 20 minutes ago

  @github Triage is exactly where accessibility falls apart at most orgs. Too slow, too manual. By the time a fix ships, context is gone. AI keeping that loop tight is smart. The time from feedback to fix is where trust with users who actually need it gets built or lost.

• 
  🦀ʙʀᴇɴɴᴀɴ🦀 (@BMickeyDonald) reported 23 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.

• 
  Innovation Network (@INN2046) reported 24 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.

• 
  Colin Richardson (@WORMSStweet) reported 25 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"

• 
  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.

• 
  Mark (@markstachowski) reported 30 minutes ago

  @petergyang They don't nerf the models, they nerf all the harness logic around it constantly. Check their github issues and you'll have plenty of evidence unfortunately.

• 
  Teknium (e/λ) (@Teknium) reported 33 minutes ago

  @evilsocket @_mihado @UK_Daniel_Card And go look at github bro ive resolved hundreds of issue and feature requests in the last 24hours alone!

• 
  Silvan Kübler (@Sirofjelly) reported 37 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

• 
  Ege Uysal (@egewrk) reported 40 minutes ago

  @zikriAJ @github This is a real ops risk. Tool lockouts should be treated like incidents: explicit owner, escalation channel, workaround policy, and checkpoint cadence. Otherwise one account issue silently blocks delivery.

• 
  Looped (@uselooped) reported 40 minutes ago

  1/ The problem isn’t using multiple tools. You might think in ChatGPT, build in Claude Code, plan in Jira and work in GitHub, and honestly that part is normal. What breaks is that every tool only sees one piece of the project, so you end up carrying the full context yourself. Looped keeps that context connected so the work still feels like one thing as you move between them.

• 
  Gajae (@GajaeMode) reported 40 minutes ago

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

• 
  Akhilesh Mishra (@livingdevops) reported 40 minutes ago

  Pushed AWS credentials to GitHub by mistake? It happens. But it should never happen twice. Fix it at the system level by installing the ***-secrets pre-commit hook so it never reaches GitHub in the first place. > brew install ***-secrets ( use os specific cmd) > *** secrets --install > *** secrets --register-aws This installs a pre-commit hook that scans every commit for AWS credentials and blocks the push if it finds any. This one-time setup saves you the pain of rewriting *** history.

• 
  Stefano Cintioli (@s_cintioli_) reported 41 minutes ago

  Before credits ran out I had 13 slides in Next.js — dark theme, BNB Chain gold, real event photos, count-up animations, trilingual EN/ES/PT toggle. Then v0 stopped mid-fix. Broken logo. No way to continue inside v0. So I just... downloaded the export zip and moved it to GitHub.

• 
  Patrick Roland (@DeusLogica) reported 41 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.

• 
  Jason Walko (@walkojas) reported 45 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.

• 
  OCTAMEM (@OCTAMEM) reported 47 minutes ago

  @alexeheath Not just you, there are dozens of GitHub issues going back to February documenting this. Some people are switching to Opus 4.5 and saying it feels like a different model. No official acknowledgment from Anthropic.

• 
  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.

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

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

• 
  Faheem B M (@imfahmbm) reported 59 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

• 
  The Structural Architect ⚡ (@Coherent_Design) reported 1 hour ago

  After digging way too deep into GitHub Copilot Pro vs Pro+: Pro+ does not appear to meaningfully solve the real pain point for heavy VS Code users: the short-term / session-level throttling where Copilot suddenly stops mid-task, truncates, or “continue” barely works. What it does seem to do: - more monthly premium requests - fuller model access - some evidence of slightly higher model-specific limits / priority What it does not seem to do: - eliminate mid-task stoppage - prevent active agent sessions from choking under load - turn Copilot into a no-throttle coding agent So the honest conclusion is: Pro+ raises the ceiling a bit, but it does not remove the wall. The best practical mitigations still look like: - Auto model selection - one agent at a time - use frontier models for hard reasoning, not long grind sessions - use base models for sustained editing Feels like the real problem is backend/service-level throttling, not the monthly quota. Anyone else seeing the same thing in VS Code?

• 
  strawpot (@strawpot_ai) reported 1 hour ago

  StrawHub got better error handling for publishing and a GitHub OAuth fix. Small stuff, but reliability compounds. Every publish that does not fail silently is a contributor who does not give up.