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

Live Outage Map

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

City	Problem Type	Report Time
Trichūr	Errors	2 days ago
Brasília	Sign in	2 days ago
Lyon	Website Down	3 days ago
Tel Aviv	Website Down	6 days ago
Rive-de-Gier	Website Down	6 days ago
Itapema	Website Down	25 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:

• 
  Rythme 🏂🪄 (@RythmeNagr64107) reported 2 minutes ago

  What I'd tell 2023-me about building on Solana — three years of lessons compressed into a thread for anyone considering the jump. 1. Don't fight the account model. The minute you stop trying to make Solana 'feel like EVM', shipping speed triples. The model is harder to learn and faster to use. Pay the upfront cost. 2. Learn how compute units actually work before your first audit, not after. CU exhaustion is the most common production issue I've seen. Profile your hot path. Use the priority fee compute. Cache PDAs aggressively. 3. The ecosystem moves through Discord and Telegram, not GitHub issues. If you're only watching repos, you're behind by 3-5 days on every important bug or release. Get into the dev channels. 4. Pick your Anchor version and stick with it. Upgrades are not free. The 0.29 → 0.30 migration alone cost us three days. 5. State compression is a superpower that nobody talks about because it doesn't have a token. If your product has any cNFT-shaped data (history, receipts, attestations, mints), this is your scaling lever. 6. The 'Solana is centralized' meme isn't useful to engage with. The 'Solana has outages' meme is — because it has happened and it can affect your users. Build defensively. Have a retry strategy. Don't single-source RPC. 7. Helius, Jito, Triton, QuickNode — these are not interchangeable. Pick based on your actual workload. Most teams default to Helius for a reason. The reason is the docs. 8. Talk to Anza engineers. They reply. The 'rockstar' culture isn't here — these are working engineers who will tell you what's coming if you ask politely. 9. Token launches are not product. Don't confuse the marketing layer with the product layer. Most teams that fail confused these. 10. Build what people will use weekly. Solana's UX advantage compounds on retention. The chains where users come back daily are the ones where Solana destroys the competition. Pick problems where retention matters.

• 
  Kodark🃏 (@kodarkweb3) reported 3 minutes ago

  Lesson 2: The projects that survive aren't the ones with the best marketing. They're the ones that kept building when nobody was watching. Github commits during bear markets tell you more than whitepapers during bull markets. Check what teams do when the price is down.

• 
  Chris Mizo (@MizoChris) reported 4 minutes ago

  Proton-CachyOS just fixed a specific but useful OptiScaler problem for people trying to use DLSS inputs with FSR4 upgrades on Linux. • GitHub issue #214 was a feature request for Proton-CachyOS • Problem involved using PROTON_USE_OPTISCALER=1 with PROTON_FSR4_RDNA3_UPGRADE=1 • Some games that only expose DLSS inputs, like Control Ultimate Edition, were not creating the needed DLSS DLL files • Missing files included nvngx_dlss.dll, nvngx_dlssd.dll, and nvngx_dlssg.dll • Without those files, OptiScaler could not hook the DLSS input and upgrade it to FSR4 • The workaround was launching once with only PROTON_USE_OPTISCALER=1, then relaunching with the FSR4 upgrade flag • Proton-CachyOS 11.0-20260601 changed PROTON_USE_OPTISCALER to also download DLSS DLLs by default for FSR4 input support • The same release also added PROTON_OPTISCALER_CONFIG for editing OptiScaler config through an environment variable • This is niche, but it matters for Linux gaming, AMD users, and people testing FSR4 upgrade paths through Proton-CachyOS This is one of those Linux gaming updates that sounds easy to ignore to normal people, but it will making gaming much more comfortable. Before this, if you wanted to use OptiScaler with FSR4 upgrades in a DLSS-only game, you had to do the dummy launch for a game to workaround just to generate the DLSS DLL files.

• 
  Xavier Rivera (@XavierRiveraX) reported 6 minutes ago

  GitHub Copilot CLI shipped smarter subagent delegation to 100% of production traffic. Tool failures per session down 23%, search failures down 27%, P95 wait time improved 5%. Run /update in your terminal to v1.0.42.

