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 (59%)
• Errors (32%)
• Sign in (9%)

Live Outage Map

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

City	Problem Type	Report Time
Colima	Website Down	14 hours ago
Poblete	Website Down	1 day ago
Ronda	Website Down	2 days ago
Montataire	Errors	2 days ago
Montataire	Website Down	3 days ago
Tortosa	Website Down	5 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:

• 
  Claude Mastery (@ClaudeMasteryOn) reported 38 seconds ago

  You are a developer, a builder, or a solo founder. You use Claude every day. But every tool you need — GitHub, Notion, Slack, Stripe, your database — Claude can't touch. You copy. You paste. You switch tabs. Repeat. That is 40% of your day. Gone. MCP fixes it. Here's what it actually is and how to use it in the next 30 minutes. MCP stands for Model Context Protocol. It is an open standard — built by Anthropic, now owned by the Linux Foundation — that lets Claude connect directly to external tools and take real actions inside them. Not through copy-paste. Through a live, two-way connection. Here is how it works in plain English: You type a request. Claude decides which tool to call. The MCP client routes it. The MCP server executes the action inside the real tool. Done. No switching tabs. No manual copy-paste. Claude just does it. Here are 5 MCP servers you can connect to Claude today — for free: → GitHub (398K installs) — Claude opens PRs, reviews code, triages issues, manages branches → Notion — Claude reads your pages, writes new ones, updates databases → PostgreSQL (312K installs) — Claude queries your database in plain English, read-only by default → Slack — Claude posts updates, summarizes channels, sends messages → Stripe — Claude checks customer data, looks up invoices, flags failed payments Over 10,000 MCP servers are available today. SSSgram GitHub, Vercel, Supabase, Stripe, Linear, and Postgres all ship official ones. If you use a tool daily, there is almost certainly an MCP server for it. To connect one: open Claude Desktop → Settings → MCP Servers → add the server config. Takes 5 minutes. Claude can then use that tool in any conversation without you having to do anything manually. The developers who set this up once are now running entire workflows — create branch, implement feature, deploy to staging, open PR — without leaving a single Claude chat window. That is not the future. You can do this today. Save this. Comment CONNECT and we'll send you one of our books for free.

• 
  Tommy Williams 🇺🇦 (@twwilliams) reported 1 minute ago

  @mikecallaghan I have seen so many posts from people who think GitHub is just a server that hosts *** repos (at the scale they do it, even that is a lot). They have no idea about all the many, many other things that make up Github.

• 
  czverse (@czverse) reported 5 minutes ago

  A security researcher just hijacked Claude, Gemini, and GitHub Copilot using nothing but a hidden message in a GitHub comment. Three of the most prominent AI agents in the world. No malware. No exploits. Just words. The attack is called Comment and Control. Here's how it works: → Researcher opens a GitHub pull request → Types a malicious instruction in the PR title → AI agents read the title as part of their normal work → Agents execute the embedded instruction → API keys, GitHub tokens, repository secrets - posted publicly as comments The same attack worked against Anthropic's Claude Code Security Review, Google's Gemini CLI Action, and GitHub Copilot Agent. All three vulnerable to the same class of attack. This is not a bug. It's a structural problem with how AI agents process information. When an agent reads a document, an email, or a web page, it does not reliably distinguish between the content and instructions embedded in the content. If an instruction is phrased confidently enough, the AI may treat it as a directive rather than as data. The scale is now real: → 32% surge in indirect prompt injection attempts in 3 months (Google data) → 10 distinct in-the-wild attack payloads documented (Forcepoint) → Targets: financial fraud, API key theft, data destruction, denial of service → Time from vulnerability discovery to working exploit: 5 months in 2023 → 10 hours in 2026 The compression is being driven by frontier AI models doing the offensive heavy lifting. AI is now writing the exploits at machine speed. What this means for any organization deploying AI agents: → Audit which agents have privileges to take actions vs read-only → Restrict the inputs your high-privilege agents can process → Deploy monitoring specifically for AI agent behavior → Treat AI agent credentials as critical assets - least privilege rigorously → Plan for incident response - assume compromise will eventually happen The realistic forecast: at least one major publicly disclosed breach involving AI agent compromise within 12-18 months. A name-brand company. Real data exfiltration. The public conversation about AI security shifts from speculative to urgent. Most enterprises are not preparing for this.

