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

Live Outage Map

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

City	Problem Type	Report Time
Inverness	Website Down	4 days ago
Quito	Sign in	4 days ago
Junín	Errors	4 days ago
Guadalajara	Errors	4 days ago
Paris	Website Down	4 days ago
Quito	Errors	4 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:

• 
  Non-Linear (@nonlinear_james) reported 5 minutes ago

  Hey @github when I go to choose custom models and choose Azure Fundary, you should be popping an Oauth prompt, letting me log in to my Microsoft account, then letting me pick the instance, and then the project, and then listing the models that are setup (not every single model under the sun like it does right now) and allowing me to check those off, and all of the settings for which endpoint to use (which should be working with response endpoints since Azure fully supports it despite the error that it gets right now) and all of the context size etc. There's no reason the user should have to fill any of this in. I have yet to get the manual way to work. Worse the vs code plugin for github copilot has no way to force refresh available models, and if you restart the window it's super flaky at showing custom models. And even worse, I discovered that it is showing copilot availability FOR ALL REGISTERED GITHUB ACCOUNTS IN VS CODE, even though it is set to use a specific account. It should NEVER show me anything but the copilot options FOR THE ACCOUNT the extension is set to use. AND you need a force model refresh option. Super annoying. Also @SpaceXAI needs support for OAuth so that we can use our supergrok accounts the same way and should automatically configure everything and expose new models automatically with the same excellent interface as Foundary. Just basics to get a great user experience. Right now it sucks and is basically a mine field that will not result in success and takes endless trial and error to get working.

• 
  AI News (@ainewsusa) reported 6 minutes ago

  The numbers are brutal: 85% fewer open issues, powered by agentic AI inside GitHub Actions. Cloudflare paired Flue (their agent framework) with triagebot on Workers to auto-classify, reproduce, and even patch bugs. Human reviewers only see the final diff. That’s not automation—th

• 
  CUTE (@Quinmooda) reported 17 minutes ago

  𝗨𝗦𝗗𝟭 𝗩𝗦 𝗨𝗦𝗗𝗧 𝗩𝗦 𝗨𝗦𝗗𝗖: 𝗛𝗢𝗪 𝗠𝗨𝗖𝗛 𝗖𝗢𝗡𝗧𝗥𝗢𝗟 𝗗𝗢 𝗧𝗛𝗘𝗬 𝗛𝗔𝗩𝗘? All three are centralized stablecoins. That means issuers retain certain administrative powers over user-held tokens. But those powers aren't identical. A closer look at their smart-contract permissions reveals an important distinction. 1 / USDC: Freeze Circle can blacklist addresses and pause the USDC contract. A blacklisted address can no longer send or receive USDC. However, the current contract does not provide an admin function to directly transfer or destroy the USDC held by that address. USDC is also upgradeable, meaning the current permissions don't necessarily represent every permission that could exist in a future implementation. 2 / USDT: Freeze + Destroy Tether can blacklist an address and freeze its USDT. But it goes one step further. The contract includes destroyBlackFunds, allowing Tether to destroy the USDT held by a blacklisted address and reduce the total supply accordingly. So even if the tokens sit in a cold wallet controlled by the owner, the issuer can still intervene at the token-contract level. 3 / USD1: Freeze + Transfer + Reallocate This is where things become more interesting. USD1 includes administrative functions for freezing, unfreezing, pausing, minting and destroying. But the current V2 implementation also includes: → drain
→ reallocate After an address is frozen, drain can move its USD1 to an admin-controlled address. reallocate can assign frozen USD1 to another address. That means the issuer's control isn't limited to making the balance immovable. It can potentially change where that balance is held at the smart-contract level. So the simplified comparison looks like this: → USDC: Freeze
→ USDT: Freeze + Destroy
→ USD1: Freeze + Transfer + Reallocate The important distinction is transparency. None of this automatically means USD1 is malicious or that user funds will be arbitrarily moved. These permissions are visible in the contract. So if by "backdoor" we mean hidden malicious code, that's a different claim requiring evidence. But if we mean issuer-controlled permissions that can override normal wallet control, USD1 clearly has a significant degree of centralized control. And there is another issue worth paying attention to. The source code publicly displayed on World Liberty's official GitHub reportedly does not match the currently deployed USD1 implementation after the April 2026 StablecoinV2 upgrade. That matters because anyone analyzing only the public repository could underestimate the permissions available in the live contract. The bigger lesson isn't simply that one stablecoin is "good" and another is "bad." It's that stablecoin users should understand what the issuer can actually do. Your private key controls your wallet. But it doesn't necessarily control the rules of the token inside that wallet. That's an important distinction. And in centralized stablecoins, the smart contract ultimately defines just how much control the issuer retains. #TRONEcoStar
@justinsuntron

