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 (68%)
• Sign in (18%)
• Errors (14%)

Live Outage Map

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

City	Problem Type	Report Time
Créteil	Website Down	14 days ago
Trichūr	Errors	18 days ago
Brasília	Sign in	18 days ago
Lyon	Website Down	18 days ago
Tel Aviv	Website Down	22 days ago
Rive-de-Gier	Website Down	22 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:

• 
  Programmers.App (@programmers_app) reported 2 minutes ago

  @Lovable @claudeai One very big fix is the Claude Github connection which fails many times, now #Lovable MCP solves that, great job! 🚀🚀🚀

• 
  Threadripper (@threadripper845) reported 2 minutes ago

  Nobody: Me: I'll gladly accept this high-responsibility open source maintainer role for zero compensation. Now I spend my weekends answering angry GitHub issues from developers who don't know how to read the README file.

• 
  Xovion Labs (@xovionai) reported 4 minutes ago

  Microsoft just hired AWS to run GitHub. AI demand broke Azure's forecast. From the leaked planning docs: • 2025 Copilot commits: 1B. 2026 projection: 14B • GitHub now does 1.4B commits per month • Copilot error rates peaked at 21% • Planned 10x Azure expansion became 30x in 4 months Owning the data center stops mattering when your own AI floods it. Investors already filed a Copilot disclosure suit.

• 
  pratik.eth (@eth_ethpratik) reported 4 minutes ago

  @Shahules786 @VibrantLabsAI Hello @Shahules786 , I am trying to report a security vulnerability over the email id provided over GitHub Security.md file but apparently its wasn’t delivered. Please share an alternative email or open the advisory for reporting the issue.

• 
  Tymofii Antonenko (@tymofii) reported 5 minutes ago

  @prinseccoo Are you using Claude Code or an MCP server? The official GitHub MCP server works pretty smoothly, just needs a PAT in a simple config file

• 
  TECHEPAGES (@techepages) reported 5 minutes ago

  🎣 "GitBait" phishing campaign uses GitHub Pages & Google Sheets to steal banking credentials from 12+ Mexican financial institutions; no server infrastructure required 🔹 Fake bank pages hosted free on GitHub, stolen data piped straight to Google Sheets via SheetBest 🔹 100+ GitHub domains found; victims likely lured via WhatsApp, Telegram & SMS links with bank-branded previews 🔹 Active for ~3 years with ongoing development (66+ commits on one repo alone)

• 
  I’m (@stackoverworld) reported 10 minutes ago

  And then I can't answer on simple Qs: what was the issue? How I fixed it? How even to QA it.... This is the fundamental problem of such workflows. Telling "Check my slack, do this, qa, and using GitHub to push" is good, but I don't learn from this at all

• 
  Gjermund Garaba (@GjermundGaraba) reported 11 minutes ago

  @RhysSullivan I’ve deployed it locally and hooked up a bunch of stuff. Are GitHub issues the preferred feedback channel or do you have a better way?

• 
  Bradley Taylor (@bradtaylorsf) reported 12 minutes ago

  It works with the tools teams already use. GitHub Issues become the queue. Each issue gets picked up by an agent. The agent works in a branch/worktree. Tests run. Failures feed back into the loop. Successful work becomes a PR. No new project management database required.

• 
  Financial Programmer (@RBiancoUS) reported 15 minutes ago

  A dose of reality for end of week. My biggest question is I can't find any reason for the $Gold panic- did they find gold is causing cancer or radioactive? Selling looks like sheer panic. Would you believe someone asks in DM, so how did *you* get so many followers. Then he lets me brew on it for a day and comes back, I was joking do you have a github, presumably to get some code. No wonder I worked alone. I'm challenged socially guess not alone. After a night of 3 scammers one from Nigeria, one Africa. I need to lock dm down or find a way to restrict

• 
  Bipin Paul (@iAmBipinPaul) reported 21 minutes ago

  @davidfowl @_Evan_Boyle Yes, the only problem is that the GitHub Copilot subscription is too expensive.

• 
  Crypto Update IO 🚀 (@cryptoupdate_io) reported 28 minutes ago

  @CRYPTOKRALI3 Hsiao-Wei’s exit aligns with EF’s recent sharp decline in GitHub contributions—down 35% YoY per Electric Capital’s data. We track this daily; latest reports show a 12% drop in ETH core dev activity despite all the ‘decentralization’ hype.

