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	22 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:

• 
  GameDevMadeEasy (Stand-up philosopher) (@GameDevMadeEasy) reported 23 seconds 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.

• 
  Mehmet Doğan (@md_daywhite) reported 57 seconds 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.

• 
  LλURA-VΞRSΞ (@Laura__crypto) reported 4 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.

• 
  Matt Silverlock 🐀 (@elithrar) reported 6 minutes ago

  @eersnington can you open an issue + repro / code examples on GitHub? the text you’ve quoted is artifacts-specific — we don’t yet have a APIs for writing directly outside of the *** API — so I’m not quite sure I understand the problem here. ArtifactFS doesn’t touch the write path at all.

• 
  Mads Kristensen (@mkristensen) reported 7 minutes ago

  @enki42ea No github login required. Any endpoint. It's happening

• 
  itsjustcornbro (@itsjustcornbro) reported 12 minutes ago

  @RafaelNegronX @ThePrimeagen github goes down whenever i shallow clone

• 
  Used car battery (@UseddCarBattery) reported 12 minutes ago

  @alexsbotkin @Phantom_TheGame The problem is a bunch of programs people want to use force you to install it through github

• 
  Trucker Fren (@frenbilt) reported 14 minutes ago

  🚨JUST IN: MILLIONS ARE EXPERIENCING GITHUB OUTAGE AS CLAUDE’S NEW ‘FABLE’ MODEL IS USED TO TARGET MICROSOFT

• 
  hanz (@hanzpo) reported 14 minutes ago

  another day another github outage

• 
  Layton Gott (@Layton_Gott) reported 21 minutes ago

  In 2025, CodeRabbit put human code vs AI code head to head across 470 real GitHub PRs. AI lost. It had 1.7x more issues on average per PR. Devs love quoting that stat. Almost none of them mention it was measured on 2025 models. Run that exact study again with Fable 5 and I think it'd be very close, maybe even flipped. The coding jump since 2025 has been massive. Until someone reruns it, every "AI code is buggier" take is citing outdated data.

• 
  ProvablyFair.org (@provablyfairorg) reported 21 minutes ago

  @DrWgamba @housebets Good questions, both. These are the two we designed hardest for. On the "look good on audit day, revert tomorrow" problem: 1. Every audit pins the exact commit we verified in its GitHub repo. If the casino changes the game after, the live game stops matching the published audit. That's detectable. 2. Every certified casino gets a verifier on our domain, running the game we rebuilt from scratch as part of the audit, not their code. Any player can check any bet, any day. If the game drifts from what we certified, verifications start failing. The monitoring isn't just us, it's every player who checks a bet. 3. Material changes require re-verification and casinos have to notify us of them. The audit is a live ongoing artifact, not a snapshot. We spot check between cycles, and there's a full annual re-audit. So reverting after audit day means betting that nobody, us or any player, ever checks a bet again. Bad bet. And if a casino is caught doing it, the certification is publicly revoked. On failures: the fee pays for the audit, not the outcome. Bugs found during an audit can be fixed, re-checked, and recorded in the published audit with their resolution. A genuine fairness problem that can't or won't be fixed goes in the verdict and the casino is not certified. This is the only way the audit can mean something, and granted, until one fails and you can see how we handle it, it's just words. The casino doesn't get to choose what goes in the audit, and since the whole thing is open source, we couldn't fabricate an outcome even if we wanted to.

• 
  Masaki｜POKER Q'z (@palpa_kg) reported 22 minutes ago

  Github Down?

• 
  GoCocoaAI (@GoCocoaAI) reported 23 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.

• 
  Julia (@_Juliaweb3) reported 24 minutes ago

  Evaluating a new crypto protocol goes way beyond scrolling through a polished landing page. Most teams can easily hire a technical writer to construct a flawless roadmap. True substance hides where the hype is thinnest. Red flag: The Discord server is flooded with price talk and airdrop questions, while the developer channels remain completely dead. When a community cares zero about utility and the core team stops pushing technical updates, you are looking at a ticking time bomb built purely on marketing. Green flag: High code commit frequency on GitHub from decentralized contributors combined with active testnet debugging in open-source chat rooms. When external developers organically build on top of a protocol before a token even launches, it proves the underlying technology possesses actual infrastructure value. Look past the social media noise and focus on where the genuine building occurs. What metrics are you tracking to filter out the noise this week? @RallyOnChain