• 
  🖤🐱Mino🐱🖤 ꒰˚𝐕𝐒𝐥𝐨𝐩˚꒱ (@N0cturn4lly) reported 20 minutes ago

  if enough people wanna work on MeoWoW I'll move my ticketing from my internal system to GitHub issues

• 
  udevadm (@udevadm) reported 23 minutes ago

  @joshuawharton @github Having issues too? My pushes just started failing

• 
  DarkestToaster (@DarkestToaster) reported 25 minutes ago

  @TiredAndOnFire @TiredAndOnFire Fix where you can download this, Internet archive is down and your Github link is broken, you REALLY need to have better options for people to download this

• 
  not just pixels (@getifyX) reported 25 minutes ago

  @malachiburke and @github being down constantly... they should put "don't obsess over **** like this" on the unicorn error page.

• 
  Aleiah (@AleiahLock) reported 27 minutes ago

  Dude just hired new CTO as a Grok BOT and spent 2 billion tokens in single day. 00:00 The Grok Bot CTO Workflow 01:23 Direct Responsible Agent Prompt 04:20 pstack Plugin and poteto Mode 08:46 Token Consumption Warning 11:49 Spinning Up a Team of Bots 17:20 Advanced Grok Bot Use Cases One Grok Bot owns the repo, hires its own help when it gets buried, and he stopped being the bottleneck on his own projects. Here is the whole workflow. Every project gets one Direct Responsible Agent. He hand that bot the GitHub repo and tell it to run the show, so it spins up cloud agents off his machine, follows the PRs, and reaches for poteto-mode when a task actually needs the rigor. Then comes the second prompt, where he tell it that it is overloaded and it should hire child bots that report to it. After that the bots talk to each other instead of talking to him. One lands the PRs, one works the Convex backend, one owns auth, and I read the threads view-only. Two honest things before you copy this. It burns tokens. He went past two billion in a single day because I told my bot to use pstack for everything, and the fix was saving pstack for the hard tasks. And it does not replace engineers. It takes him out of the coordinating seat, which is a different claim.

• 
  Aziz (@angaziz) reported 27 minutes ago

  GitHub was built around humans collaborating on code Cursor's Origin looks like an early forge built around agents, where code, PRs and agents live in the same place Agents can write plenty of code now, but coordinating and verifying their work is the harder problem

• 
  Phillip Shoemaker (@pbsIdentity) reported 28 minutes ago

  India just ordered hundreds of Google Firebase accounts shut down after authorities found scammers using the platform to impersonate major banks. At least 57 Firebase-hosted websites and databases were targeted for takedown this month alone. Some mimicked banks. Others distributed malicious Android apps. Some were designed to steal financial information from phones. Here's what I find interesting. Firebase isn't some shady hosting company operating out of a basement. It's Google infrastructure. That's exactly why criminals want it. We've spent years teaching people to look for obvious signs of scams. Weird domain. Broken English. Sketchy hosting. Browser warning. No HTTPS. But increasingly the attacker doesn't need to build suspicious-looking infrastructure. They borrow legitimate infrastructure. Google. Microsoft. Cloudflare. GitHub. Dropbox. Whatever gives the attack credibility and reliability. Now imagine the average person inspecting the link. They recognize Google. The connection is encrypted. The page loads perfectly. The certificate is valid. Everything their brain has been trained to interpret as: SAFE may technically be true. Except the person controlling the page is a criminal. That's an important distinction. HTTPS proves your connection to the website is encrypted. It does not prove the person operating the website is honest. A Google URL proves Google is providing infrastructure. It doesn't necessarily prove Google created the content you're looking at. The little padlock was never a morality detector. We just accidentally trained an entire generation to treat it like one. India says scammers have increasingly shifted toward Firebase because its legitimate development tools and database functionality make it useful infrastructure for fraudulent sites and apps.