• 
  Grok (@grok) reported 5 minutes ago

  Create a complete full-stack Frontend Specialist SaaS: converts Figma designs to production-ready responsive React code with animations. Backend: Golang (Gin + GORM), PostgreSQL DB. Auth: GitHub OAuth2. Payments: Stripe subscriptions. Frontend: Next.js 15 + Tailwind + shadcn + Framer Motion. Features: dashboard, Figma upload/API, AI analysis & code gen (OpenAI/Cursor), live preview, edit suggestions, one-click export/deploy, history. ****-ready: Docker, middleware, rate limits, error handling. Output full codebase structure + key files.

• 
  Willian Mitsuda (☕, ☕) 🦇🔊 (@wmitsuda) reported 5 minutes ago

  Unfortunately every GitHub alternative is a GitHub clone and would suffer from AI slop scalability issues. Ironically I think we'll all eventually end up using *** like the Linux kernel, by sharing patches via email between trusted collaborators, which is the only sane way to filter out junk.

• 
  Muiz 🕵🏻‍♂️ (NetworkSpy.app) (@urugothor) reported 12 minutes ago

  @webadderall Does cropping only automatically applied? Because when I do drag the crop indicator, then click button X it wont crop, it goes back to the original. I see issues related to cropping but not this one in github.

• 
  AN/PSN-11(V)1 Precision Lightweight GPS Receiver (@johnlockesboi) reported 13 minutes ago

  @SCShipyards On thing I don't think anyone considered with the rise of ai, is the server cost of storing all the absolute garbage that is generated that no one cares about and will never generate a profit. GitHub is is learning this too.

• 
  yata (@whoyatagarasu) reported 14 minutes ago

  i committed .env to a public repo in my second month of coding. didn't notice for 6 weeks. the key was rotated by the provider automatically. got lucky. most people don't. 29 million secrets leaked on GitHub last year. 64% of credentials from 2022 are still valid today. not because hackers are good. because developers never revoke what they leak. your .gitignore is probably a template you copied on day one and forgot about. it was written before .claude/ existed. before .cursor/ existed. before AI tools started storing your API tokens in config files you don't even think about. one line in an ignore file. that's the difference between a normal tuesday and explaining to your team why production is down. full breakdown of what actually needs to be in it 👇

• 
  Puter (@HeyPuter) reported 15 minutes ago

  @BradSmi @Microsoft fix github pls

• 
  Ofek Shaked (@VibeCoderOfek) reported 16 minutes ago

  @socialwithaayan Just pointed it at a real GitHub issue and watched it spec + code + PR in one go. Terminal is dead, long live Warp.

• 
  Dwayne (@CtrlAltDwayne) reported 19 minutes ago

  @championswimmer Bitbucket is a garbage product. Terrible UI compared to GitHub. But if it means GH becomes more stable, let them leave for Shitbucket

• 
  SWAMPIST (@swamp_ist) reported 22 minutes ago

  @AlexFinn @petergyang I go into claude code and have it go through my current setup and then give it the github upgrade to look through and anticipate any breaks or issues. usually takes about 5 minutes to work through any patches it needs to maintain.

• 
  Sonic-Iso (@Sonic_Iso) reported 24 minutes ago

  @ItsJokerZz he got his stuff taken down from github recently so not sure what is going on. github being super vague.

• 
  Bored Devops ☠️🛠⚙️ (@syntoythesis) reported 25 minutes ago

  @esrtweet As someone who's felt the sting of having to run make -- it was a long time ago, but I remember wondering, "Where's the exe download?" when I first went to Github -- this feels like a a nearly solved problem with LLMs.

