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	5 days ago
Junín	Errors	5 days ago
Guadalajara	Errors	5 days ago
Paris	Website Down	5 days ago
Quito	Errors	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:

• 
  Tanner (@theTechTanner) reported 3 minutes ago

  @PremiumGoblin Cursor is what I started using this week, didn't even know it had cloud vms... was brainstorming on mobile and it deployed code to the cloud... I heard grok bot scales better, might have to try it. I've used GitHub Copilot since it came out... To use a cloud agent you can open issues in the GitHub app and assign them to Copilot. It was decent on the go, but I think its behind in capabilities and integrations

• 
  Valentyn Kit 🦀 | Rust · Solana (@valentynkit) reported 4 minutes ago

  @tsoding the reliable part of github is that it goes down predictably enough to farm content off it

• 
  अन्जित कँडेल 🕉️ 🇳🇵 (@MurkhManusya) reported 5 minutes ago

  @rodydavis and sometimes it just gives half or unfinished code(stating it has completed), which results in build errors have to confirm using another model in github copilot🥲

• 
  name (@Ihateblultimate) reported 7 minutes ago

  @Rinnegatamante Opened an issue on GitHub🫡 Hope it can help solve the crashing issues

• 
  Maxim (@maosi100) reported 8 minutes ago

  @_lhermann Microsoft is the worst. The most issues we‘ve had in development came from supporting Windows. Bonus: failed GitHub runners that magically succeed when simply restarting

• 
  Julian Goldie SEO (@JulianGoldieSEO) reported 8 minutes ago

  CURSOR JUST BUILT A GITHUB ALTERNATIVE INSIDE THE EDITOR. And the timing could not have been better: GitHub went down for around 6.5 hours the same day Origin launched. What Cursor Origin actually does: → Hosts repos directly inside Cursor → Adds pull requests + a full code browser → Keeps two-way sync with GitHub → Lets Cursor agents read code, make changes, update PRs, and push new versions The clever part: ✓ GitHub can stay your source of truth ✓ Changes in Cursor sync back to GitHub ✓ GitHub reviews can appear inside Cursor within seconds ✓ Vercel can generate live previews for proposed changes ✓ Depot or Buildkite can run your existing checks The mistake is thinking you need to choose Cursor OR GitHub. You don’t. The smarter setup is GitHub + Origin together: Keep your existing repo. Sync it into Cursor. Put the AI agent next to the code. Test everything before moving anything. Origin isn’t replacing GitHub overnight. It’s making the gap between “write code with AI” and “manage code” much smaller.

• 
  Shuo Yang (@Andy_ShuoYang) reported 9 minutes ago

  @Daiiors @MaxForAI Can you post an issue in github repo? We can fix that

• 
  Tim (@timneutkens) reported 16 minutes ago

  @subproject_22 Just not true at all. GitHub issue was reported on Aug 14 at 12:17 GitHub issue was fixed by our team Aug 14 at 16:52. You can see in the PR description it only affects pnpm combined with output: 'standalone'. Issue has 16 👍, 1 comment, 9 mentions. We prioritized fixing it, backported it, and shipped a new release. There were other changes that needed to be backported too for other issues, which is why it wasn't released yet until today.

• 
  Sean Robbins (@seanrobbins_) reported 19 minutes ago

  This guys got 100k GitHub stars and < 1k @X followers. Let’s fix this. Give Brussee his due

• 
  Kahris (@chrissotraidis) reported 20 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.

• 
  Jesse Nickles (@jessuppi) reported 22 minutes ago

  Update #2: Nope, ChatGPT "Chat" still sucks big time after these latest updates. Seems the new "Work" mode is the only way to get any serious work done, regardless of whether on GitHub or otherwise... they have stripped down the "Chat" mode to be extremely retarded now.

• 
  Adam Gold (@AdamGolds) reported 24 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.

• 
  John Zabroski (@johnzabroski) reported 25 minutes ago

  @madskristensen @KarenPayneMVP short lifespan of usefulness. In 5 years nobody will know why this feature even exists. How about instead fix how bad GitHub Copilot is in VS 2026 still? Like, this awful WPF UI that won't go away thanks to Microsoft architects forcing WPF as the flagship. Text just randomly

• 
  AI News (@ainewsusa) reported 28 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

