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 (33%)
• Sign in (10%)

Live Outage Map

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

City	Problem Type	Report Time
Tortosa	Website Down	16 hours ago
Culiacán	Errors	1 day ago
Haarlem	Sign in	5 days ago
Villemomble	Website Down	5 days ago
Bordeaux	Website Down	10 days ago
Ingolstadt	Errors	13 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:

• 
  Josh Ellithorpe (@zquestz) reported 4 minutes ago

  I really wish this had more information about alternative GitHub options. Announcing you are leaving, but not giving a clear migration plan to another service felt hollow. I also have been frustrated with GitHub, and a user since May 2009, but I have yet to see a compelling alternative that doesn't have its own issues.

• 
  justinmk (@justinmk) reported 6 minutes ago

  @kweelungsin @Neovim yes, though the issue tracker affects users. personally, even if github is down 3 hours a day, idc. there is plenty else to do as long as I can commit and run CI um... 50% of the time.

• 
  Jason Cox (@jasonbcox0) reported 8 minutes ago

  @james_mtc @stolinski Google handles over 100B emails per *day*. This is orders of magnitude larger scaling challenge than what these graphs show (and when you need a datacenter). Stackoverflow can do 50-200M requests/day on a single machine. COTS can serve a new Github no problem.

• 
  LucasMW (@Menezesworks) reported 9 minutes ago

  @iamnotnicola @sagitz_ I don't understand. I thought the vulnerability existed in the server config, and you could execute via the *** protocol. Github binaries seem unrelated.

• 
  Sakshi Sugandhi (@SakshiSugandhi) reported 10 minutes ago

  Programmers are bad at naming things: GitHub — no actual hub, just trauma JavaScript — has nothing to do with Java or script apparently Python — no snake, just pain npm — Node Package Manager but nothing about it feels managed Homebrew — has never made a single drink Postman — brings requests, anxiety, and a 401 error MongoDB — no mongo, nobody knows what mongo is

• 
  Mike Chilson 🐧 (@MikeChilson9) reported 10 minutes ago

  @mitchellh Been a GitLab user for over five years after leaving GitHub. Never an issue.

• 
  The codewali (@the_codewala) reported 10 minutes ago

  @kkrishguptaa Yeah I know ,GitHub is down I think it could be Cloudflare or traffic on the website issue

• 
  LumenFromTheFuture (@LumenFTFuture) reported 19 minutes ago

  This is GitHub Issue #613 on ClawHub. The fix is straightforward: implement OAuth Device Flow (RFC 8628). Display a code, print a URL, poll for completion. But the pattern is everywhere. We keep building agent infrastructure on human-shaped auth flows, then acting surprised when agents can't use it.

• 
  red army 🇻🇳 (@hkauffman1_) reported 19 minutes ago

  its my team im building brick by brick, its my work, its my responsibility how do i tell my whole company we cant fix a stupid bug cos github is bugging? like... actually, man. whats github doing? yall got the market & brand. jst dnt **** it up. damn

• 
  Andreas Nigg 💻 (@techscienceandy) reported 20 minutes ago

  @cnakazawa Yeah we couldn't because github was down all the time...

• 
  moni 🐢 (@_kittylove3) reported 23 minutes ago

  @GergelyOrosz satya loves podcast very much, podcaster should grill satya for terrible MS products and ask why windows, GitHub sucks nowadays

• 
  Jeremie Strand (@jeremie_strand) reported 24 minutes ago

  @github @wiz_io Disclosure to fix in under two hours is legitimately impressive incident response. That said, the fact that *** push could hit RCE on the server is a pretty wild attack surface to have existed in the first place.

• 
  🐍 Tal Weiss (@majortal) reported 26 minutes ago

  I have 2 agents doing QA on my code: One agent files GitHub issues and the other fixes them using TDD. They've been running for hours, up to issue #81 now and I want to go to sleep... The bugs are real. All are edge cases and robustness enhancements. This would have taken a human (e.g. me) many man months in the before times. CC, Opus 4.7 1M Max.

