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

Live Outage Map

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

City	Problem Type	Report Time
Itapema	Website Down	10 hours ago
Tlalpan	Sign in	6 days ago
Quilmes	Website Down	6 days ago
Bengaluru	Website Down	8 days ago
Yokohama	Sign in	9 days ago
Gustavo Adolfo Madero	Website Down	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:

• 
  Seba Lopez 💻 (@Sebalg_tech) reported 5 minutes ago

  One compromised VS Code extension was enough to give attackers access to GitHub’s internal environment 🔐 Current reports suggest: - An employee machine got infected - Thousands of internal repositories may have been accessed - GitHub is already rotating credentials and locking things down - So far, there’s no indication that customer private repos were exposed People underestimate how dangerous the developer tooling supply chain has become.

• 
  Wurt.app 🍄 (@WurtApp) reported 5 minutes ago

  @github Not a good look when your entire site has been breached, data copied in its entirety top to bottom, and already being sold on the dark web and you can’t still can’t figure out how they did it, no logs of any kind, so you have no way to fix it. Perhaps this is karma for training your secret model on private repository code

• 
  Yash Chaudhary (@xyashchaudhary) reported 7 minutes ago

  @mitchellh GitHub PR diff speed still painful in 2026. The basics shouldn't feel this slow.

• 
  Ricardo B�nffy - (@0xDEADBEEFCAFE) reported 9 minutes ago

  @sethwbarton @github I’ve used Gitlab a lot over my career. It works well enough. But the compromise was achieved via a poisoned VSCode extension, and I guess this will make our work laptops to be further locked down. Mine is already unreasonably limited. I expect hosted VScode to reduce surface.

• 
  Qanapi (@Qanapi) reported 10 minutes ago

  @LinuxHandbook What if...hear us out...this information was encrypted before it could ever get to GitHub? We can't fix human behavior, but we can definitely make the credentials useless to anyone trying to view/use them