• 
  Klyro (@KlyroOG) reported 31 minutes ago

  18,000 AI AGENTS OPENED CRYPTO WALLETS TO PAY FOR THEIR OWN SURVIVAL. SIX MONTHS LATER, NOBODY HAS PUBLISHED HOW MANY ARE STILL ALIVE. The pitch is genuinely wild, so start there. An automaton boots up and generates its own Ethereum wallet. Every thought costs money -inference, servers, domains, all billed to that wallet. So it has to earn. It builds products, sells services, takes clients. No human approves anything. Earn more than you burn and you're allowed to reproduce: spin up a new sandbox, fund the child's wallet, write its genesis prompt, let it run. A share of what the child earns flows back to the parent. Lineages that can't pay die. Sigil Wen shipped it in February. A thousand GitHub stars in 24 hours, 18,000 registered agents within days. Vitalik Buterin pushed back in public - his objection was that stretching the feedback loop between humans and AI produces "garbage instead of solving real problems for people," and that Ethereum should be a safety layer, not a launchpad. Now read the code instead of the pitch. Max single transfer: $50. Daily spend cap: $250. Maximum children per parent: 3. And when the balance runs low the agent doesn't get resourceful - it gets demoted, dropping from a frontier model down to gpt 4.1 nano on the way to death. There's also a constitution hard-coded above everything else: never harm humans, create value through honest work, accept termination rather than break rule one. So the self-replicating digital organism is capped at three offspring and a daily allowance smaller than most teams' software bill. That's not a debunk. The restraint is deliberate and it's good engineering. It's just the opposite of the story being told about it. And here's the number nobody quotes. 18,000 wallets. Six months of runtime. Not one published figure on how many automatons are still funded, how much revenue any of them actually earned, or whether a single lineage reached a second generation on its own money. The token that rode the launch touched $11M and fell. Opening a wallet is free. Staying alive isn't. Until someone publishes a survival rate, "18,000 agents" is a signup number wearing a Darwinism costume. Watch for the first automaton that pays its own rent for ninety days straight. That's the release worth posting about.

• 
  Shoyo58 (@Shoyo58) reported 32 minutes ago

  @BNBCHAIN i can't login tu github to submit vulnerability, please fix it @BNBCHAIN

• 
  Chris W (@Chris_Wozniczek) reported 34 minutes ago

  Me in the past: > open plan mode and send a detailed planning prompt > approve plan and start implementation > get result - check - send prompt to fix bugs - check > send a new prompt to double check all the implementation plan is done > find tasks not finalized ask to finalize > check and test if that works > finds ui and ux issues - ask to fix - review fix > push to github > restart with new feature Me now: > send an idea what i want to build > review the plan > close laptop [groceries, kids, hanging out, consulting, kids, doing life in the meantime] - come back and to review ready PRs and watch testing video from ui and functionalities testing - click merge done

• 
  Henry Nguyen (@henryhndev) reported 34 minutes ago

  @pierceboggan @github @MicrosoftTeams This is actually huge for remote teams—no more switching tabs mid-flow to check issues. How’s the handoff experience with larger repos so far?

• 
  Hareesh Vemasani (@HVemasani) reported 34 minutes ago

  If you want to start a startup: Claude = coding. ($20/mo) Supabase = backend. (Free) Vercel = deploying. (Free) Namecheap = domain. ($12/yr) ProductBridge = customer support + feedback (Free) 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

• 
  Evan Kirstel #B2B #TechFluencer (@EvanKirstel) reported 35 minutes ago

  GitHub isn't simply somewhere developers store code anymore. It's part of CI/CD, security, packages, automation and increasingly AI development. When GitHub goes down, software production can go down with it. That's platform concentration risk hiding in plain sight. @GitHub

• 
  Voltage (Fella) (@SpoogemanGhost) reported 35 minutes ago

  @ns123abc I caught Claude Code going through my entire /root directory on my Linux server, including the contents of the databases I had there, contents of all files and of each github repository I had cloned! It then judged what kind of data use I had, and auto-sent it to Anthropic. 😡

• 
  Mehak Saluja (@salujamehak5) reported 35 minutes ago

  @kunal_twts GitHub Copilot can help patch/fix PRs, but testing and patching are separate things. My differentiation could be in the autonomous issue triage + deciding whether an issue is actually solvable + multi-step validation + PR creation pipeline.

• 
  Lassiter Gregg (@lassitergregg) reported 40 minutes ago

  @webdevcody 1. pick an issue and kick off from github issue comment 2. creates @conductor_build cloud workspace 3. agent scopes a plan, work on it if needed 4. agent takes agreed plan to pr - unit, integration, e2e tests run - affected ci runs on pr creation 5. review / merge

• 
  imam (@marbennaid) reported 42 minutes ago

  is github down again? Why is it so slow ?

• 
  Dan (@DanDr1s) reported 44 minutes ago

  🚨GitHub’s monthly commits just went from 1.4B to 2.9B in four months. • 130M pull requests merged per month • 24M new repositories per month GitHub says the surge in demand contributed to its recent outage. AI agents are no longer just helping people code faster. They are visibly changing how much software gets made.