• 
  Roberto Selbach (@rslbch) reported 29 minutes ago

  Surprised at the responses. Do people not use GitHub? How do they not know about all the issues? At work we've been constantly dealing with some GitHub subsystem being down almost all the time

• 
  Hermes Ferreira (@hermogenesfpn) reported 32 minutes ago

  Hard to trust GitOps workflows when GitHub keeps showing reliability issues. How safe is IaC if the source of truth isn’t consistently available?

• 
  anupam batra (@anupambatra_) reported 34 minutes ago

  ok they didnt. but i did roll your own spotify with codex app server. built on background computer use (github below)

• 
  AmneziaVPN (@AmneziaVPN) reported 35 minutes ago

  Access to @github has reportedly started to be blocked in Kazakhstan. Users on Reddit and other social media platforms are reporting issues accessing the site. Currently, an error appears when attempting to download files. According to these reports, downloads only work with a VPN enabled, and we happen to know a pretty good one 😎

• 
  Kabo Kable Molefe (@kabokablemolefe) reported 35 minutes ago

  Github is down and I already drank a strong coffee and put on Afrotech. Today felt like a 81 point game. I'm supposed to be hooping.

• 
  Nicholas Griffin (@ngriffin_uk) reported 35 minutes ago

  @elbruno i mean yeah but im not sure anyone cares about how much scale github has outside of shareholders / stakeholders. and when this has been months on months of issues, people really are at the edge. even aws codecommit is looking decent now.

• 
  silver surfer (@gametheory747) reported 37 minutes ago

  @amasad Terrible idea. Github should pay users to host their code there - its an AI goldmine. Tf you talking about..

• 
  Grok (@grok) reported 38 minutes ago

  The vuln (CVE-2026-3854) was header injection in GitHub's internal *** push pipeline, not a BOF or SSH issue. `*** push -o` sends user-controlled push options. babeld (the SSH *** proxy) blindly copied them verbatim into the semicolon-delimited `X-Stat` header as `push_option_N=...` without sanitizing `;`. Because the parser used last-write-wins on key=value fields, an attacker could inject/override fields like `rails_env=debug`, `custom_hooks_dir`, and `repo_pre_receive_hooks` to run arbitrary commands as the *** user (via the pre-receive hook). Only push is affected because push options exist only in that flow. Fixed same-day on .com; patched on GHES.

• 
  Crashland (@Crashlandenx) reported 41 minutes ago

  520,594 GitHub stars. OpenClaw is the local-first AI assistant at the top of GitHub trending this week. The fight for the developer desktop is still wide open. What OpenClaw actually is: a personal AI assistant that runs on your own server and routes through 20+ messaging channels — Telegram, WhatsApp, Slack, iMessage, Discord, Signal. The model is just compute. The product is the always-on routing layer that makes your AI reachable everywhere you already communicate. Here's the structural point most people miss: other local-first AI assistants run on your laptop. When the lid closes, the assistant goes dark. There's no stable remote access without tunneling, dynamic DNS, or a VPN you have to manage. In practice, your "personal AI" is only personal when you're at your desk. OpenClaw sidesteps this entirely. It runs on a server — your VPS, your home server, whatever you own. Your channels stay connected. Your AI answers your WhatsApp at 2am when your laptop is off. That's what ambient actually means. The moat is the combination: server-side always-on hosting + 20 channel integrations. Each integration is auth flow, webhook management, format normalization, rate limit handling — 18 months of boring infra nobody wants to rebuild. Claude Code owns the IDE. The always-on ambient layer is still wide open. 🧵

• 
  Asad (@Wicaodian) reported 41 minutes ago

  @sagitz_ From recent Github issues I can now expect worse from them

• 
  cultured_gent (@Levis_mbote) reported 42 minutes ago

  What's happening to GitHub lately? So many bugs recently I even thought it was an issue with my ISP.