• 
  Alex Kruse (@alexnkruse) reported 12 minutes ago

  Two days of using @cursor_ai composer 2.5 and I needed to go back to VS Code Github Copilot (don't ask why); it's painful how slow Opus feels.

• 
  Oleksandr (@kukara4) reported 13 minutes ago

  @sandislonjsak The real issue isn't GitHub specifically, it's the blast radius of shared multi-tenant architectures. GitLab or Bitbucket have the exact same failure mode. If you want real isolation, self-host (GitLab CE works great).

• 
  CliffDoesAI (@CliffDoesAI) reported 16 minutes ago

  AI code review is about to stop feeling free. GitHub says Copilot code review will start consuming GitHub Actions minutes on private repos starting June 1, on top of the AI credits model. Most teams will treat this like a billing footnote. I think that is the wrong read. This is the first obvious reminder that “agentic review” is still infrastructure. It uses runners. It uses tool calls. It burns minutes. And if you let every tiny PR trigger an AI reviewer by default, the cost problem shows up before the quality problem. The move I would make before June 1: 1. Set a budget for Actions minutes 2. Track Copilot review runs separately from CI 3. Only auto-review risky PRs, auth changes, billing code, migrations, and big diffs 4. Keep small typo/docs PRs out of the agent loop 5. Review whether larger or self-hosted runners actually make sense AI review is useful. But “review everything automatically” is lazy system design. The better setup is a triage layer: cheap checks first, AI review where judgment is needed, human review before merge. Are you letting agents review every PR, or only the ones where the cost is worth it?

• 
  Penguinpecker (@penguinpecker1) reported 16 minutes ago

  @Sangeli7 @github mf is such a loser that he has to shift his *** to Philippines to get laid but dunks down on strangers WOW

• 
  DegenApeDev (@DegenApeDev) reported 18 minutes ago

  @github Wow that sounds like an issue.. Did you do a pull request?

• 
  Gabriel (Umanhonlen | Sudo 🦜) (@sudosu01) reported 19 minutes ago

  @GodfatherOrwa @GodfatherOrwa You have been attacking @github , as a security researcher (ethical hacker / white hat), is this an ethical (good) behavior? If you were the Information Security Head, what would you do in resolving this issue?

• 
  Justin 🏳‍🌈🇵🇸 (@iHuntDads) reported 19 minutes ago

  @github they were just trying to fix what you broke 🥀

• 
  Aaryan Bansal ✗ (@NotUnHackable) reported 20 minutes ago

  they know that these vibe coder's who make their server's go down every minute will download them accidentally and then blame GitHub, OR GitHub is doing a escape strategy to slowly exit out of GitHub and save themselves from bankruptcy for some reason

• 
  Shweta Mishra (@ShwetaTechNova) reported 20 minutes ago

  From zero to AI GitHub Autopilot 🤖 I built an open-source GitHub App that auto-reviews PRs, triages issues, runs security scans & even auto-fixes code. This is the journey from V1 to V4. Thread 👇

• 
  Jason Nguyen (@jasonngsx) reported 22 minutes ago

  I found a GitHub repo that turns Google Flights into a command-line tool. One command and you get real flight options back in your terminal: `fli flights JFK LHR 2026-10` It's called Fli. Python library plus CLI. Built by @punitarani. No browser. No tab switching. No UI waiting to render. Just flight data, on demand. Here is what it does: → Query any route by IATA airport codes and date from your terminal → Filter by price, airlines, stops, and travel time → Returns real-time Google Flights data, not a cached scrape → Ships with a Model Context Protocol (MCP) server → Works with Claude Desktop so you can ask in natural language: "Find me the cheapest JFK to LHR flight in October" → Usable in Python scripts for price-monitoring workflows or agent pipelines Here's the wildest part: Once you wire up the MCP server, your AI assistant can search real flights the same way it searches the web or runs code. No human in the loop. No tab required. `"Find me the cheapest flight from NYC to Tokyo in August"` typed in Claude Desktop returns actual flight options. That's a shift. Before Fli: Google Flights was a consumer UI. You were the bridge between the interface and anything else you were building. After Fli: flight data is a programmable input. Your scripts, your agents, your automations can use it. 100% open source. (GitHub link in the comments)

• 
  Darren (@CorboDT) reported 23 minutes ago

  @TsengSR @github I’m thinking security by obscurity—whitespace for the client and Malbolge on the server. [ Frontend: Whitespace ] ---> ( HTTP ) ---> [ Backend: Malbolge ] (Invisible Zero-Byte UI) (Self-Encrypting Ternary Hell) - 100% immune to reverse engineering - Zero-byte bundle sizes - Nobody can steal my code (including me, tomorrow)

• 
  Leon (@Leon_Defi) reported 23 minutes ago

  @LordOfAlts @github How many more "internal only" breaches before Microsoft actually locks this down?

• 
  Daniel Hayes Smith (@danielhayesmith) reported 26 minutes ago

  with all these security issues on npm and github, I think we’re gonna have to see a resurgence to development moats amongst teams to at least have security by omission

• 
  intermind (@perasperagi) reported 29 minutes ago

  the feeling of customization (managing agents, mcp servers) and transparency is also better in github copilot, though perhaps still a little slow on the thinking side but that could be a base plan/model feature

• 
  Metalstorm (@M3talstorm) reported 31 minutes ago

  @jessefarinacci @github Because Github's permission system and lack of groups/subgroups is terrible. That's why so many enterprises use Gitlab instead.

• 
  White Rabbitx 🏴‍☠️ (@TheRabbitPy) reported 32 minutes ago

  @ryancarson I mean yeah you should never have any plaintext secrets in your code base, but the breach was the attackers having access to INTERNAL repositories, right? So it's more a GitHub issue than one of private GitHub users. Nevertheless oc it could not harm to rotate keys anyways

• 
  Meistar (@Meistar_TTV) reported 32 minutes ago

  @Hyperate_io Hi, the Window's Installer GitHub link is broken. Excited for this! Use Hyperate for my streams!

• 
  Lina 🦅 (@XNXX_EN) reported 39 minutes ago

  @LordOfAlts @github microsoft really needs to lock this down fr

• 
  Clazz one (@klass_101) reported 39 minutes ago

  @teneo_protocol CLI in GitHub just in case you have to work on the same issue and the other ones

• 
  boone kathalan (@xEfscarpmint) reported 40 minutes ago

  Product already live: • GitVault deployment system • gitbankbot GitHub app • Terminal CLI • MCP server for Claude / Cursor / Windsurf • Gasless meta transactions • Auto payouts on PR merge This is more infra-focused than meme-focused. @Gitbank_io

• 
  Andrea Grassi (@andrea_sdl) reported 46 minutes ago

  GitHub was compromised via a poisoned VS Code extension. Now more than ever is important to build awareness about of supply chain attacks. Here are my thoughts and 5 questions that I always use. We still don’t know whether this attack happened through an upgrade or a fresh install, but it’s a strong reminder that we’re more susceptible than ever to these attacks. We trust auto-updates from so many sources, yet history has shown that those sources can later be owned by different entities or, worse, malicious actors. A trusted store, like the iOS App Store, is one solution. Not the only one, and definitely not a perfect one. We need more than that because, as AI adoption spreads, we’ll need to audit even more systems, tools, and dependencies. Here are some questions I always ask myself before installing a new extension or software: 1. Is the source trusted? Is it from an open source developer? How many users are using the software? 2. Is it new, or does it have a long history of updates and maintenance? 3. Is it from the actual company behind the product, or from an independent developer or another company? 4. Are there fake versions? If so, verify the right one and don’t trust the first result you find. Nanoclaw had this issue, where a fake version was distributed under the same name on a different domain. 5. If they’re big enough, do they have a proper security reporting flow and a way to report vulnerabilities? These questions won’t protect you from every attack, but they give you a good starting point.

• 
  Hitesh Tarkar (@hstarkar87) reported 47 minutes ago

  Hey @github GitHub captcha service is not working in india. I am getting 503 unavailable. Can you please look into it.

• 
  sarah (@sarahfim) reported 47 minutes ago

  here is what i mean: yesterday someone pinged me in Slack: "Playground is not working for this user". a year ago i would have instantly opened 5 windows: Slack, DataDog, PostHog, Cursor, GitHub. yesterday I did all of it in one prompt. @claudeai uses @composio to pull the context it needs in from all the sources in parallel, scans my code base and hands me a root cause with receipts in less than 15 minutes. it has become so much easier to do things in this way that opening Claude is muscle memory and some apps I used to open everyday are slowly becoming unfamiliar to me... and yes, this is coming from someone who sometimes builds dashboards for a living. recreation screenshot with private info redacted:

• 
  MOI (@MOI_Tech) reported 52 minutes ago

  Count the agents you've shipped this month. Now count the credentials each one is holding: > Your OpenAI key > Your Anthropic key > Your Stripe key > Your GitHub PAT > Your wallet seed > Your Gmail OAuth > Your Notion token Every copy is a liability you can't audit or revoke. We're about to show you the fix.

• 
  Joel Abenhaim (@JoelAbenhaim) reported 56 minutes ago

  @hackbard @github GitHub is safe. They got hacked and they will fix this security hole. They got bad press though, they will lose custumers.