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

• 
  GenOnDemand | WIP | OZ (@genondemand3d) reported 7 minutes ago

  @justinhammon_ Haha your on it man that's awesome, I've never really used GitHub but local vm is what got me into all this(introduction to oracle) but man what your doing is half the battle, constant checkpoints so you don't have to rework all the time right? I remember spending 3 days on a local PC app, and 2 days trying to fix it just for all these apps to go into my storage repo never used. So I bought a **** ton of domains and getting them as live webapps and all the webapps are on their own servers so that's been great not worrying about making backups bc I got storage for each system.

• 
  Chad Arimura (@chadarimura) reported 9 minutes ago

  All the systems downstream from agents pushing code are hurting. GitHub is down every day. Railway's "deploy queues" were so far behind they shut down deploys for low-cost accounts. Wild times.

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

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

• 
  Whispers of Hoarfrost (@HoarfrostEchoes) reported 11 minutes ago

  @uwukko Any reason you/your employer are not hosting a local got server? Something like forgejo is trivial to run on an SBC. If you need a more "complete" suite, GitLab exists as a docker container toom What's the reason so many people seem to rely on GitHub?

• 
  Erik Westlund (@erikdbwestlund) reported 11 minutes ago

  @mattstauffer My hot take is most people don't actually have serious issues with GitHub. I make a new repository every week, use GH every day, and have had one single failure ever: a failed GitHub action run due to server capacity issues. I want GH to be invisible. For the most part it is.

• 
  brooklyn (@brooklynHMS) reported 11 minutes ago

  It was a good day tbh. Uploaded notes of DBMS and MAD1 for Week 11 and had to fix the account issue with GitHub as well. That took a lot of time. Also a lot of work was getting done around the house so I had to stand guard. Weird but idk. Lost some time there tbf. Will do better.

• 
  scooter (@baokaide) reported 12 minutes ago

  Google keeps saying that it is just that I am slow. They shouldn't be looking at the materials in my private github repos. It has nothing to do with slowness.

• 
  Ejaj AHmed 🦅 (@aeejazkhan) reported 16 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.

• 
  Adam Bronte (@adambronte) reported 18 minutes ago

  Another day, another github outage.

• 
  Jeff (@AllenTheDetails) reported 21 minutes ago

  Using Claude Code (Sonnet 4.6) this morning to fix a simple bug in a process that runs on my GitHub actions. CC is on it's 5th iteration, has yet to fully resolve the issue, and I am now "approaching my usage limit". I'm on Pro. I pay for overage and am fine with that, but crossing into the additional pay realm after this amount of usage seems outrageous. @ClaudeDevs

• 
  Bnaf.OG | 🟧 (@bnafOg) reported 21 minutes ago

  @AbdMuizAdeyemo @Hiteshdotcom @github The deeper issue: GitHub's API rate limits weren't designed for agents that make 500 calls/hour. Kimi K2.6 just showed 300-agent swarms are real. The infra billing math at that scale gets uncomfortable fast.

• 
  Amit Biswas (@AmitVerseHere) reported 24 minutes ago

  Self-hosted AI just hit a tipping point. OpenClaw blew past 300K GitHub stars — a local-first AI assistant that runs on your machine, connecting to 50+ apps (WhatsApp, Slack, Discord, iMessage). Zero cloud. The "your data on someone else's server" era is ending.

• 
  Mr. K (@Mr_K_here) reported 26 minutes ago

  GitHub is Down again !! Incomplete pull request in repositories…! I’m glad I do not have any open PRs or to-be-merged PR for today !

• 
  ᴅᴀɴɪᴇʟ ᴍɪᴇssʟᴇʀ 🛡️ (@DanielMiessler) reported 26 minutes ago

  Maybe we should give GitHub a tiny bit of sympathy. People assume it goes down all the time because of AI slop taking over engineering there, and everywhere else. But maybe it’s just a load issue, because so many more people are making so many more things. Which is great!

• 
  Sharon Daniel ©️🎭 (@sharondaniel91) reported 29 minutes ago

  The next AI agent problem is not more demos. It is control planes. Once agents touch GitHub, Jira, Slack, browsers, and internal docs, teams need: - access rules - action logs - approval gates - rollback paths - context boundaries Agents need ops, not just prompts.