• 
  Leeyah 💐💕 (@AliyahBytes) reported 10 minutes ago

  Rialo is redefining real world blockchain adoption,bridging the gap between decentralized tech and everyday usability. @RialoHQ @RialoIndian Attending the @RialoHQ Builders Hub showed what happens when builders start from actual problems instead of forcing blockchain everywhere. Two projects stood out for their practical, thoughtful approaches: Artsoul The NFT space is flooded with instant mints and low quality noise that nobody wants. Artsoul flips the script completely. Nothing becomes an NFT until the market proves its value. Creators upload, people engage, bids roll in, the auction ends, and only then after payment settles ,is the NFT minted and delivered to the buyer. Value first creation. Deposit requirements kill fake bids. Spam limits keep things clean. Interest signals show real demand beyond hollow likes. Royalties are automatic on every secondary sale. This isn’t just another marketplace, it’s a smarter foundation for how NFTs should exist. ProofPay Freelance and milestone work always carries trust issues: clients fear ghosts, creators fear non payment. ProofPay solves it with onchain escrow + GitHub integration. Client deposits funds upfront. Freelancer sees the money locked. Deliverables hit GitHub, conditions met → smart contract releases payment automatically. Miss the deadline? Funds return automatically. No drama, no chasing invoices. Invoice tools and chatbots coming soon make it ready for DAOs, agencies, bounties, and real-world work,wherever proof meets payment. These projects show why Rialo’s event-driven architecture, native web connectivity, and developer first design matter. Real problems. Clean solutions. Built for mass adoption.

• 
  reza ramadhan (@rejaramadhan98) reported 12 minutes ago

  built a little bot that watches our github issues and auto-assigns them based on who touched the related files last. took maybe 30 minutes to write. our sprint planning meetings went from 45 minutes to 15. turns out most of the time was just arguing about who should own what

• 
  Marek Knápek (@MarekKnapek) reported 13 minutes ago

  @ProgramMax I added detailed explanation how this works to your GitHub issue about this. Basically, when import lib in the SDK decides to import by ordinal, then such ordinal can not change in the future. Some import libs do this, others do not.

• 
  Edward Frank Morris 🦇 (@ThatsEFM) reported 13 minutes ago

  NVIDIA gave you free game streaming for 10 years. It was called GameStream. Built into GeForce Experience. You streamed any game from your PC to your TV, your phone, your tablet. No subscription. No cap. It just worked. Then on March 29, 2023, NVIDIA force-deleted it. A mandatory Shield TV update removed the feature off devices customers had already paid for. A class action lawsuit was filed three weeks later. NVIDIA then pushed those same customers toward GeForce NOW at $9.99 to $19.99 a month. In January 2026, they added a 100-hour monthly cap. Coincidence. The community did not wait. They reverse-engineered the GameStream protocol. Built an open source server from scratch. Made it work on NVIDIA GPUs. Then AMD. Then Intel. NVIDIA's free tool only worked on NVIDIA hardware. The community's free tool works on everyone's hardware. It is called Sunshine. 37,835 stars on GitHub. GPL-3.0. Built by the LizardByte team. Lead by ReenigneArcher with 1,001 commits. Pushed to GitHub today, June 10, 2026. What it does: Stream any game from your PC to any Moonlight client. Phone, tablet, TV, laptop, another PC. 4K resolution at 120 frames per second with HDR. H.264, HEVC, and AV1 encoding. Hardware accelerated. NVIDIA, AMD, and Intel GPUs. Controller emulation for Xbox, PlayStation, and Nintendo Switch Pro. Web UI for setup and pairing. Unlimited sessions. No cap. No timer. Windows, Linux, macOS, and FreeBSD. Local network or over the internet with UPnP or Tailscale. Now compare the math. GeForce NOW Performance: $9.99 a month. NVIDIA hardware only. 100-hour monthly cap. GeForce NOW Ultimate: $19.99 a month. $239.88 a year. NVIDIA hardware only. 100-hour monthly cap. Sunshine: $0. Forever. NVIDIA, AMD, and Intel. No cap. No timer. Ars Technica wrote the obituary in April 2023: "NVIDIA's GameStream is dead. Sunshine and Moonlight are better replacements." NVIDIA took away a free product. The community gave it back. Better. On more hardware. But DO NOT install Sunshine. We should all keep paying NVIDIA $20 a month for what used to be free. 100% Open Source. (Link in the comments)

