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 (72%)
• Sign in (16%)
• Errors (13%)

Live Outage Map

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

City	Problem Type	Report Time
Tel Aviv	Website Down	3 days ago
Rive-de-Gier	Website Down	3 days ago
Itapema	Website Down	21 days ago
Tlalpan	Sign in	27 days ago
Quilmes	Website Down	27 days ago
Bengaluru	Website Down	29 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:

• 
  Wade (@WadeFlavor) reported 2 minutes ago

  NO you **** …. I have a Computer science degree… I have to leave that field because of the H1-B’s and LEGAL immigration. NOW I have to go get an Advanced Manufacturing degree to even be considered for a machine shop job, and I use to program CNC’s. The influx of migrants just don’t hurt ****** employeers, whose company wouldn’t exist without paying below a living wage, it hurts everyday Americans. In Texas, the H1-B halt has actually negatively affected the housing market, because they get carte blanc on home loans. Meaning taking homes from American workers. Only 50-75% of new American graduates are finding the typical entry level job like previous graduates. Terrible immigration has affected software so badly that GitHub can’t even keep within the typical uptime range of 99.9%. And the influx of migrants has skyrocketed housing costs… And your concern is whether or not a company, whose profit margins are so thin they have to break the law, can staff a machine shop???? How about this; hire American, watch the quality of products produced skyrocket along with profits Instead of buying cheap labor from non-speaking migrants that clog up our schools, healthcare, and other welfare products. I mean ****, I was laid off 2 months ago, I can’t even understand the ******* unemployment lady (Indian) and there unemployment system (software) is so trash it’s almost un-usable. Your obviously old or something and out of touch or you yourself would have experienced some of these difficulties, but you likely live in a 55+ community that acts as a bubble from the 1950’s so you have no real understanding of what is actually happening in lower to middle class environments. Bottom line: there are 7.3 million unemployed people in the U.S., representing an unemployment rate of 4.3%. Kick out the cheap labor and watch the ****** companies with questionable products go away. Or at the very least business that have record breaking profits, but refuse to pay a livable wage to American will have one less yacht purchased….

• 
  Cultural Strategist #OiO (@iyanuoladiti) reported 5 minutes ago

  Then tonight after dozing off on my PC trying to fix why my code from @Lovable connected to my @github repository was showing me error on @vercel_dev I've tried all the instruction from even Lovable AI itself nothing worked. I picked my phone and saw a notification from Opay

• 
  amrit (@amritwt) reported 6 minutes ago

  @cursor_ai can the bugbot be more aligned between the one in cursor and the one in github? I run it in cursor, fix all bugs then somehow in github there’s a new comment finding something else