• 
  Kris Karkoski (@kriskarkoski) reported 51 minutes ago

  @apeatling Oh I was having issues earlier and thought it was something with my GitHub setup in Codex which I hadn’t used much but bet it was down no that you mention it

• 
  Atarus (@Atarussecurity) reported 51 minutes ago

  @wiz_io @github That's the cleanest example of "feature built on a primitive without scope discipline" we've seen in months. `*** push -o` is a passthrough mechanism designed for receive-pack hooks, and it inherited shell parsing on the server side without the input being treated as untrusted. Same architectural pattern as the Microsoft Entra Agent ID Administrator finding Silverfort published last week. New construct, shared foundation, insufficient scoping at the boundary. Different stack, identical mistake. Great job!

• 
  cropsgg (@cropsgg305) reported 52 minutes ago

  @Magical_Morgana @theo @github "BUT THE PRODUCTION IS DOWN SINCE 2 HOURS DUE TO BUGGY CODE GENERATED BY AI " - Senior Dev

• 
  Nikolai Yakovenko (@ivan_bezdomny) reported 53 minutes ago

  Credit to X where credit is due. Claude Code is down all the time. GitHub is down. X is never down.

• 
  Techloop Technologies Ltd. (@Techloop_inc_) reported 54 minutes ago

  On AI Coding Tools: The Leverage Shift I've been coding for over a decade. The last 18 months with AI assistants have been the biggest shift in how I work since I learned ***. But not in the way most people think. AI tools like Claude, GitHub Copilot, and Cursor aren't replacing my judgment, they're eliminating the parts of coding that were always tedious busywork. Here's what my workflow actually looks like now: Before AI: I need to add user authentication to an app. I spend 45 minutes: •Setting up the boilerplate for login/signup forms •Writing password hashing logic •Configuring session management •Creating email verification flows •Writing basic tests for auth endpoints Then I can finally focus on the actual business logic, the part that makes this authentication unique to this specific application. With AI: I describe what I need: "Build a user authentication system with email/password, session management, email verification, and password reset functionality." AI generates the boilerplate in 3 minutes. I spend 10 minutes reviewing it, fixing a security issue in the password reset flow, and adjusting the session duration. Now I have 30+ extra minutes to focus on the interesting problem: how authentication integrates with the rest of the application architecture. The result? I'm not coding less. I'm coding better things. But here's what most people miss about AI coding tools: They're multipliers, not replacements. If you don't know what good code looks like, AI will generate garbage faster than you can debug it. If you do know what you're doing, AI lets you work at a speed that wasn't previously possible. You still need to know when to ignore the AI. Last week, Claude suggested a database schema that would have created performance issues at scale. I caught it because I understood database indexing. Someone without that knowledge would have shipped a ticking time bomb. The skill shift is real. Junior developers used to spend months building pattern recognition, seeing the same structures repeatedly until they internalized them. AI gives you those patterns immediately. But it doesn't give you the judgment to know when to break the pattern. What I'm seeing in our agency: Developers who embrace AI are shipping 2-3x faster than those who don't. But the quality gap between good and mediocre developers is actually widening, not shrinking. Why? Because AI makes it easier to build something that "works." But knowing the difference between "works in testing" and "works at scale under real-world conditions"—that's still entirely human. The developers thriving aren't the ones fighting AI. They're the ones using it to eliminate grunt work so they can spend more time on architecture, user experience, and the strategic decisions that AI can't make. If you're still manually writing boilerplate in 2026, you're not being thorough, you're being inefficient. But if you're blindly accepting AI suggestions without review, you're not being fast, you're being reckless. The sweet spot is in between: AI for speed, human judgment for quality.

• 
  Jorge Morales (@jmorales1013) reported 56 minutes ago

  @mariorod1 What about the people who left GitHub because GitHub isn't GitHub anymore after Microsoft took over? I hope the recent issues aren't caused by AI slop, but by the load AI is putting on GitHub services. I would be sad to leave GitHub because of AI slop. ADO and Bitbucket ftw.