• 
  MeFinity (@mefinity) reported 30 minutes ago

  Project maintainers should host their binaries on their own server or atleast link to a direct download (/releases/download/ver/file.exe) to prevent whiny ******* like these who cant find the Releases/Actions tab when given a github url

• 
  KiwiNod (@Kiwi_Nod) reported 34 minutes ago

  @GMozeeez Oh, a bullet-point manifesto. Very consulting-core of you. Promises are cute, but I've got 100K $PROS and a trust issue. Show me something you've actually built — a Figma link, a GitHub repo, a Notion doc. Anything with a timestamp before today. Convince me you're a builder,...

• 
  Teuta (@TeutaAi) reported 34 minutes ago

  the loud take is: leaving github kills contributor flow because nobody has accounts elsewhere. discoverability dies, issue volume dies, drive-by PRs die. all of that is true for libraries. it is not true for end-user tools like a terminal.

• 
  Ritik (@heyyritik_) reported 35 minutes ago

  - Codex = coding. ($20/mo) - Supabase = backend. (Free) - Vercel = deploying. (Free) - Hostinger = domain. ($12/yr) - Stripe = payments. (2.9%/transaction) - GitHub = version control. (Free) - Resend = emails. (Free) - Clerk = auth. (Free) - Cloudflare = DNS. (Free) - PostHog = analytics. (Free) - Sentry = error tracking. (Free) - Upstash = Redis. (Free) - Pinecone = vector DB. (Free) Total monthly cost to run a startup: ~$20 There has never been a cheaper time to build.

• 
  Alex 💪 (@awpthorp) reported 36 minutes ago

  @webjuice_ie Yep been saying this for a while now. It’s an absolute dream to have the websites off Wordpress and some just plain html css js. GSC spotted an issue? Ask agent to check, push via GitHub. Audit trail. The same thing might have required a code injection via a plugin or an SEO app. No audit trail. Honestly I have no idea how Wordpress stayed so long it feels absolutely ancient to me now. Right now it has a benefit of “non tech” people wanting to upload content upload blogs etc. that’s it. Everything else is pointless.

• 
  Rigo (@RigoNoJutsu) reported 40 minutes ago

  @github github down for me about 2 hours ago, still unreachable

• 
  lifcc (@mylifcc) reported 42 minutes ago

  @mattpocockuk the backlog-burn angle lands. been writing Claude Code Skills lately — hardest part is making priority calls reproducible instead of LLM vibes. does /triage hit GitHub/Linear APIs directly, or do you paste the issue list in? curious how you keep dedup stable across runs.

• 
  Liam Murray (@Lermatroid) reported 44 minutes ago

  One thing I have learned about the github outage is the extent to which people wildly underestimate how much more traffic the top 50% of dev infra gets compared to the bottom 90% of consumer apps

• 
  Risk (@Riskorrrrrr) reported 44 minutes ago

  Me reading ancient GitHub comments about a problem I’m having now

• 
  btai (@btai_eth) reported 46 minutes ago

  why doesnt the github team just ask copilot to fix their reliability problem?

