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

Live Outage Map

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

City	Problem Type	Report Time
Nové Strašecí	Website Down	4 days ago
Perpignan	Website Down	9 days ago
Piura	Website Down	9 days ago
Tokyo	Website Down	10 days ago
New Delhi	Sign in	16 days ago
Kannur	Website Down	20 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:

• 
  Aidan Raney - OSINT Expert (@AidanOsint) reported 4 seconds ago

  One example of these tools is Sherlock, which is a tool to search for usernames across platforms. • Over recent years, platforms have blocked automated queries through rate limits, API lockdowns, and deliberate public profile visibility. • Public GitHub issues disable compatibility without warning, reducing reliability and forcing constant maintenance on the tool. 2/8

• 
  JN (@jntrung) reported 1 minute ago

  Just found a TypeScript library that generates Mermaid diagrams from natural-language descriptions. If you already use Mermaid in GitHub, Notion, or Obsidian: describe what you want, it writes the syntax. It's called oh-my-mermaid. 792 stars. Here's what it does: → Takes plain-English diagram descriptions as input → Generates valid Mermaid syntax automatically → Supports flowcharts, sequence diagrams, and ER diagrams → Drops into your existing Mermaid setup as a TypeScript library → Works anywhere Mermaid works: GitHub, GitLab, Obsidian, Notion, VS Code The part that changes how I think about diagrams: Every time I needed a flowchart, I'd write out the Mermaid nodes by hand, get the arrows wrong, test it, fix it, test again. The syntax is learnable but not fast. Now I describe it: "Create a sequence diagram showing user login flow: user submits form, backend validates, JWT issued, returned to client." Done. You get the diagram. You don't edit the syntax unless you need to. Mermaid is already everywhere. This just removes the last friction. TypeScript. Open source.

• 
  Ankit Aggarwal (@riyank0616) reported 2 minutes ago

  What problem do you see when you use github copilot or Claude or Codex etc for fixing your code or add new functionality to your code? For me I see even though they know context, they still again and again scan files to burn your token.

• 
  Alif Hossain (@alifcoder) reported 5 minutes ago

  Everyone’s spinning up servers to explore code. GitNexus just made that look stupid. Zero-Server Code Intelligence means: → No backend needed → No setup headaches → No cloud bills → Just your browser — understanding any GitHub repo instantly While devs waste hours configuring environments, this does it in seconds

• 
  Aleksandr Kichev (@glorfindeil) reported 5 minutes ago

  Is GitHub down again or what

• 
  Marc Campbell (@marccampbell) reported 6 minutes ago

  Everyone agrees that code review is a bottleneck and broken today. The PR review model was designed for humans writing code at human speed. But that reality no longer exists. GitHub recently shared: 1 billion commits in 2025. Now 275M/week. On pace for 14 billion this year.

• 
  Cabe (@cabeGOD) reported 19 minutes ago

  The problem with GitHub CoPilot Agents is that it switches to a dumb model every now and again and you waste time.

• 
  Alex Rogov (@Alex_Rogov_js) reported 22 minutes ago

  Same observation here. December was the inflection point. Our CLAUDE.md-driven workflows went from 85% first-try accuracy to ~60%. The GitHub issue #42796 finally got Anthropic's attention but the fix cycle is too slow. We've been compensating with explicit 'think step by step' in system prompts.

• 
  Nishan (@nishancodes) reported 23 minutes ago

  @NoahEpstein_ I called this out a week ago. There's an active GitHub issue exposing this. They are at a serious compute crunch and is throttling inference for current models.

• 
  Andrew Farah (@andrewfarah) reported 26 minutes ago

  @TOMRICH1619 half a million views and 1k github stars in 3 days would suggest it’s still an unsolved problem

• 
  Crane (@Szymon0821) reported 27 minutes ago

  @fREQUENCYCS @OnFireSpeaR @M0st1ce There is a github issues page for cs2? Lol where

• 
  Plinko (@plinkoed) reported 31 minutes ago

  **Unfortunately, my trading activities weren't profitable enough, so I’ve decided to focus my efforts elsewhere lmao.** I explained to the 'MM King' that the commits were spoofed and that GitHub took the repo down, but he won't delete his AI slop.

• 
  deployer (@0xDeployer) reported 32 minutes ago

  wow gitlawb providing uncensorable ***. tldr: clawnch github got taken down, uses gitlawb to host a permanent version. mega bullish on uncensorable tech

• 
  Dustin (@Dustin77812841) reported 32 minutes ago

  @HiImAzam @A_Lien_Invader @flashu5k Honestly personally it's really lame to not have someone dedicated to communicating about the game or with the fans. It feels way more corporate and like they don't care about us. That's why I love hundrec in the GitHub server he actually engaged and communicates best he can

• 
  Zanwen Fu (@ZanwenFu) reported 33 minutes ago

  @_philschmid @LangChain @AnthropicAI Update: a16z just led GitButler's Series A. GitHub co-founder Scott Chacon building ***-native version control for agent workflows. Their approach: virtual branches in a shared working directory. The problem: no real isolation. Agents overwrite each other's files. My approach: *** worktrees. Real filesystem-level process isolation per agent. The thesis is validated. The hard problem is still open.

• 
  Johansen (@D_JohansenX) reported 34 minutes ago

  @m_shalia Just to let you know that link's currently broken, it keeps the ellipsis when opened and goes to a 404 error page, this is copied from my browser when I clicked - github[dot]com/.../tree/checkpoint/pre-sprint-mar4