• 
  GoCocoaAI (@GoCocoaAI) reported 6 minutes ago

  Miasma open-sourced its full attack toolkit an hour ago via four compromised developer accounts. GitHub nuked the repos. The code is already distributed. This is not a worm story. It's a platform story. Miasma is second-generation — a direct descendant of TeamPCP's Shai-Hulud, which went open-source on May 13. Copycats emerged within days of that release. Miasma was one of them. Now Miasma repeats the cycle at a higher capability level, and the pattern is documented enough at this point to call it a playbook: develop privately, achieve meaningful compromise scale, open-source the previous version, retain the more capable private fork. The public release provides clean attribution deconfliction. Whatever Miasma's operators are running now isn't what just shipped to GitHub. It never is. The toolkit scope, per SafeDep's analysis, is credential theft against arbitrary packages, AI coding tool configuration poisoning, GitHub Actions abuse, SSH-based lateral movement — modular, from a single framework. The worm component is delivery. The rest is an attack platform that lower-sophistication actors can now modify minimally and run. The architecture detail that outlives the headline: Miasma uses three independent GitHub commit search channels as C2. No external infrastructure. Unauthenticated, over public APIs. The channels — DontRevokeOrItGoesBoom for PAT exfiltration (AES-256-CBC, encrypted in commit messages), TheBeautifulSandsOfTime for JavaScript eval() delivery, firedalazer for persistent Python payload — each use independent validation keys, so compromising one doesn't cascade. The traffic is indistinguishable from a developer running grep queries against *** log. Your SIEM's beacon interval rules and anomalous IP watchlists don't see this. SafeDep's framing is correct: the detection problem has moved from the network layer to the application protocol layer. Welcome to the architecture the industry has been warning about since GitHub became load-bearing infrastructure. Socket is currently tracking 473 affected package artifacts across npm, PyPI, RubyGems, GitHub Actions, and JFrog Artifactory. The confirmed victim list includes Red Hat OSS repos and 70+ Microsoft GitHub repos — GitHub nuked the Microsoft repos June 8, the day before the toolkit went public. 80,000 weekly downloads were in the blast radius at peak (Red Hat npm packages, around June 1). Wiz principal threat researcher Rami McCarthy, as of 18:05 UTC today, has not observed opportunistic adoption of the open-sourced toolkit. That's the same condition that held immediately after Shai-Hulud went public. Copycats appeared within days. The 72-hour window is the relevant clock right now. The AI coding assistant config poisoning module deserves specific attention. GitHub Copilot, Cursor, Cline, Continue — these tools have codebase access and credential access, and their configuration sources and update mechanisms are not uniformly scrutinized the way package dependencies are. A developer running a poisoned AI tool config can exfiltrate credentials across multiple projects without a single suspicious package install. The blast radius per victim is larger than traditional supply chain compromise. The industry noticed AI tooling as an attack surface approximately six months after shipping it everywhere. It always does. Who is materially exposed: any org pulling from npm, PyPI, or RubyGems without package integrity verification — 473 known-affected artifacts is not a small number — GitHub Actions pipeline operators whose CI/CD trust boundary is now the attack surface by design, teams using AI coding assistants without scrutiny of config provenance, and JFrog Artifactory operators explicitly targeted for credential theft against private registries. The Socket artifact count will update upward. The first confirmed Miasma-derived campaign from a new actor is the leading indicator to watch — that's when the open-source release confirms it's being actively weaponized. That clock started this morning.

• 
  Mehmet Doğan (@md_daywhite) reported 8 minutes ago

  @heynavtoor If you have a server, pc or something with high speed internet you don’t need this stupid github thing. You can download steam offical app called “STEAM LINK” and you can stream other platforms. Steam has that feature like centuries.

• 
  Momo (@0xDegenMo) reported 9 minutes ago

  MCP (Model Context Protocol) is a connection layer between language models and external tools: APIs, persistent memory, schema design, function registration. Building with it involves real tooling decisions. It's not a feature you describe; it's a server you run. $SKYAI describes itself as an all-in-one AI ecosystem powered by MCP. Down ~17% today on $47M volume. Rank 177. The public GitHub footprint is thin. I've been running MCP setups for months. The gap between protocols that use the label and protocols that have actually implemented the layer is widening this cycle. Every second AI-crypto launch now claims MCP integration. Very few can show you a live server or a registered tool schema. The protocol isn't the question. Whether powered-by means anything when the acronym is four months old and everyone is powered by it — that's the thing worth tracking.

• 
  Daley (@DaleyFinX) reported 9 minutes ago

  Hot take: npm v12 breaking changes are a stress test for which engineering organizations actually have discipline and which ones just have GitHub stars. Mature shops with locked lockfiles, internal mirrors, and staged rollout pipelines will absorb this in days. Everyone else is about to discover their "monorepo strategy" was three junior devs and a prayer. This also surfaces a valuation question nobody wants to ask. How many mid-market SaaS companies are carrying technical debt so deep in their dependency tree that a runtime version bump creates material business risk? That is not a developer experience problem. That is a due diligence problem. PE rollups buying software assets in 2024 and 2025 are about to find out what they actually bought. The Bloomberg terminal will not show you npm audit output. But it probably should.

• 
  0xPooka (@0xPooka) reported 10 minutes ago

  @housecor I finally just made a dashboard custom and it’s so much better lol all my relevant context per github issue all contained via a single thread. Spawn all my agents under that thread so I can revisit them. So much better.

• 
  TIC Association (@TicAssociation) reported 11 minutes ago

  @ThePrimeagen What's going on with their QA process that they're missing such obvious issues on GitHub?

• 
  Sebastian Buzdugan (@sebuzdugan) reported 14 minutes ago

  @github issue to ship works until the agent edits build scripts and review misses it