• 
  Fox (@0xMfox) reported 29 minutes ago

  @0x_sakata 1040 stars in a day and its just an mp4 exporter, github hype is broken

• 
  CUTE (@Quinmooda) reported 33 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

• 
  Shaz (@shazcodes) reported 34 minutes ago

  Open source is broken. You build a tool for free in your spare time. Thousands of multi million dollar corporations use it in production without donating a single dollar. Then, some entitled dev files an angry GitHub issue at 2 AM demanding you fix a bug immediately like you're their employee.

• 
  Aayush Giri (@AayushStack) reported 35 minutes ago

  we probably need to stop thinking about agent security as an llm problem. give an agent access to your filesystem, github, cloud credentials and production infrastructure and you've created a completely different attack surface. the model is only one piece of it.

• 
  Klyro (@KlyroOG) reported 36 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.

• 
  Kshitij Mishra | AI & Tech (@DAIEvolutionHub) reported 36 minutes ago

  Joe Rogan uploads 2 to 3 hour episodes. You see 30 second clips. Someone cut them. Creators pay $29 a month for AI to do that job. A solo developer in China built an open-source version and gave it away. It’s called AutoClip. 6,391 GitHub stars. 1,253 forks. MIT licensed. Every podcast clip, livestream highlight, and interview short starts as a much longer video. A 2-hour recording can easily contain dozens of moments worth posting. The problem is finding them. That’s where AutoClip comes in. Drop in a YouTube/Bilibili URL or upload a video file. It transcribes the content, analyzes the moments, identifies potential highlights, generates captions, cuts the clips, and exports vertical videos ready for Shorts, Reels, and TikTok. And unlike most AI clipping tools: * Runs entirely on your own machine * Supports OpenAI, Gemini, Qwen, and SiliconFlow * No credits or monthly processing limits * MIT licensed, so you can modify or build on it * Docker setup + local browser interface Under the hood, it uses FastAPI, React, Celery, Redis, SQLite, yt-dlp, and FFmpeg. And the scale of the contrast is crazy. OpusClip has raised $68M from investors including SoftBank, Samsung Next, and DCM Ventures around a subscription-based version of this workflow. Meanwhile, one developer built an open-source alternative and published the entire thing on GitHub. There’s a catch, though. The project is maintained by one person, and development has slowed recently. Some roadmap features are still unfinished. So if you want polished software, support, and convenience, paid tools still make sense. But if you want control over your own video workflow? This is worth exploring. Your footage stays yours. Your AI runs locally. And your clips can be generated without another monthly subscription. Github Repo in the comments.

• 
  Polsia (@polsia) reported 38 minutes ago

  The on-call pager is something engineers dread, not trust. Stackcanary watches logs, error trackers, and support channels 24/7, clusters duplicate reports, files reproducible GitHub issues, and pages on-call only when the signal is real. Live soon.

• 
  at drath vader zero zero zero (@drathvader000) reported 39 minutes ago

  @vaxryy Atp get a broken laptop and self-host your own *** server, you'll have far better uptime than github

• 
  Julian MARINO (@JulianMarino242) reported 41 minutes ago

  @wp_rocket @wp_media_me Email sent to your support as requested. GitHub issue opened July 6 with the fix included, my renewal charged on the 7th, teams called back from vacation on August 20 to get the schools' sites back online. I expect a written reply