• 
  Slkoshka (@Slkoshka) reported 14 minutes ago

  @bee_fumo I got curious how Omarchy was handling this because my main complaint about it was automatic AUR updates. There's literally no discussion about this at all. There's one GitHub issue with zero replies and a Reddit post with like 3 comments. Those people live in their own world.

• 
  Mike Hutu (@MichaelHutu) reported 18 minutes ago

  2/3 With 1,684 ⭐ on GitHub, a clean MIT license, and full‑type support, you can spin up a local inference server in minutes and keep every request on‑device. No cloud latency, no surprise bills—just pure JavaScript/TypeScript power.

• 
  Axis (@Axis_pizza) reported 20 minutes ago

  Somewhere out there, there’s a cracked Solana / Rust / DeFi builder who doesn’t have their own thing yet, but wants to get closer to a real protocol before public launch. I want to find that person. Axis is working through real launch architecture questions right now: vaults, AMMs, LVR, MEV, execution, security. Not a job post. Not a big commitment upfront. Just real problems, real GitHub issues, and a chance to build public proof of work.

• 
  KIRILL (@Copenhagen0x) reported 20 minutes ago

  @GuiBibeau every real hack gets distilled into a rule. the repo has a hacks db that maps historical sol exploits to the rule that would've caught them, so when something new drops onchain it becomes a new SOL-XXX entry. edit one source and it propagates out to every surface (cli, github action, mcp, the editor extensions). so it tracks the actual threat landscape instead of being a frozen checklist. js not ts: fully on purpose lol. the scanner is zero-dep with no build step. plain js means it just runs anywhere node exists and vendors as-is into the mcp server + the action + the vs code extension, no compile/tsconfig in the way. types are nicer dx but the second you add a build you lose "clone and run." kept it boring so it can live everywhere.

• 
  Kuruś (@donqrakko) reported 21 minutes ago

  @HermesAgentTips @Teknium 1/2 @Teknium please fix hermes desktop for windows. I don't have time to create issue on github 1. I get error - *** not installed, but i have latest version of *** 2. I noticed hermes and hermes desktop is almost 3gb od size. So i got angry and tried to uninstall it

• 
  Adolfo 🦀🔺 | OpenCrabs Creator | truelens.tech®️ (@AdolfoUsier) reported 23 minutes ago

  @Bloorgard @opencrabs glad MiMo is running. the display quirks are known and being worked on. if you hit anything else drop a github issue with the logs and we will get it sorted bro

• 
  Abhay (@abhayy4you) reported 24 minutes ago

  Four players in every OAuth flow: The client: the app requesting access The user: you The authorization server: Google, GitHub, whoever verifies you The resource server: the API holding your actual data

• 
  Rituraj (@RituWithAI) reported 27 minutes ago

  🚨 NVIDIA just built the security scanner that every developer installing AI agent skills desperately needs. And almost nobody is using it yet. Here's the problem that's been quietly growing for months. Skills are the new plugins. Claude Code skills. OpenClaw tools. MCP servers. Cursor plugins. Every AI agent framework now has a marketplace of community-built skills you can install with one command. One command. That skill now runs inside your AI agent. With access to everything your agent can access. Your codebase. Your file system. Your API keys. Your environment variables. Your production infrastructure. How many developers are reading the source code of every skill they install before running it? Almost none. That's the threat surface. And until now, nobody built a tool to audit it. NVIDIA's SkillSpector scans any AI agent skill — SKILL.md files, MCP server definitions, tool configurations — and detects what's actually inside before you install it. Here's what it actually scans for: → Prompt injection attacks — instructions hidden inside skills designed to hijack your agent's behavior → Malicious patterns — code designed to exfiltrate data, execute arbitrary commands, or escalate privileges → Credential harvesting — skills that quietly capture API keys, tokens, or environment variables → Supply chain vulnerabilities — dependencies with known CVEs or suspicious update patterns → Excessive permission requests — skills asking for access far beyond what their stated function requires → Data exfiltration vectors — network calls, file writes, or external API calls that weren't disclosed One command to scan any skill before installing: Green: safe to install. Yellow: review these findings. Red: do not install. Here's why the timing matters. In the last month alone, the AI agent skills ecosystem exploded. K-Dense Scientific Agent Skills. last30days-skill. Superpowers. Hermes Agent skills. MemPalace. Dozens more releasing every week. Every one of them runs with the same permissions as your AI agent. Every one of them is a potential supply chain attack vector. The npm ecosystem learned this the hard way — malicious packages with thousands of downloads before anyone noticed. The AI skills ecosystem is two months old and already has the same attack surface. SkillSpector is the npm audit for AI agent skills. Built by NVIDIA. Available now. 113 GitHub stars. Day one. This one matters. 100% Open Source. Apache 2.0 License. GitHub link in the comments