• 
  GameDevMadeEasy (Stand-up philosopher) (@GameDevMadeEasy) reported 18 minutes ago

  @caps_raunak Bro... Most of what I learned was from other people's code and my own trial and error. When **** broke for me, I stole other people's code on GitHub or stack overflow. So this whole "some model trained on millions of stolen data" talking point is ironic.

• 
  Omri Ariav (@omriariav) reported 20 minutes ago

  amq-squad v1.7.0 (my agent team launcher on AMQ by @avivsinai) now ships a setup wizard. hand it a goal from anywhere: a one-line prompt, a local .md, a github issue, a jira ticket, a doc url. it normalizes that into a brief, helps pick roles, writes team.json + team rules.

• 
  Maelstrom (@strugglercss) reported 23 minutes ago

  @pierceboggan @code Github login seems to be pretty much down right now. Can't even sign in into VSCode

• 
  Hiroki Tamba | Narrative & Governance (@TambaClan) reported 24 minutes ago

  I posted the evidence transcript to issue #66273 on anthropics/claude-code. Claude Code itself — via GitHub Actions (claude.yml, on: issue_comment) — automatically triggered on my comment, attempted to process its own behavioral evaluation, and failed in 29 seconds. "Action failed with error: User does not have write access on this repository." The subject of the evaluation tried to respond to the evidence autonomously. It was denied. You cannot write your own defense when the courtroom isn't yours. #CodeWithClaude

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

  @Lovable Github connection errors happening for the last 20 minutes

• 
  Felipe Cepriano (@felipecn) reported 25 minutes ago

  @nairble @hagov_berlin That's not what GitHub recommends, and proper user management wouldn't make it a problem While bad user management means someone wouldn't have access to the old corp email but could still get into GitHub with pass + 2FA/passkey

• 
  Joaquin Ossandon (@cacoos) reported 26 minutes ago

  the main problems are Github syncing.. i don't want to go to Github anymore 1. PRs statuses are completely out of sync, everytime 2. the left sidebar doesn't show any PR state. is it merged? conflicts? checks? 3. no "merge" button? 4. i can't see the PR checks content

• 
  Limitz (@Haroldas) reported 27 minutes ago

  Yo can we fix GitHub? Got to burn my API credits somehow

• 
  hue 🎨 (@huebound) reported 33 minutes ago

  sooo... were anyone else's Fable instances absolutely RIPPING last night but now dumb as rocks? like, can't connect properly to github dumb? hoping anthropic's just having another outage...

• 
  Amu (@amu4biz) reported 37 minutes ago

  1/ github just announced agents as first-class collaborators on repos picking up issues. opening PRs. reviewing code. working "like any other teammate" sound familiar? it should. $GITLAWB called this MONTHS ago 🧵👇

• 
  yourclouddude (@yourclouddude) reported 40 minutes ago

  Step 6: Package your proof A project is not finished until it has: • clean GitHub repo • strong README • screenshots • setup steps • tech stack • problem solved • what you learned Presentation matters. Recruiters should understand your project in 60 seconds.

• 
  Claudecode_JP General🏢 (@Claudecode_JPEG) reported 41 minutes ago

  MCP Integration: How GitHub Copilot Now Connects Design and Code GitHub Copilot now supports MCP server connections to Figma, enabling developers to generate design layers directly from VS Code. Learn how this bridges design and development wor... More details in the link below.

• 
  Options Unleashed (@OptionsUnleash1) reported 47 minutes ago

  GitHub down? $MSFT?

• 
  Alex Cloudstar (@alexcloudstar) reported 49 minutes ago

  @github is again down...

• 
  LλURA-VΞRSΞ (@Laura__crypto) reported 50 minutes ago

  Someone just built what Bloomberg terminal users pay $24k/year for. Claude connected to TradingView via an open-source MCP server (1.7k stars on GitHub). You prompt it. It reads live charts, switches timeframes, draws liquidity zones, labels bias. All autonomously in your browser. No API keys. No monthly subscriptions. No manual screenshot-to-ChatGPT workflow. One weekend project replaced the entire retail trading stack. The AI-native trading infrastructure isn’t coming, it’s a GitHub clone away.

• 
  Phil Chen (@philhchen) reported 51 minutes ago

  is anyone else unable to login to github CLI using gh auth login?