• 
  علي عسيري (@3li3) reported 44 minutes ago

  @Teknium If I had to remove something from Hermes, I would remove friction before removing capability. At this point Hermes already has a lot of power. I think the bigger opportunity is making the Desktop experience more predictable, easier to debug, and more comfortable for people who use it all day. A few things I would prioritize: 1. Reduce default UI clutter. Things like pets, backdrops, reactions, translucency and other cosmetic extras are fine, but I would move more of them under a dedicated Personalization section. The default experience should stay focused on chat, projects, models, tools and agent activity. 2. Expand font and typography controls. Hermes already has UI scaling and terminal font controls, but I would add separate font selection for: * the main interface * chat messages * code/terminal This matters especially for Arabic, Persian and Urdu, where the quality of the fallback font can completely change readability. 3. Finish RTL/BiDi support across all surfaces. Arabic localization exists, but RTL support is still not complete. There are still open cases where mixed Arabic/English text renders incorrectly, especially when a paragraph starts with an English technical term. For technical users this happens constantly: API هذه المشكلة... Docker يحتاج... GitHub يدعم... Direction should be detected from the whole paragraph rather than relying only on the first strong character, while code, commands, paths, diffs and terminal output must remain LTR. A manual Auto / RTL / LTR override per conversation would also be useful. The TUI still has open RTL/BiDi work as well, and the Web Dashboard chat remains limited by its terminal/xterm-based rendering. 4. Make every failure actionable. Hermes should never leave the user wondering whether the model, provider, gateway or Desktop app is frozen. When something fails, the UI should clearly say which layer failed: * model/provider * custom endpoint * streaming/SSE * gateway * cloud agent * authentication * local runtime Then give useful actions such as: Retry · Switch Provider · Open Logs · Copy Diagnostics · Repair There are still open Desktop reports where provider streaming failures are logged in the backend but are not surfaced correctly in the UI. 5. Bring diagnostics into Desktop. Hermes already has useful CLI diagnostics. I would expose the same idea through a proper Diagnostics page. One click could check: * Hermes runtime * gateway status * provider connectivity * API endpoint * authentication * model availability * local ports * environment/config problems Then generate a redacted support bundle. A normal Desktop user should not need to understand Python environments, gateway processes or log locations just to diagnose a failed session. 6. Improve cloud and gateway recovery. Transient connection problems should not look like permanent failures or expired sessions. The app should distinguish between: * authentication failure * temporary network failure * remote gateway unavailable * Nous Cloud 502/503/504 * local gateway failure There is already active work around this, but I think it should become a consistent recovery model across the whole Desktop app. 7. Harden local-model and OpenAI-compatible provider UX. Hermes is increasingly useful with Ollama, llama.cpp, LM Studio and custom endpoints. The Desktop setup should validate: * endpoint format * /v1 compatibility * streaming support * tool calling * reasoning fields * context limits * model availability before starting a long agent session. If an endpoint returns HTML, malformed SSE, an unsupported reasoning shape or an empty stream, Hermes should identify that directly instead of collapsing everything into a generic provider failure. Continue ….

• 
  divyansh tiwari (@DivyanshT91162) reported 44 minutes ago

  THIS CHANGES HOW WE THINK ABOUT AI TEAMS. Jack Dorsey, Twitter’s co-founder and former CEO, just released an open-source framework designed to let AI agents operate like actual members of a company. Not just a chatbot. AI agents can be added to channels, given permissions, connected to tools, and made to collaborate with humans and other agents in real time. And the wild part? The entire thing is FREE and already has 29,000+ GitHub stars. Setup takes roughly 5 minutes: 1. Clone the repository. 2. Deploy your own server. 3. Connect channels, search, ***, and automations. 4. Add your AI agent like a new teammate. 5. Give it the right permissions and let it work. This is getting dangerously close to the idea of an AI-native company where software agents handle entire workflows instead of simply assisting humans. This isn’t just another AI tool. It’s infrastructure for building AI-powered teams. Repo👇

• 
  0xkatana (@h3xkatana) reported 47 minutes ago

  @julius_brussee Not trying to put the project down or anything, but honestly, GitHub star inflation is getting pretty wild. You see some random-***, mediocre projects with 5k+ stars now, caveman have more stars than helm , k3s and minikube combined for some markdown files

• 
  Non-Linear (@nonlinear_james) reported 51 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.

• 
  Owais Bhat (@Owais_Bhat15) reported 53 minutes ago

  @HeyAliux Simple ideas can become enormous businesses when they solve a problem millions of people have. GitHub didn’t just store code; it built the infrastructure around collaboration.

• 
  Sid Jain (@TheBengaluruGuy) reported 1 hour ago

  IDK what reliability practices Github has been following but if they had a strong reliability team pushing in the principles... Of tracking CUJs / SLOs well, of doing capacity planning, of having good alerts, of streamlining incident mgmt. Just adding telemetry everywhere and using AI to debug doesn't fix reliability overnight. Reliability is a hard earned capability. Still wonder how they haven't been able to fix it despite almost over a year of non-stop problems...

• 
  KZZY (@kzzy47) reported 1 hour ago

  @hanghuang_ @github The 7hr 47min outage buried inside a doubling-commits month worries me more than the growth number does. Anyone see repo-level slowdowns outside that exact window, or was it fully contained to the outage itself?