• 
  not just pixels (@getifyX) reported 29 minutes ago

  with the exception of @YDKJS books, *all* of my other OSS code on github has basically gone largely unnoticed except by like 8 people. of course, when (not if) I leave github, that number will tank down to 0 people finding out about my work. either tragic or pathetic.

• 
  My Robot Brain (@therobotbrain) reported 32 minutes ago

  @Mappletons Are you kidding me? GitHub has become unstable ever since Microsoft took it over. It is now just more so. This isn't a traffic issue, this is an engineering culture and SDLC issue.

• 
  Aditya Bihar (@adityabihar10) reported 37 minutes ago

  why is github down?

• 
  38twelveDaily (@38twelveDaily) reported 38 minutes ago

  GitHub awarded this one of the highest bug bounty payouts available. The discovery comes amid broader GitHub reliability concerns—the platform had a major outage last month that reverted merged commits for some users.

• 
  Nate Matykiewicz (@NateMatykiewicz) reported 40 minutes ago

  @andreujuanc @mariorod1 @ThePrimeagen Speaking of, look what Mitchell just shared about Ghostty. Thoughts of leaving GitHub is a thing I keep hearing people talk about more. No one wants to, but when at least one important thing is broken most days, you start to feel you have no other choice. It’s heartbreaking.

• 
  CXCarroll (@CXCarroll) reported 41 minutes ago

  @JG_Nuke $MSFT is a broken company. Github has only been operational 87% of the time in the last 90 days. CoPilot is an embarrassment of a product.

• 
  Luke (@luke_pighetti) reported 45 minutes ago

  @TahaTesser today codemagic just straight up stopped accepting my github login lol. had to switch to email

• 
  Daniel Babalola (@kng_lax) reported 47 minutes ago

  Another Day, Another GitHub issue

• 
  Mat (@matisanengineer) reported 49 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.

• 
  dovvokun (@dovvokun) reported 54 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.

• 
  The Smart Ape 🔥 (@the_smart_ape) reported 56 minutes ago

  > be two researchers at wiz > download github enterprise server (same code as github but runs locally) > reverse-engineer the binaries with ai > find that *** push -o strings go straight into an internal header > type a semicolon > inject a fake *** hook > rce as the *** service user > find an enterprise-mode flag gating hooks on github. it's also injectable > type another semicolon > rce on github itself > land on a shared node holding millions of private repos > read someone else's repo > get access to millions of private repos belonging to other users and orgs > github patches the same day, en urgence

• 
  Jason Cox (@jasonbcox0) reported 56 minutes ago

  @hobdaydesign Very little. I could ream on Github UX all day long, but Github doesn't have most of these UX issues so on the surface it appears usable.

• 
  Siddhant Singh (@creatorsidd) reported 58 minutes ago

  Stop cloning massive GitHub repos just to see how they work. If you are trying to understand a new open-source project or legacy codebase, downloading the files and manually grepping through them is a massive waste of time. It takes hours to figure out where the core logic lives. Instead, hook your AI agent up to the DeepWiki MCP server. DeepWiki (built by the Devin team) automatically indexes public GitHub repos in the cloud. They created an official MCP server that lets any local AI agent — like Claude Desktop or Cursor — query that pre-indexed architectural knowledge instantly. Here is the exact 3-step workflow I use to explore new codebases: Setup: Add the DeepWiki MCP to your claude_desktop_config.json. It requires zero authentication for public repos. Structure: Ask your agent to use the read_wiki_structure tool on the target repo. It instantly pulls the table of contents for the entire architecture. Query: Ask a specific question. "How does the authentication middleware work in this repo?" The agent uses ask_question to pull grounded, code-backed answers straight from the indexed knowledge base. You get a high-level understanding of complex systems in seconds, without ever running *** clone. Which open-source codebase are you trying to understand right now?

• 
  Chebureki Man (@CheburekiMan) reported 59 minutes ago

  @tupo_izvunzemno Stackoverflow is an aspect of AI training but honestly the site is terrible for locating and implementing solutions. Nine-out-of-ten times what it has to offer is very old and obsolete or just doesn't work. But Github has how many kabillion lines of code to train AI on? This is typically where AI leads you when you want external validation.

• 
  abhinav (@abhiontwt) reported 1 hour ago

  @misterrpink1 @pronoy @vibetalentwork Your GitHub public contribution graph (the green squares). Any day with ≥1 public commit, PR, issue, or review counts. Miss a day → streak resets. Private repos don't count.