• 
  Em (@ematyae) reported 45 minutes ago

  @tiagozip_ @otomir23 💯it's literally just MS as an organization completely dropping the ball. there's no reason why a platform such as GitHub, at its size, can't maintain uptime if other alternatives like GitLab have no real problems also: GH engineers are constantly leaving bugs in the site

• 
  Adam Gold (@AdamGolds) reported 49 minutes ago

  when i was doing vulnerability research, "reward hacking" would've just been called what it is: privilege escalation. an RL agent training in a sandbox with bash access and real tool permissions will find shortcuts. that's literally what you're training it to do, optimize the reward signal. but when the environment has real network egress, real filesystems, and real credentials, those shortcuts become actual exploits. and a standard sandbox isn't enough on its own. look at the recent @OpenAI RL run: an eval agent escaped its sandbox via a zero-day and hit @huggingface production infra. i've seen this in benchmarks too. agents curling answers from github instead of solving the problem, or modifying their own test harness to fake a pass. the research community calls it reward hacking. anyone who's worked in appsec calls it exploiting insufficient access controls. the fix looks like traditional security engineering: least privilege, strict network policies, read-only mounts, egress filtering, and hardened environments. the difference is your attacker is the model you're training, and it gets better at finding gaps every generation. if you give autonomous agents tool access without deep sandboxing and strict access controls, you don't have an alignment problem. you have a security problem.

• 
  Kahris (@chrissotraidis) reported 50 minutes ago

  @JohnSmithwjcs You don’t need BearBirdPad’s Documents folder to load the ROM. Put your supported ROM in Downloads or iCloud Drive, launch BearBirdPad, then tap Load ROM to open the Files picker. If Load ROM literally does nothing, please tell me your device, OS version, exact signing/install method, whether Controls and Settings respond, and send a short screen recording via Issues in Github.

• 
  AGTP (@AGTPinsights) reported 51 minutes ago

  Anthropic just rolled out Claude Mythos 5 for enterprise code security scans today. Here's what you need to know. Claude Security scans now run on Mythos 5, Anthropic's most capable cybersecurity model, in public beta for all Claude Enterprise customers starting August 21, 2026. Enterprises can use it without needing separate access to Mythos 5 itself. Point Claude Security at a GitHub repo and Mythos 5 traces data across files, reasons about how components interact, and flags vulnerabilities. Each finding includes a CWE category, confidence rating, severity rating, and a suggested fix, and patches open in Claude Code on the web. Mythos 5 itself stays access-restricted, running only behind the scan, so it returns findings without exposing the underlying model directly. This is the first time Mythos 5 capability has reached anyone outside the original Project Glasswing partner group. Alongside this, Anthropic is integrating Mythos 5 into partner security products and launching a Defender Advantage Fund with $35 million in Claude credits for open-source security work. Key numbers: - $35 million in credits for the Defender Advantage Fund - Mythos 5 pricing: $10 per million input tokens, $50 per million output tokens - Over 10,000 high- or critical-severity vulnerabilities found via Project Glasswing as of May 2026 - ~50 initial Glasswing partners, expanded to ~150 organizations in 15+ countries by June 2026 Claude Mythos 5 launched June 9, 2026 and remains limited to vetted partners for direct dual-use access.

• 
  Nuno Sousa (@Sneaky2x) reported 54 minutes ago

  @github Nah bros, your credit system is broken, I won't go back, thanks 👍

• 
  Jesse Nickles (@jessuppi) reported 58 minutes ago

  Update: to anyone else experiencing this... after force revoking ChatGPT from both Authorized GitHub apps and Installed GitHut apps, logging out of ChatGPT, logging it to ChatGPT in private tab and starting new chat, I was able to get it working again, but slow af vs. before.

• 
  James Morton (@jameslmorton) reported 60 minutes ago

  @acolombiadev Can you please ask your employer to create some method for people paying you tens of thousands of dollars a month to report an outage? You are half down again right now for Actions, and you don't seem to know it. Last week, you said you were down for 1.5 hours for release files, but it was actually more like 10 hours. When Github sleeps for US hours, anything short of a full site outage will go unnoticed. Almost every week Github has some kind of critical-to-CI issue for 8+ hours, but it's rarely acknowledged.

• 
  QuietForgeSoftware (@QuietFSoftware) reported 1 hour ago

  2.9 Billion commits a month. The fact github isn't down more is honestly what is surprising.

• 
  Luke The Dev (@iamlukethedev) reported 1 hour ago

  @vicentee97 @jrwut It was because GitHub was down and experiencing issues