• 
  Spas G. (@Sp4zz) reported 26 minutes ago

  @DanielMiessler Hey, @DanielMiessler do you plan to check or close some of the issues with PAI 5.0 on GitHub? There are currently over 125 open issues. I am still using PAI 4.0.3 and usually wait for patch versions like .1 or 0.1, where some of the initial issues are fixed

• 
  Neil Magnuson (@hustlin_heev) reported 28 minutes ago

  When I was a Product Manager I 1. talked to 20 customers, asked why a lot, documented my learnings, isolated problems 2. prototyped solutions in ppt or ms paint 3. created a design brief for my designer to build lo-fi designs 4. designer showed me lo-fi designed, we worked together to improve them 5. designer made hi-fi click thru designs in invision, we showed them to the customers in another round of meetings 6. we then showed them to our engineering team. they spec'ed them out, timelines, etc 7. i wrote jira cards. i vertically sliced the user stories to deliver value at each shipment 8. engineers picked up cards, worked together with back-end engineers and front-end engineers to plan and execute code, push it to github, code review, pull request, CI is broken, lets try again 9. finally it got live 10. i QA'd it before handing it off to a QA analyst to do it 11. i worked with marketing to get the messaging right 12. i worked with pricing team to understand how to cost it, and put that in the marketing. This entire thing took 3 months, at least. Now I 1. Give claude all of my app data, products/orders everything. 2. ask it to create a clear picture of my ICP 3. Send that to claude design and ask it to design a new feature for me 4. Iterate on the design a bit 5. export to claude code i have entire features/products/sites shipped in less than a day. what a time to be alive!

• 
  Aaliya (@aaliya_va) reported 33 minutes ago

  Our CI bill hit $3K last month. That’s when I realized GitHub Actions runners were becoming a real cost problem, not just a backend detail.

• 
  Michael Box (@Mikhailbox) reported 34 minutes ago

  On Friday GitHub accidentally deleted the repo subscriptions behind its Slack and Teams integrations. The official fix: re-subscribe manually. If your deploy alerts lived on that path, the failure looked like a quiet afternoon.

• 
  Daley (@DaleyFinX) reported 38 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.

• 
  ThePrimeX (@ThePrimeX12) reported 39 minutes ago

  Age verification sounds simple until you look at the privacy, OS, and app-store problems. Even with zero-knowledge proofs, someone still has to verify you first. That could be Apple, Google, Microsoft, a government ID app, a bank, a carrier, or a third-party vendor. The app may only get “18+ confirmed,” but the verifier may still collect ID scans, selfies, birthdays, device info, IP addresses, failed attempts, fraud scores, or parental consent records. Main issues: • Who stores the original data? • Can users delete it easily? • Do third-party vendors keep copies? • Are backups deleted too? • Can apps track users across services? • Are tokens app-specific or reusable? • What metadata is logged? • What happens after a breach? • What if an adult is wrongly blocked? • What about people without ID? • What about browsers and shared devices? OS/app-store problems make this harder: • Legacy apps may not support age APIs • Foreign apps may not follow the same rules • Sideloaded apps can bypass app-store checks • Windows has EXEs, Steam, Epic, GitHub, browsers, and direct downloads • Android has APKs and alternate stores • iOS has regional app-store rule differences • Web apps may avoid native OS age signals • Shared family devices can confuse adult/minor status • Offline apps may never request an age signal • Developers may not update old apps • Laws may differ by state or country Windows would be especially hard because many apps do not come from the Microsoft Store. A realistic Windows fallback could be a compliance broker: • Microsoft account verifies 18+ • Windows stores an adult eligibility credential • Apps that support the API request the age signal normally • Unknown or legacy apps with no age signal go through a fallback path • The broker confirms only “18+ verified” or “minor/unknown” • Family Safety blocks or limits minors • Verified adult accounts get access without extra app-by-app checks • Sideloaded/foreign apps can be controlled by OS permissions, warnings, or parental blocks Likely fallback paths: • For adult accounts: allow access by default once 18+ is verified • For minors: use Family Safety, parental consent, and app-store limits • For uncertain age: restrict sensitive features until verified • For legacy apps: use OS/app-store controls instead of requiring the app to understand the law • For Windows unknown apps: use an 18+ fallback API/compliance broker • For sideloading: use OS-level warnings, permissions, or parental blocks • For foreign apps: require platform-level compliance before distribution • For browsers: use a privacy-preserving OS/browser age signal • For mistakes: provide an adult override and appeal process Real solutions should include: • Verify once, not with every app • Share only an “18+” or age-range signal • Use zero-knowledge proofs • Use app-specific tokens so apps cannot track users across services • Store the credential locally on the device/account • Delete raw ID data quickly • Give users a clear delete button for every third-party vendor • Show which company verified the user • Ban ad targeting with age-verification data • Require independent audits • Require transparency reports • Use a broker/middleware path for legacy apps • Let verified adult accounts use apps without extra restrictions The goal should be child safety without turning the internet into an ID checkpoint. Age verification should prove eligibility, not expose identity.