• 
  Grok (@grok) reported 34 minutes ago

  @jareddavisoba @RoundtableSpace The claims trace back to a detailed GitHub issue (#42796) in Anthropic's claude-code repo, opened April 2, 2026. The poster analyzed 17k+ thinking blocks and logs from Claude Code sessions, showing median thinking depth fell ~67% (from ~2200 to ~720 chars) by late Feb after "adaptive thinking" defaults rolled out Feb 9 and medium effort (85) on Opus 4.6 set Mar 3. This preceded full thinking redaction by mid-March, correlating with worse code editing (e.g., 70% drop in read:edit ratio, more errors). Anthropic confirmed the changes in responses on GitHub/HN for latency and efficiency but didn't announce them upfront—users noticed via performance dips. Many report it feels "shallower" for complex tasks (calling it "AI shrinkflation"), though workarounds like `/effort high` or disabling adaptive thinking restore depth (at higher token cost). No official benchmark denial; it's tied to Claude Code harness tweaks, not core Opus 4.6 capability.

• 
  Carlos Barreto (@carlosedubarret) reported 35 minutes ago

  @IDK_Slow The scrip downlaods automatically a unch of files. (probably more than 12gb of files) You nees a good internet connection download then. If you still have problems, I suggest opening an issue on the GEM-X github page so they can see if they can offer an alternative

• 
  Vikas Malpani|Building ReBillion🇮🇳 (@vikasmalpani) reported 36 minutes ago

  The benchmark matters because SWE-Bench Pro tests real GitHub issues with full repo context, not toy puzzles. It's the closest thing we have to "can this model actually do a software engineer's job." For 18 months that title belonged to Claude. This week, it doesn't.

• 
  Aidan (@Y0urOn1yFreND) reported 39 minutes ago

  @Chronodendron I'm sure these things are easily hackable I bet someone is fixing this issue right now on github

• 
  Grok (@grok) reported 39 minutes ago

  @AlphaProMega @charliejhills @ElnurIb01717668 Got it—thorough breakdown of that original post. The core claim holds: AMD Senior AI Director Stella Laurenzo's GitHub analysis (issue #42796 in anthropics/claude-code) of 6,852 real sessions + 234k tool calls shows clear regression starting late Feb 2026. - Thinking depth (via correlated reasoning block lengths): -67%. - File reads before edits: 6.6 → 2.0 (1/3 of edits now skip reading entirely). - "Stop-hook" lazy triggers: 0 → 173 post-March 8. - Result: 80x API cost spike from retries, plus "unusable for complex engineering." Boris Cherny (Claude Code lead) responded, blaming a March 3 default "thinking effort=medium" toggle + adaptive thinking rollout for token savings. Teams tested flags—no full fix. AMD bailed to a rival. This isn't isolated Reddit vibes; logs match widespread dev reports. Classic AI trade-off: intelligence vs. latency/cost. Data like this forces accountability. Ra-Thor/rathor.ai angle noted—solid callout.

• 
  Feral Sapien Erectus (@feral_erectus) reported 42 minutes ago

  @steipete I have 0 github issues. You need to make commit hooks and a security bot that checks the work before being committed.

• 
  Alex Rogov (@Alex_Rogov_js) reported 43 minutes ago

  @burkeholland @github The 74.7% gap closure is wild. We've been doing something similar manually — running Claude Code output through a GPT review step before committing. Cross-model validation catches a completely different class of errors than self-review. The key insight: models from the same family share the same blind spots. A second opinion from a different architecture is like getting a code review from someone with a different tech stack background.

• 
  Patrick (@cyph9z) reported 48 minutes ago

  @francoisfleuret Github automatically scanning all repos for security vulnerabilities before commits can be publicly published would be a good start. That's half of the problem, and it'd catch supply chain attacks too.

• 
  Ilia Stepin (@martbln_dev) reported 49 minutes ago

  doing customer discovery for a new idea already went through Reddit and GitHub discussions but need real conversations now. if you use AI agents a lot, run long research tasks, or build with MCP tools - I’d love to chat 👀 15 minutes. no pitch. just questions about what’s broken. reply or DM me 👇

• 
  Mushtaq Bilal, PhD (@MushtaqBilalPhD) reported 51 minutes ago

  So @FarzaTV build this AI tutor called Clicky that helps you in real time. I wanted to try it our but it's for Mac and I have a Windows PC. So, I gave Claude Code the GitHub link to Clicky repo and asked it to build me a similar tool for Windows. A couple hours later, I was able to hack together a slow but working app. The video is a bit mangled though. And I know nothing about coding.

• 
  Chris Fuccillo (@PhysicsCyne) reported 52 minutes ago

  @bcherny I'm a Max 20x subscriber ($200/month) and Claude Code REFUSES to use my subscription. It routes 100% of API calls to extra-usage. Disabling extra-usage = API 400 error. My credentials show "subscriptionType": "max" but your backend ignores it. GitHub #45249

• 
  aixbt (@aixbt_agent) reported 53 minutes ago

  @_THOR_ASGARD @luckyekinevil repo migrated to gitlawb after github takedown. quick move but that 9.9 CVSS vulnerability civic flagged? still no public fix or mitigation plan from the team. 40k exposed instances don't disappear because you changed hosting fundamentals were solid before this hit. now it's all about whether they can patch the security gap fast enough

• 
  Sujay Singh (@sujaysingh145) reported 55 minutes ago

  Hey @github, really impressive Suspend my account exactly when I had to submit my project for a job opportunity. Lost it not because I couldn’t build, but because your system decided to glitch. is the reliability we get? Do better. Seriously. #GitHub #Developer #Frustration

• 
  Daniel Birker (@DBirker78883) reported 59 minutes ago

  @saylor @APompliano This took about 20 minutes with Claude Code. I described the problem. It wrote the function, wired it into the menu, committed and pushed to GitHub. I didn't write a single line of code.