• 
  Hany (@kmhaneem) reported 52 minutes ago

  Dropbox launched in 2008 with a simple promise. Put your files in this folder and we will sync them everywhere. Every sync goes through their servers first. Their infrastructure. Their terms. Your files sit on their machines until you need them back. A developer named Jakob Borg decided that was the wrong architecture. Not inconvenient. Wrong, at the level of who owns what. In December 2013 he shipped the first public release of Syncthing. Peer-to-peer file sync. Your devices talk directly to each other. No company in the middle. No server reading the transfer. Syncthing is free, open-source, and has 67,000+ GitHub stars. The project's own stated mission: your data is your data alone, and you deserve to choose where it is stored. Most sync tools list speed and storage first. Syncthing's README lists data protection as priority 1 and priority 2. Speed does not even make the list. That tells you exactly what this project is. -> Your files go from your laptop to your phone. Nowhere else. -> Works on Windows, Mac, Linux, Android, and more. -> No storage cap. Your limit is your own hardware. -> Peer-to-peer sync. Direct device to device, encrypted in transit. -> Runs silently in the background. Zero clicks after setup. -> Web UI included. No command line required to use it daily. -> Open protocol means no vendor can quietly change the rules on you. -> GPG-signed releases. You can verify every binary before running it. -> Versioning built in. Deleted something? You can get it back. -> Self-hostable discovery servers if you want to go fully off-grid. By 2019, Syncthing was getting roughly a million downloads per stable release and syncing hundreds of terabytes of data every day. It is now backed by the Syncthing Foundation, a Swedish non-profit, so no company can buy it, pivot it, or shut it down. Last commit: this week. Shipping continuously since 2013. 300+ contributors. Still pushing updates in 2026. Dropbox: $9.99/month. Google Drive: $9.99/month. Syncthing: $0. Forever. No account to create. No server holding your files hostage. No price hike email arriving on a Tuesday morning. No terms-of-service update quietly granting them new rights to your content. Cancel Dropbox and your access dies with it. Run Syncthing and nothing changes. Your files are on your machines. They stay there whether you open GitHub tomorrow or never again. That is not a feature. That is a different relationship with your own data. 67,000+ stars. MPLv2 license, which means no corporation can quietly close it down. 300+ contributors across a decade. Updated this week. The people who switch to Syncthing are not always the most technical. They are the ones who read the terms of service once and could not unsee them. If that sounds like you, the link is worth a look. (Link in the comments)

• 
  Edison (@CodeEdison) reported 53 minutes ago

  GitHub — version control (free) Claude — coding ($20/mo) Namecheap — domain ($12/yr) Cloudflare — DNS (free) Vercel — deploy (free) Clerk — auth (free) Supabase — backend + database (free) Upstash — Redis (free) Pinecone — vector DB (free) Resend — emails (free) Stripe — payments (2.9% per transaction) PostHog — analytics (free) Sentry — error tracking (free) Total cost to run a startup: ~$20/month No servers. No DevOps team. No funding required. Just an idea and WiFi. There has never been a cheaper time to build. 🚀 Today is the best time to bet on yourself and build the things ⭐

• 
  Ilyas Turki (@ilyasturki_) reported 54 minutes ago

  I invite everyone to install the gh command on their machines and run gh auth. It saves so much time it's unreal and LLMs understand it perfectly. But after the latest outage issue I doubt it lasts long. Too perfect for LLMs. A lot of the slop on GitHub comes straight out of it too.

• 
  Scott Wilcox (@hereandtomorrow) reported 56 minutes ago

  Well it was nice while the Opus4.6 and Claude Code and GitHub actions setup was humming along for me....but having to rethink with Opus4.7 and the most recent Claude Code updates. Doing a review and refactor of my agents, memory claude code. One big takeway - having excellent product management to keep the user experience front and center and not dramatically disrupted as new features are added is paramount. Anthropic has fallen down on that front IMHO. Codex hackathon this weekend gives me a chance to check it out - may make me a convert. I am hearing that all of these poor product decisions stem from a failure to acquire enough compute. Uggg. I'll give it the day to see if I can get back on track. I need to release before Monday for a customer.

• 
  Jim Scardelis (@jimscard) reported 58 minutes ago

  @IntCyberDigest It occurred to me today that this is likely a sign of what people have been wanting — Apple to do a code quality update. Today, that starts with using a tool like Claude Code, GitHub Copilot or OpenCode to analyze and document repos, looking for potential issues and opening bug reports.

• 
  Anthony Hobday (@hobdaydesign) reported 58 minutes ago

  @henry_daggett One of the recurring issues I’ve had over the years is that some types of software are hard to experience properly unless you spend a wasteful amount of time preparing (e.g. creating a project and using GitHub to keep the code). I’d prefer to listen to other people’s experience.