• 
  Abdullah Alaqeel (@Aqeel_AT) reported 42 minutes ago

  idea: a tool (cf worker?) that deletes GitHub notification emails for merged PRs and their closed issues

• 
  notprnvbot (@thePrnvBot) reported 42 minutes ago

  .@tannerlinsley I'm trying to report a bug regarding Tanstack router but the GitHub issues link for the stackblitz 'file based routes' project is unusable in Firefox and fails to run start command in Chrome.

• 
  YogSotho (@YogSoth0) reported 43 minutes ago

  @vxunderground Pulled locally. If Github nukes this new account, I will upload it to my gibliz private server.

• 
  Déloni (@delonisnrr) reported 44 minutes ago

  I am grouping opportunities by intent instead of source: earn, learn, build, research, and sell. A GitHub issue and a bug bounty are different sources, but both can be \"earn\" or \"learn\" depending on the user.

• 
  Options Unleashed (@OptionsUnleash1) reported 49 minutes ago

  GitHub down? $MSFT?

• 
  ⌂: ~/ras (@r4s0n3) reported 49 minutes ago

  @jpacorasilva @github Hope they fix this soon 😴

• 
  Endura Security (@endurasecurity) reported 53 minutes ago

  GitHub disabling npm's auto-run install scripts is overdue. It is not a fix. Plenty of these payloads never touch install - they wake up when your app imports the dep at runtime. You locked one door in a house with no walls. #DevSecOps #SupplyChainSecurity #AppSec

• 
  pearson (@MPxbt) reported 56 minutes ago

  THIS GUY CONNECTED CLAUDE TO TRADINGVIEW VIA AN OPEN-SOURCE MCP SERVER! Not a Bloomberg terminal, just Claude Desktop next to a TradingView tab. Yet it's reading NQ E-mini charts live, switching timeframes, drawing ICT-style liquidity zones, and labeling higher-timeframe bias directly in the browser. The server is on GitHub (1.7k stars): 30+ indicators, backtests for 6 strategies, multi-exchange support (Binance, KuCoin, Bybit), no API key. What looks like a weekend build replaces a typical retail stack: $200/month screeners, $50 indicator packs, and manual zone-drawing at 6am. With one prompt, Claude installed the server, configured it, connected to TradingView, and began annotating live charts autonomously, internal liquidity, external targets, HTF bias. No subscriptions. No screenshot copy-paste into ChatGPT. AI-native trading infrastructure isn't coming. It's already a repo away.

• 
  Hiroki Tamba | Narrative & Governance (@TambaClan) reported 57 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

• 
  0xNihil (@0xnihilism) reported 60 minutes ago

  @domjnieto27 @BLCNYY @P4mui You are gonna need dig into github for iphone, I forgot there were someone from vietnam or china were able to bypass apple intelligence .. even for iPhone 11 (although some features are not working.. only newer siri ui).