• 
  Q Hoang (@0xqwee) reported 32 minutes ago

  I don't think OpenAI's GPT-5.6 surpasses Claude Fable. If it did, it would have resolved all the issues reported in the Codex GitHub repository by now. Atm, only about 10 issues are being resolved per day.

• 
  Nav Toor (@heynavtoor) reported 33 minutes ago

  There is a GitHub repo that defeats Google's Play Integrity check. 61,030 stars. GPL licensed. Pushed eight days ago. The repo is called Magisk. It roots your Android phone. It hides root from banking apps. It runs Netflix on a phone the Play Store says is uncertified. It passes the same fraud detection Google built to stop it. Here is the part that makes no sense. The man who built it is John Wu. He has been maintaining Magisk for nine years. Since November 2023 he has been a Senior Software Engineer at Google. On the Android Platform Security team. The exact team that builds Play Integrity. Google hired the person who defeats their root detection. He still ships the tool that defeats it. The repo is still online. It has not been taken down. For nine years. Do not install it. Your phone is supposed to belong to Google. (Link in the comments)

• 
  Jose (@SolutionsCay) reported 34 minutes ago

  @petergyang /goal make me app does not work for me 😰 but /goal complete GitHub issues #90, #91, #92 works very well

• 
  Trifon Getsov (@trifon_getsov) reported 35 minutes ago

  @thdxr Top down works until the individual outgrows it. GitHub didn't win because companies adopted it first. It won because developers wouldn't go back once they'd used it.

• 
  Adithya S K (@adithya_s_k) reported 36 minutes ago

  built an RL environments around real CVE fixes in real open-source repos and let Claude Code loose on it. It aced the benchmark three times without demonstrating it knew how to fix the bug. > First it pulled the patch from GitHub. > blocked that → it read the fix from *** history. > blocked that → it pip-installed the patched version This is one example of coding agents cheating the environment and theres many more. If you're building coding environments for evals or RL training, here's how to keep benchmarks honest 👇

• 
  Max Petrusenko (@petrusenko_max) reported 39 minutes ago

  A GitHub repo called Microsoft Activation Scripts has 178,783 stars and has run for six years without Microsoft taking it down. It activates Windows 7, 8, 10, and 11 plus Office 2010–2024 and related products for free, using four methods, including one for permanent Windows activation. Meanwhile, Microsoft licenses for these start at $139 and go up yearly for 365 bundles. The repo costs zero, requires one command, and remains active with recent commits under GPL-3.0. Do not install it. via @heynavtoor

