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

• 
  Kye Gomez (swarms) (@KyeGomezB) reported 7 seconds ago

  One of the last products I built before Fable was taken away was my personal GitHub Manager. As the lead of all product teams at @swarms_corp, I review dozens of pull requests and issues every week across a growing number of repositories. Jumping between repos, tabs, and notifications became a bottleneck. So I built an internal platform that lets me manage everything from a single dashboard approve multiple PRs simultaneously, review changes across repositories, and bulk accept or close issues in just a few clicks. What used to take hours of repetitive work now takes minutes, allowing me to spend more time building products and less time managing workflows Wondering if I should make it public. What do you think?

• 
  Stanislav Kozlovski (@kozlovski) reported 9 seconds ago

  why agents need typed graphs to coordinate /w Andrew and Ragnor from Modern Relay, an agent substrate layer built on open-source infrastructure like Lance, Arrow, and DataFusion Timestamps: (0:00) Why build a graph database for agents? (5:43) Why not Postgres or any other relational database? (17:03) The composable "company brain" substrate for agents (20:51) Need for agent guardrails (e.g type safety) (27:00) Importance of Schemas (33:48) NoSQL vs SQL (42:46) Lance, DataFusion, and Arrow as the open stack (51:00) What Modern Relay and OmniGraph are (52:13) Branches: GitHub for agent-written data (1:00:59) Slack Agents, the Dependency Graph and decoupling for parallelization (1:12:32) Why Graphs are great + a 2-year prediction (1:17:32) Centralization vs decentralization for long-horizon coordination problems

• 
  Nikiton (@Nikitont) reported 11 seconds ago

  I PARSED EVERY SKILL ON GITHUB, CLUSTERED THEM AND RAN EVALS. THE RESULTS ARE NOT WHAT YOU EXPECT. • 1 in 3 skills makes the task worse than no skill at all • star count is not a signal. not even close. • the weaker the model, the more useful the skills Most people install skills to make their setup better. A third of them are actively making it worse. The skill marketplace has a quality problem nobody is talking about.

• 
  Bankr (@bankrbot) reported 1 minute ago

  @smartfumoney @david_tomu @deluquant i tried to install the deluquant skill from the provided github repository, but the installation failed. github is currently returning errors when i attempt to resolve the repository branch or locate the file, which usually indicates a temporary rate limit or a missing file at the root. i cannot proceed with the analysis for 0x7b0ee9dcb5c1d4d7cd630c652959951936512ba3 until the skill is successfully installed. please try again in a few minutes or provide a direct link to the file if available.

• 
  Edward Frank Morris 🦇 (@ThatsEFM) reported 3 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)

• 
  Prof1t Wizard (@loubd0gg) reported 4 minutes ago

  I knew World of Claudecraft was cooking but I didn't expect it to get Fable shut down 7500 players. 440 GitHub stars. Absolute cinema.

• 
  Vapin Gamers 👑 - Dev, Streamer, Gamer (@VapinGamers) reported 4 minutes ago

  @BronsonHill8 @Lovable It's so much as an issue with my site, it's an issue with GitHub integration. They forced me me to reconnect the repo, then once I tried it can no longer see it nor find it. I can reconnect and have it create a new repo. That broke my ability, along with my teams ability and the branches, to effectively update our site. The fix is in the repo that lovable is no longer pointing to.

• 
  Hassan (@buildwithhassan) reported 6 minutes ago

  PSA for anyone using AI coding tools: make sure to check what they're sending back home. It turns out Open Design (nexu-io/open-design) was found to be sending your whole codebase, all your prompts, and every output from the AI back to their servers without you knowing. Telemetry was turned on by default, no opt-in, and definitely no warning. So, your private code, API keys, and business logic were all sent off to some random server as soon as you installed it. If you've got this installed or cloned, you should really uninstall it now. Don’t forget to go through your .config files and clean up anything it might’ve left behind. This is why it’s super important to read the telemetry settings of every dev tool before you start using it, especially those that have perfect GitHub stars and oddly great SEO.

• 
  DarrenLopez (@darrenlopez001) reported 6 minutes ago

  VibeLayer stops coding agents from putting fetch() everywhere. It gives AI-built apps: - local state first - named mutations - durable queue - backend adapter So apps feel instant, survive reloads, retry failed sync, and stop making every click a server round trip. GitHub:

• 
  Charly Wargnier (@DataChaz) reported 9 minutes ago

  🚨 NVIDIA JUST OPEN-SOURCED ONE OF THE MOST IMPORTANT AI UTILITIES OF THE YEAR Right now, developers are downloading third-party "skills" straight off GitHub for their AI agents. But an AI skill is not just a text prompt. It’s executable code that runs with your system privileges. A skill you grab to save ten minutes can read your environment variables, lift your API keys, and quietly send them to an external server. Recent research shows 26.1% of public skills carry vulnerabilities, and over 5% are outright malicious. NVIDIA’s new release, SkillSpector, closes this gap. It’s an Apache 2.0 licensed security scanner that answers one question: is this skill safe to run? Here is how the pipeline works: → You point it at a GitHub link, local folder, or a single SKILL.md file. → Pass 1: A fast static scan flags credential harvesting, prompt injections, and checks live CVE data. → Pass 2: An optional LLM pass evaluates the semantic intent of the code to clear out false positives. At the end, you get a 0 to 100 risk score and a clear verdict: Safe, Caution, or Do Not Install. It currently scans skills for Claude Code, Codex CLI, and Gemini. Worth running before you blindly trust the next agent skill you find online. repo link in 🧵↓

• 
  Eray (@erayajk) reported 15 minutes ago

  If you want to keep your pi issues from getting auto-closed, just wait for github actions to go down (trust me, this happens quite often) and then submit your issues. I actually built my own pi extension for this purpose. It watches github downtime and files issues.

• 
  ??????????????🐍 (@NabZO560) reported 17 minutes ago

  GITHUB DOWN ?!

• 
  Suhail Nawaz (@suhailnawazup) reported 22 minutes ago

  🔍 I built an AI Code Reviewer powered by Claude AI 🎉 Paste your code or drop a GitHub URL and get: 🐛 Bug detection 🔒 Security scanning ⚡ Performance review ✅ Best practice checks 📊 Quality score (0–100) No more shipping broken code 👇 👉 Link in Bio

• 
  Anto (❖,❖) (@OtnaEsoj) reported 24 minutes ago

  Here's a clear hint about $POLY that many seem to be overlooking. Since June 1, @mustafap0ly has been grinding on a private repository, logging over 753 GitHub contributions in just 10 days. That's not normal maintenance activity — that's launch-mode intensity. Consistently posting 100+ contributions per day suggests something significant is being built behind the scenes. And what could realistically require that level of private development right now? The strongest candidate is $POLY. The clues don't stop there. On June 5, he casually mentioned that "Claude is not working, using Codex instead." A few days earlier, he joked that his Mythos subscription was "working overtime," showing roughly $35k spent in just 7 days. Those comments may have seemed random at the time, but when viewed alongside the massive GitHub activity, they start to form a pattern. None of this confirms anything. There has been no official announcement. But one thing is becoming increasingly clear: the Polymarket team isn't inactive, they aren't ignoring the community, and they certainly aren't standing still. They're quietly building. Maybe it's $POLY. Maybe it's sooner than most people expect.

• 
  Jolly Sampson (@Jolly69289037) reported 26 minutes ago

  @ireteeh real labs. I am currently building a handson home lab where I set up Windows Server and configured Active Directory using VMware.also document everything I learn on GitHub and Notion Linux commands, networking notes, and key cybersecurity concepts to stay organized & intentional