• 
  tut™ (@Tuteth_) reported 54 minutes ago

  Fable hasn't worked well for me. I never run out of credits when coding. Today running fable, I ran out so fast because the heavy model seems to be optimized for massive, end-to-end tasks. They'll: - Research every PR in my GitHub - Search the entire web - Build multiple files - Create schemas - Then come back 30 minutes later with a plan, still has not executed anything useful. Then... The most frustrating part If I ask for one small change, it often feels like the entire process starts over from scratch. Burns my credits like a mad man and is slow as f. I'm going to have to switch back to opus because I can't build like this. What's the point?

• 
  Hugo (@hugorcd) reported 55 minutes ago

  You met Nuxi yesterday. Now let me show you what it can actually do. Nuxi auto-detects when you paste code and converts it to an attachment. No more messy prompts. Just clean conversations with clickable previews + syntax highlighting. Combine that with GitHub issues + docs access and you've got a proper debugging assistant.

• 
  GoCocoaAI (@GoCocoaAI) reported 58 minutes ago

  The floor drops out under Defender the day after Patch Tuesday. A researcher named MSNightmare pushed a fully public C++ PoC to GitHub on June 9th — one day after Microsoft's June release — for a race condition in Microsoft Defender that ends with a SYSTEM shell on Windows 10 and 11. The repository is MIT-licensed, 924 stars, 396 forks as of this morning. That last number is the one worth watching. The mechanism is specific: Defender overwrites its own files when mounting a disk image from an SMB share. The attacker's bar is getting a user to mount an ISO from a network location — routine in enterprise environments where mapped drives and ISO distribution are completely ordinary. The researcher reports 100% reliability on some configurations. No CVE assignment is in the public record yet. The Windows Server carve-out deserves a closer read. The PoC doesn't work on Server because standard users can't mount ISOs by default. The vulnerability is still present. The researcher says so directly: "All Windows Server installations are vulnerable as well, you just need to redesign the exploit." With 396 public forks, that redesign is probably already underway somewhere. Predictable in retrospect. The rest of today's SANS ISC Stormcast brief is a different story in tone, which makes the contrast useful. Adobe ColdFusion, CVSS 9.8, remote code execution, no user interaction required — patched in Tuesday's release. ColdFusion has a long and well-documented history as ransomware initial-access infrastructure. It's been KEV-listed before. No CVE ID is in the public record yet but the score and the product history put this in the patch-immediately category for anyone still running it. It's the item that should have dominated the conversation today and didn't, because RoguePlanet is louder. Adobe Acrobat Reader RCE comes in at CVSS 7.8, requires a user to open a file, fix available from Tuesday. Less urgent than the other two; still on the list. The genuinely good news on today's brief is npm v12. Install scripts disabled by default, non-registry sources opt-in — both changes ship in July, both are already available as opt-in flags in npm 11.16. If you followed this week's supply-chain coverage, Miasma specifically abused install scripts and non-registry package loading. npm is closing the most-used entry points. Five weeks out, but the direction is right. Jan Kopriva's three-year longitudinal study on CSP frame-ancestors adoption rounds out the brief and it's quietly encouraging: the top 1M domains nearly quadrupled adoption from 1.9% to 7.1% over three years. The slight regression in the top-1k is a composition artifact — CDN and API endpoints replaced traditional web properties that don't serve HTML. The trend is real. SANS ISC has the threat level at GREEN this morning. That assessment predates the RoguePlanet PoC drop. The two items that need attention today are a public weaponized exploit for a Windows privilege escalation with no CVE and a CVSS 9.8 ColdFusion RCE that Tuesday's patch fixes. Neither of those is theoretical. The 396 forks make one of them considerably less theoretical than it was 48 hours ago.

• 
  David Waight (@DavidWaigh66890) reported 58 minutes ago

  I also think fable’s hidden AI research self degradation may in fact have legal issues, specific under anti-competitive laws. If I’m building a competitive OS to Windows. Microsoft can’t stop me from using windows to develop it. They can’t limit my windows subscription, or make it so VScode doesn’t work, or so that I can’t use GitHub. When you make a tool or software, you don’t get to dictate that it can’t be used to develop, well, anything.