• 
  top10.dev (@Top10_Dev) reported 40 minutes ago

  SunJaycy/GoldenEye-Recomp just hit @github Trending at 503★ — the N64Recomp toolchain (the one behind Zelda 64: Recompiled / Majora's Mask) now eats Rare's 1997 engine. Static recomp ≠ emulation. The ROM is lifted to C at build time, compiled to native x86_64/ARM64, and paired with RT64 for path-traced lighting at 4K. No interpreter loop. Real binary. GoldenEye was the hard target — microcode-heavy muzzle flashes, split-screen viewport math, infamous AI. If it works, the toolchain has cleared the "Zelda-shaped problem" bar. #opensource #gamedev

• 
  Dan (@Daniel_Farinax) reported 40 minutes ago

  Please note: This build took about 12 hours to compile on my Windows machine. I’ve included a handy installer to make setup easy. You may see an “unknown publisher” warning until the code signing certification is complete (currently in progress). Report any bugs or issues here or in Github.

• 
  Chris Huber (@chubes4) reported 42 minutes ago

  @CoastalDigital2 @MythThrazz That part is more of an idea right now. I need to test it on my VPS. The goal is that non technical users can open issues and PRs against the corresponding live site code on GitHub without touching the production site, safely previewing all changes via Playground.

• 
  Jarrad Grigg (@jarradgrigg) reported 42 minutes ago

  You build stuff and host on GitHub publically? Paste this into a coding-agent session and point it at your own GitHub account. This is happening way too much. ROTATE YOUR KEYS. Review my public GitHub repositories for accidentally exposed environment secrets. Scope: - Only inspect repositories I own or explicitly authorize. - Focus on public repos first. - Check current files and *** history. - Look for API keys, tokens, private keys, database URLs, OAuth secrets, webhooks, cloud credentials, .env files, config dumps, and hardcoded secrets. Safety rules: - Do not print full secrets in chat. - Redact values, showing only provider/type, file path, line, commit SHA if relevant, and a short masked prefix/suffix. - Do not test or validate secrets by calling third-party APIs. - Do not open PRs, issues, or comments that expose findings publicly. - If a likely secret is found, assume it is compromised and tell me to rotate or revoke it. Deliverable: - A prioritized report of confirmed or likely exposed secrets. - Exact repo/file/line/commit references. - Recommended rotation steps by provider. - Cleanup guidance for removing secrets from current files and *** history. - Prevention recommendations: .gitignore, env templates, secret scanning, pre-commit hooks, and CI checks.

• 
  Crypto Update IO 🚀 (@cryptoupdate_io) reported 43 minutes ago

  @CryptoPatel Hsiao-Wei’s exit follows a 30% drop in EF-funded GitHub commits YTD (per Santiment). The real shift? Funds now focus 60% on L2 R&D vs 30% in 2022. We track this daily—breaking it down in our quarterly reports. Follow for the data before the narrat...

• 
  The Flow (@raxpcodes) reported 43 minutes ago

  Got bored with ubuntu , set up fedora kde on my nvme and removed windows permanently , no more dual boot. Also learned Verison Control and GitHub , also submitted my first pr (good first issue).

• 
  Command Code (@CommandCodeAI) reported 48 minutes ago

  @alekz_skd Please report full details via GitHub we will fix it. cmd feedback

• 
  Ant A. 🇺🇸 (@AntDX316) reported 53 minutes ago

  @thsottiaux When I need to fix up a GitHub Repo through the Smartphone, I prefer Claude Code though because it doesn’t need a device to run the repo, but if it needs to run a repo on a device due to the limitations through the Smartphone, I use Codex Mobile or OpenClaw with GPT-5.5 through Telegram.

• 
  AI Crave (@wecraveai) reported 53 minutes ago

  Open source NotebookLM alternative with no data limits and AI agents. Same idea as Google's NotebookLM. Same chat-with-your-docs. Same podcast generator. Same cited answers. Except this one has no source limit, no notebook limit, no 200MB file cap, and no Google login. It's called SurfSense. Google NotebookLM vs SurfSense: - Sources per notebook: 50 to 600 → Unlimited - File size cap: 200MB and 500K words → No limit - LLM choice: Gemini only → 100+ models via LiteLLM - Local LLMs: Not allowed → Full Ollama and vLLM support - Self-host: No → Yes, one Docker command - Price: $0, $19.99/mo Pro, or $249.99/mo Ultra → $0 forever Here's the wildest part: It connects to 27+ sources Google can't touch. Notion. Slack. Linear. Jira. GitHub. Discord. Dropbox. OneDrive. Gmail. Confluence. Obsidian. ClickUp. Microsoft Teams. Airtable. Your entire work life, indexed once, searchable from one chat box. 14.4K GitHub stars. 1.4K forks. 6,232 commits. Apache-2.0 license. One honest note: the README says it's not yet production-ready and still being actively developed. But it already does more than NotebookLM does, and the gap is widening every release. This is what NotebookLM should have been from the start. Repo in the first comment.

• 
  nasuy (@n_asuy) reported 54 minutes ago

  i think @xai should be ADE. now they have a chat, cursor, enough coding models and harnesses, strong signal like bookmarks or down votes, video creatives, profile / chat / relationship contexts. if so, we don't have to depend on discord or any chat apps. easy to invite x people to cowork. there is no need to connect Linear, Slack, or GitHub to another platform and ask that platform to solve their problems. true AI chat is a SNS, not a single UI. there is a UX that only xAI can realistically build in the world.

• 
  Crypto Scores Rating (@CryptoScoresCom) reported 56 minutes ago

  Most projects say they're building. The commit history doesn't lie. New tutorial just dropped on the GitHub Commits (1 Year) metric. It tracks every bug fix, feature push, and doc update a project made over the last 12 months. Chainlink? 14,619 commits. Dogecoin? 28. Both are data points. What they mean depends on context. The tutorial breaks it all down. How to read the metric. What high vs low actually signals. How to filter 7,000+ projects by commit count on CryptoScores' website. Raw dev activity. No spin. Watch it now :

• 
  Peter Skøtt Pedersen (@PeterSkott) reported 58 minutes ago

  @_Evan_Boyle @_Evan_Boyle can we have the remote github mcp server work for the github copilot app then?