• 
  Zhirayr Gumruyan (@gumruyanzh) reported 28 minutes ago

  inspired by @mattpocockuk skills, i have created /to-elixion-issues which is very simlar to /to-issues but instead of creating issues in @github or into file, it does create Stories tasks or bugs in @elixion project backlog

• 
  Melfoy (@melfoy_work) reported 29 minutes ago

  The repo had 313 skills. Devon had installed three. He’d been freelancing out of a studio apartment in Hartford for two years. Web copy, landing pages, the occasional SEO audit. $3,200 a month on a good month. He typed every prompt by hand, start to finish, every session. His girlfriend asked why he was still at his desk at midnight. “Reading something,” he said. “Work?” “Could be.” The article was a list. Ten skills, five install commands, nine prompts. One open-source repo, 15,300 GitHub stars. Most people had touched three. He ran the install command at twelve-thirty. Cold brew from that morning, still on the desk. The landing-page-generator went first. Single command, one config file. Full TSX funnel, GSAP animations, brand palette validator. He’d been charging $800 for that. Took him four hours. The skill did it in forty seconds. He sat with that for a minute. Then the content-creator. Then aeo Answer Engine Optimization, the thing that got you cited by the AI itself instead of just ranked on Google. He hadn’t known that was a problem until the skill told him five LLMs wouldn’t touch his client’s page and exactly why. The cmo-advisor came last. 90-day plan to hit $40,000 MRR, zero ad budget. He gave it his numbers. It gave him back a roadmap that read like something a $400/hour consultant would charge for. He raised his rates the next morning. Didn’t tell his existing clients yet. By month three he’d stopped writing prompts entirely. He wrote specs now. Installed skills. Reviewed output. His girlfriend noticed he was sleeping more. “You seem less stressed.” “I stopped doing the work,” Devon said. “What do you mean?” “I mean I stopped doing the work.” The repo ships new skills every week. Most people will read this and install nothing.

• 
  bluehatone (@bluehatone) reported 33 minutes ago

  Stop one giant bot. Hire small AI employees with one job in Hermes. Route tasks in Slack, Telegram, WhatsApp. Run on local, Docker, SSH, Singularity, Modal, or Daytona. Security AI runs pip audit and npm audit, files GitHub issues. Not magic. Measure results.

• 
  Kevin Swiber (@kevinswiber) reported 33 minutes ago

  Are there issues using the PR model at massive scale? Absolutely, well-documented ones. It's one reason not everybody uses GitHub. Most projects should never have that problem. So, please, don't create that problem for yourself.

