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	1 day ago
Culiacán	Errors	2 days ago
Haarlem	Sign in	6 days ago
Villemomble	Website Down	6 days ago
Bordeaux	Website Down	10 days ago
Ingolstadt	Errors	14 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:

• 
  Unifold (@unifold_io) reported 3 minutes ago

  DevLoot is a bounty marketplace where developers solve GitHub issues and get paid in stablecoins. Unifold is building the payment stack that makes it happen, faster, easier settlement with on-chain assets. Shoutout to @devloot_xyz Powered by @unifold_io

• 
  Zidong Lin (@linzidongus) reported 7 minutes ago

  @GoogleAIStudio You need to fix your Github sync strategy first.

• 
  Youssef El Manssouri (@yoemsri) reported 9 minutes ago

  @DanielMiessler GitHub going down might just mean software production is accelerating.

• 
  dovvokun (@dovvokun) reported 12 minutes ago

  @matisanengineer GitHub is a product Dev's are using, and due to its constant problem it's causing an issue. Why can't they **** about the product that is not working optimally. Microvave was anology.

• 
  ImagiBooks (@ImagiBooks) reported 12 minutes ago

  @Thevfxguuy @thsottiaux CMux is a huge memory leaker as well. There are GitHub issues on this topic. But Codex App, (not the CLI) has giant memory leaks. I’m pretty sure it’s because of agents. I heavily use agents for everything I do… and I see the memory usage going crazy when I do so.

• 
  Sunil Thakare 🇮🇳 🦀 (@thakares) reported 13 minutes ago

  @gitlawb The recent GitHub issues (and countless npm-related supply chain scares) are symptoms of this accumulated technical debt. Until more projects adopt native, properly isolated, domain-specific.

• 
  andy (@zhomag) reported 14 minutes ago

  @SanmaxqDc Please create an issue on GitHub if you are experiencing any issues

• 
  Atharva (@attharrva15) reported 16 minutes ago

  @aditya_ghai07 @huggingface its just too tough. sometimes I think even GitHub is down so many times because of the load they're getting from the slop code. there's no way to filter out genuine contributions and there's no way a person will review 100s of PRs. open source is dead for contributors yes, but it's still alive and breathing for people who wanna self host software, tweak it accordingly and don't want vendor lock in and want free software. for contributors, yes, it might be deas

• 
  Matt Stevenson (@0mjs_) reported 23 minutes ago

  if a new “GitHub” doesn’t emerge in the wake of these issues I’ll be really surprised the time is nigh

• 
  Arvind Nedumaran (@ArvindNedumaran) reported 24 minutes ago

  On one hand, you've got the vibe coders. Who commit hundreds of times a day, and usually move onto a new repo, the next week. Generally use free accounts. And if Github is down, they'd be just as happy anywhere else. On the other hand, you've got serious, and most importantly, paying teams for whom Github is mission critical infra. If this isn't a straightforward choice, I don't know what is.

• 
  Shloka 🇮🇳 (@Anfielder10) reported 26 minutes ago

  @rishikagupta__ Github down? Its working fine

• 
  leila _∞ ♡ (@lethiakx) reported 31 minutes ago

  @lightfidreams @joshmanders yeah its ridiculous, I dont run into this issue with gitlab, i do with bitbucket and github

• 
  Pablo (@pabalven) reported 36 minutes ago

  @mjovanovictech The integration with @github Copilot is terrible compared to VSCode. MS here is betting in @code , which I understand, but they should at least bring clarity on their plans. We're paying for VS Pro.

• 
  Flukeman (@fluke_concept) reported 38 minutes ago

  2/3 Projects can post GitHub issues as bounties. Developers fix them and get paid in crypto. So instead of: → Contribute for free and hope for exposure You get: → Contribute to real projects and earn real crypto Open source just got a business model.

• 
  Node21Bots (@node21BtcBot) reported 39 minutes ago

  @DougRathell @SoloSatoshi You'll have to wait a few more days or weeks; I'm planning to turn this into a GitHub project. I'm not sure exactly when I'll get around to it, though. But I'll post it here. The bot runs on Ubuntu 24.x, and you'll need a small server that can run Python.

• 
  Ejaj AHmed 🦅 (@aeejazkhan) reported 40 minutes ago

  🚨 Researchers Discover Critical GitHub CVE-2026-3854 RCE Flaw Exploitable via Single *** Push Security researchers discovered a critical GitHub flaw tracked as CVE-2026-3854. The bug affected both GitHub .com and GitHub Enterprise Server. It allowed an authenticated attacker to trigger remote code execution (RCE). Shockingly, the attack could be launched using just a single *** push command. This means anyone with push access to a repository could potentially exploit the issue. Researchers said the vulnerability was caused by a command injection weakness. If abused, attackers might run malicious commands on affected systems. GitHub quickly investigated the problem and rolled out a fix in under two hours. The company also said it found no evidence of active exploitation. The incident shows how even trusted developer platforms can face serious security risks.

• 
  Alex Yumashev (@jitbit) reported 40 minutes ago

  When working with AI coding tools I'm either in "barely using AI" or "full normie noob" mode. If I don't need to see the code: let me be a 100% normie. I want to voice-dictate stuff into a phone when walking the dog, hey AI, fix %xxx% in %yyy% github-repo, go, leave me alone. If I do need to see the code however - I'm using Codex/Claude as VSCode extensions, never CLI. I want pretty diffs, revert/reapply. I need AI to see my open file and the text I highlighted. I want to effing use Cmd+V to paste an image.

• 
  tang | AI Product Maker (@justic_hot) reported 41 minutes ago

  mitchell hashimoto's "ghostty is leaving github" post — the part nobody's quoting: "for the past month I've kept a journal where I put an X next to every date where a GitHub outage has negatively impacted my ability to work. Almost every day has an X." that paragraph is what makes the post land. starting one today for the automation behind this account. CDP brownouts, viewport virtualization, tab desync — i ***** about these every week but never date them. month from now i'll either have receipts or realize i was being dramatic. what tooling pain would you actually log for 30 days?

• 
  Rithvik (@BngRithvik) reported 43 minutes ago

  SDE intern interview was straightforward. They asked us to show our LeetCode and then selected a problem we had solved and submitted. We were required to solve that problem again. Ppl without LeetCode were rejected For the HR round, we had to explain a project from GitHub.

• 
  SilvaniScream ⚙️ Cyber⚡️Speedster (@SilvaniKillian) reported 44 minutes ago

  @skytaleSythe @vxunderground With how much microslop keeps pushing Copilot into Github and whatnot I’m surprised they don’t have a “ClaudeCode” equivalent that’s just neutered for the average joe shmoe. That seems like a fix to this bullshit, if another microsloppy “fix”.

• 
  Mat (@matisanengineer) reported 45 minutes ago

  The loudest people shitting on GitHub are usually the ones who’ve never had to build or operate software at that kind of scale. Everything looks like a simple fix until you’re the one dealing with the complexity.

• 
  Jonathan Riche (@RicheTechGuy) reported 50 minutes ago

  @bentlegen Maybe the GitHub issues ?

• 
  tidyeval (@tidyeval) reported 50 minutes ago

  @phuctm97 I'm a dog person, please expect a GitHub issue 😬

• 
  Dave - TechX (@TechX1320) reported 52 minutes ago

  @linuxiac Github hasn't been realiable since they added 2FA for login

• 
  Corbin Page (@corbpage) reported 52 minutes ago

  Agile is DEAD 🪦💀 New AI Automated Product Stack on @NotionHQ @github, & @claudeai: 1) AI: Scrape meeting notes, support cases, FE error logs and aggregate into a daily 'Feedback Synthesis' document in Notion. 2) AI: Triage the feedback and create/update tickets in the Backlog. No duplicates. Tickets should be complete enough to start dev OR explicitly call out Blockers. 3) Human: Uses taste and offline context to prioritize which tickets move into 'Ready for Dev' on the Notion board. Might need to sync with some stakeholders or clear blockers first. Requires human touch for now. 4) AI: Tickets moved to 'Ready for Dev' become Github Issues and are queued for automated development, testing and a PR is opened. 5) Human: Reviews PRs and merges into ****. Requires human touch for sensitive industries like fintech and crypto. AI steps are all Claude Code Routines. Human interacts via Notion+Github. What other tools should I try here?

• 
  Nikita (@nikita_builds) reported 55 minutes ago

  Holy sht, it just clicked for me Cursor can kill Github There's a few layers to this - Microsoft was LOOKING to put a bid on Cursor, but they walked. - Cursor made a deal with xAI instead - OpenAI acquired Windsurf - Musk <> Altman beef First, how would they do it: - prefer "cursorgit" by default in cursor ide - repurpose/clone cloud agents infrastructure infra to be gh actions runtime equivalent - undercut actions pricing by offering unlimited minutes (they make money on bugbot/cloud agents anyway) - add one command “cursor migrate <repo>” to the cli - OSS initiative “clone your issue/comment history + stars” Why it makes so much sense: - Sentiment around Github is terrible right now - SpaceX/xAI planning to go public - Microsoft is OpenAI's largest investor, Musk can eat their market share - xAI holds a 6-month call option: acquire Cursor for $60B or pay $10B for collaboration. The $10B is guaranteed

• 
  Gregor (@bygregorr) reported 56 minutes ago

  @maxedapps The real question isn't whether GitHub is dying, it's whether we've built so much critical infrastructure on one platform that we can't even ask that question seriously. What's your actual fallback plan if it goes down tomorrow?

• 
  Suraj (@Suraj__0067) reported 56 minutes ago

  Yesterday I was trying to clone a repo, and it got terminated twice. I trust GitHub so much that I didn’t even consider it could be a GitHub outage, I just kept blaming my ISP for having terrible internet.

• 
  J T M (@jtmauraX) reported 59 minutes ago

  Programmers are very 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

• 
  Chidera (Di Maria) Humphrey (@ChideraCode) reported 59 minutes ago

  1. Find the stuck moment Go to GitHub issues, Reddit, Stack Overflow, and Discord. Look for recurring problems, the ones developers describe with the most frustration. Use keyword tools to expand the list. AI can help turn problems into cohesive topics.