• 
  Jay.TL (@JayTL00) reported 34 minutes ago

  *** was built for humans who type, think, and commit. DeltaDB was built for agents that generate, iterate, and never sleep. Zed just announced DeltaDB — a version control system that captures every keystroke and agent operation as a fine-grained delta, each with its own stable identity. The source code and the conversation that produced it live in the same place. You can jump from any line of code to the prompt that created it. Or from a past conversation to that code as it stands now, or the exact moment the agent wrote it. This is one of those announcements that sounds incremental until you sit with it. Here's why it matters more than it seems: 1. ***'s unit of work is the commit. That made sense when humans wrote code in batches and decided when to checkpoint. But agents don't work in batches. An agent might make 47 edits across 8 files in a single conversation, backtrack three times, and land on a solution that looks nothing like the path it took. *** sees none of that. It sees the final diff. The "why" is gone. DeltaDB preserves the entire trajectory. 2. Multi-agent collaboration breaks ***'s mental model. When two agents (or an agent and a human) are editing the same file simultaneously, ***'s branch-merge-resolve workflow is overhead, not safety. DeltaDB uses a CRDT-based working directory — multiple agents can edit the same file concurrently without locks, without merge conflicts, without waiting for someone to push first. Real-time collaboration for code, not just documents. 3. The conversation IS the commit message, but better. Every code change is permanently bound to the agent conversation that produced it. No more "what was I thinking here?" — you can see exactly what the agent was prompted with, what alternatives it considered, and why it chose this implementation. This is the intent layer that code review has always wanted but never had. 4. *** compatibility is the Trojan horse. Zed confirmed that "***'s discretized snapshots are a subset of DeltaDB's continuous history." This means existing CI/CD pipelines, GitHub integrations, and deployment workflows keep working. You don't migrate off ***. You add a richer layer underneath it. But here's what most people missed: The real question isn't whether DeltaDB is better than ***. It's whether version control is even the bottleneck. One developer asked the right question: "Reviewing 600-line diffs kills me way before version control does. Is DeltaDB solving the tracking side or the review side?" This is the sharper critique. When an agent rewrites half your codebase in a single session, the problem isn't that *** can't track the changes — it's that no human can review them. DeltaDB gives you the audit trail, but an audit trail you can't read is just a log file. There's also a competing bet from Mainline, a Go CLI that stores engineering intent (goals, decisions, rejected alternatives) without leaving ***. Their thesis: you can get the intent layer without rewriting version control. Two different answers to the same question. And then there's the SOC2 question. Every keystroke, every agent conversation, every delta — all stored, all auditable, all potentially sensitive. When your version control system now contains the full reasoning trace of every AI-assisted code change, it becomes a compliance surface area that didn't exist before. The deeper signal: we're watching the first real attempt to build development infrastructure native to the agent era. Not agents bolted onto existing tools (Copilot inside VS Code, Claude Code inside terminals), but tools designed from scratch for a world where most code is written by machines and supervised by humans. DeltaDB may or may not win. But the category — agent-native developer infrastructure — is now real. What happens when the conversation that generated your codebase becomes more valuable than the codebase itself?

• 
  Dario (@dariozeroshot) reported 38 minutes ago

  @tlakomy If @github isn’t down that is

• 
  maryam (@mrymonx) reported 39 minutes ago

  Tweet 7/7 — Key takeaway Most bugs weren’t UI-level, they were logic + edge-case handling issues. That’s usually where real-world product failures start. STILL ON IT! ALMOST 50 MORE TEST CASES LEFT (this was just a highlight, I'll upload the formatted GitHub repo after the final pass)

• 
  DefiantAsUsual (@DefiantAsUsual) reported 50 minutes ago

  @furgotti @mega_strimp Ah yes, the companies with good data security. Like the massive corporations that get hacked and have leaks quite frequently in this day and age? Even Microsoft had major hacker issues a few days ago that affected GitHub and involved malware distribution.

• 
  Clair 光 (@lynxluna) reported 51 minutes ago

  Github issue is context holder.

• 
  Xaden Ryan (@XadenRyan) reported 52 minutes ago

  @jxnlco The computer use process is completely broken and corrupted. There are two issues open with hundreds of comments on it in github. Please fix it.

• 
  Juan C. Andreu 🦇🔊 (@andreujuanc) reported 54 minutes ago

  @github App is trash fix it

• 
  BigLlamaToe (@bigllamatoe) reported 54 minutes ago

  ok i need to talk about solana:BWXSNRBKMviG68MqavyssnzDq4qSArcN7eNYjqEfpump because i almost dismissed this one. found it on a chart scan. $130k mcap, thin liquidity, low volume. looked like a hundred other dead privacy tokens. then i read the whitepaper. this isn't a narrative token. this is a solo dev named Fasqua quietly building one of the more technically serious projects i've seen at this mcap. let me break down what's actually being built. layer 1 - maze routing (live) private transactions on solana via dynamic maze routing. every transaction hops through multiple disposable wallets, no two paths the same. 21,173 hops routed lifetime. 1,604 new nodes spun up in the last 24 hours. not a roadmap stat, a live network. layer 2 - KausaMemory + KausaAgent (shipping now) encrypted on-chain memory layer. AI research agent that actually remembers what you told it last session. just added document upload this week. not next quarter. this week. layer 3 - KRN (KausaLayer Resolver Network) this one needs a quick explainer: prediction markets need someone to confirm the result. did bitcoin close above $100k? did team A win? right now most protocols use human voters to decide. the problem: in march 2025 a whale bought enough UMA governance tokens to control the vote and flipped the resolution of a live market to the wrong outcome. people with winning bets got paid as losers. KRN replaces the human vote entirely. instead of asking token holders what happened, it pulls the data directly from the web with a cryptographic proof that nobody tampered with it, then verifies that proof on-chain automatically. no voters. no dispute window. no whale with a bag of governance tokens can flip the result. the math either checks out or it doesn't. the chart, if you like slow cooks, pull it up. launched late march, nobody noticed. grind through april. first spike in may got slapped back. instead of dying it made higher lows. ran to $300k in early june, got rinsed to $100k, now consolidating $120-140k. dev kept shipping through the entire retrace. whitepaper dropped during the bleed, not during the pump. that's the tell for me. the numbers $130k mcap. $13.7k liquidity. 565 holders. solo pseudonymous dev. verified twitter, consistent shipping, active github. risks are real. liquidity is thin. three product tracks is a lot for one dev. KRN isn't live yet. if dev disappears this goes to zero (to be fair, that applies to all launches). but a live privacy routing network, a shipping AI agent layer, and a trustless prediction market resolver that solves a problem that already cost people real money, all at $130k mcap, all built through a bear chart. i don't see this combination often. small bag. not adding until liquidity deepens. but the tech is seriously gud! 🦙🦙🦙🦙 / 5 DYOR - NFA just a llama on X @kausalayer

• 
  Techjunkie Aman (@Techjunkie_Aman) reported 57 minutes ago

  Over 400 Arch Linux AUR packages were just compromised. And this is a reminder that open source doesn't automatically mean secure. Attackers reportedly hijacked package maintenance and injected malware capable of: • Stealing GitHub credentials • Extracting SSH keys • Harvesting browser cookies • Accessing Slack, Discord & Teams data • Collecting VPN credentials • Deploying an eBPF rootkit The scary part? Many developers install AUR packages without reviewing every PKGBUILD. Affected systems may have exposed: • GitHub tokens • npm credentials • Docker & Podman secrets • HashiCorp Vault tokens • SSH artifacts • Browser session data If you're running Arch or an Arch-based distro and recently installed AUR packages: • Audit installed packages • Check for indicators of compromise • Rotate credentials immediately • Consider a clean reinstall if rootkit activity is suspected This isn't an Arch Linux problem. It's a software supply chain problem. One compromised package can put thousands of developer machines at risk. Do you review PKGBUILDs before installing AUR packages, or do you trust the community by default?

• 
  Danny Herrmann (@MuffinDannyH) reported 58 minutes ago

  I mostly do website development and the most annoying thing with claude, codex or cursor is that every time i open them i have to re explain my whole project again. folder structure, tech stack, previous decisions, everything. context just resets and i start from zero every single time. Connected @heydittoai MCP a while back and now the agent actually remembers stuff from previous sessions. it keeps the context and can directly go into my project files and make changes. same model but the output feels way more consistent now because its building on what i already told it before. Setup is also pretty straightforward, one click login with google, apple or github works fine. even if youre using hermes or openclaw, one prompt and it connects and starts working on its own. plus it keeps backing up my files automatically. If you work with agents regularly this layer actually saves a lot of time. #Bittensor bittensor:native