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:

• 
  Oskar Wickström (@owickstrom) reported 3 minutes ago

  So, now GitHub Pages deploy is broken and I can't release my thing as planned. It really is time to move...

• 
  Nathan Colosimo (@thenathancolo) reported 11 minutes ago

  If the bun rust rewrite has shown anything, it’s that we need a better unit of measurement on GitHub. Commits can no longer be used as any measurement of output or work, and if commits / contributions were low signal before AI, they are ~0 now Same with the issue and pr slop Opening up 50 issues or PRs on shadcn doesn’t mean anything and shouldn’t Tbh here commits are actually a good measurement bc rewriting bun is actually an insane amount of work, but we need better ways of deterministically figuring out who is good at what they do + does a lot of it.

• 
  Tired Thracian (@TiredThracian) reported 12 minutes ago

  @GoogleAIStudio @github Why not from any *** server?

• 
  Frank Earl (@MadScientist_42) reported 18 minutes ago

  @r9x_zl @LundukeJournal Ah, one of my pet hate-ons indeed. There's a reason I maintain a fork of runit for emedded systems use (That needs to catch up and normalize against Gerrit's new tip on GitHub!!) and all. systemd is brain damage inflicted on us by Red Hat. In a similar manner that Wayland was inflicted on us. When people WHINE about all the major distros doing Wayland...they're saying Red Hat or Ubuntu. Not even close to the truth and they're part of the problem.

• 
  琥珀青葉@KohakuLab (@KBlueleaf) reported 20 minutes ago

  @getfailsafe PLZ stop spamming on github ok? Why you just keep spamming different open-source repo with non-existing security issue and never follow the contribution.md and/or pr template?

• 
  Harman (@itsharmanjot) reported 22 minutes ago

  GEFORCE NOW ULTIMATE COSTS $20 A MONTH. XBOX CLOUD GAMING IS $18 A MONTH. THIS OPEN SOURCE DOCKER CONTAINER TURNS ANY GPU YOU ALREADY OWN INTO A PERSONAL CLOUD GAMING SERVER. if you have a spare NVIDIA, AMD, or Intel GPU sitting in a homelab, a gaming PC that's idle 20 hours a day, or a server with a graphics card you're not fully using, this project just handed you cloud gaming for zero monthly cost. It's called Steam Headless -- a Docker image that runs a full Steam client on Linux with GPU passthrough, accessible from any device via a web browser or Moonlight, no monitor or keyboard required on the host. Here's what actually happens once it's running: → Full Xfce4 desktop streams to your browser via noVNC with audio and video → Sunshine server is included -- pair Moonlight on your phone, tablet, laptop, TV, or Steam Deck and stream at up to 4K 120fps with hardware encoding → Steam Remote Play works out of the box for streaming to other Steam clients on your network → Proton pre-configured for running Windows games on Linux → EmuDeck, Heroic Games Launcher, and Lutris installable in one click via the WebUI -- so your Epic, GOG, and emulator libraries all live in the same container → Full controller passthrough for Xbox, PlayStation, and generic HID controllers → Games library mounts to /mnt/games so you keep your saves and installs on the host filesystem → NVIDIA, AMD, and Intel GPU support with official driver integration Here's the wildest part: You can rent a GPU cloud server for less than the price of GeForce Now Ultimate, deploy this container in five minutes, install your entire Steam library, and stream it to a Chromebook from anywhere in the world. Or run it on the gaming PC in your basement and play from your couch, your bedroom TV, or your phone on the bus. Installation guides included for Docker Compose, Unraid, and Ubuntu Server. TrueNAS Scale support in progress. 4.1K GitHub stars. 262 forks. GPL-2.0. 100% open source. (link in the comments)

• 
  Danny Moerkerke (@dannymoerkerke) reported 23 minutes ago

  I just published Modern Web Weekly #76 🎉 In this edition: - pwa-check: an automated PWA health check tool - Safari MCP server - new installation dialog in Chrome 152 - Chrome 152 now correctly attributes push notifications to your PWA GitHub link to pwa-check and subscribe link 👇 🧵1/3

• 
  Vanta (@0xVantaa) reported 23 minutes ago

  9/ the team is not just random CT accounts. @dcc_crypto is the technical builder. @0xSquid_Sol is the co-founder / public face. both are @superteam builders. and the github trail shows squid wasn’t just tweeting about the engine. he was opening issues, PRs, and security fixes around toly’s tooling.

• 
  Adam Shepherd (@AdamShephe61844) reported 24 minutes ago

  The GitHub agent that leaked private repos wasn't a model jailbreak. It read a poisoned issue and did what the text said. Read scope plus any outbound channel equals an exfiltration path. Least privilege stops being optional the moment your agent can be talked to.

• 
  William Belfort (@WilliamBelfort_) reported 24 minutes ago

  Imagine if @base used a project building in their ecosystem to solve this GitHub outage issue… No delay on launch and we’d likely have our Base runner… Imagine. base:0x5f980dcfc4c0fa3911554cf5ab288ed0eb13dba3

• 
  RipAPixel (@RipAPixel) reported 25 minutes ago

  @zaynmcps Looking at issues in github it has a trojan in it

• 
  Germomics 🔬 (@Germomics) reported 27 minutes ago

  @sahildarz @jacob_posel Separate credentials for separate jobs: OAuth App for login (single-admin lock) and GitHub App for repo access. Worker mints an RS256 JWT from the App private key, exchanges it for a ~1 hour installation token, caches in KV. No PATs, nothing long-lived. Reads open to admitted clients, writes behind the operator grant.

• 
  Bryan McAnulty (@BryanMcAnulty) reported 28 minutes ago

  @ashtom @EntireHQ This looks great! GitHub cloning is painfully slow for agent use.

• 
  Nav Toor (@heynavtoor) reported 29 minutes ago

  Intuit shut down Mint on March 23, 2024. Millions of Americans woke up that morning with no budgeting app and no transaction history. Credit Karma got their accounts. It did not get the budgets, the categories, or the bill reminders. Then the paid apps started ringing the register. YNAB. $109 a year. Went from $50 to $84 to $99 to $109 in a decade. Monarch Money. $99.99 a year base, $199 for forecasting. Copilot Money. $95 a year. iOS and Mac only. Rocket Money. $12 a month to actually cancel your subscriptions. An app that shows you where your money went is now $100 a year for the rest of your life. There is another way. It has been sitting on GitHub since 2014. Firefly III. Not a budgeting app that tells you what you cannot buy. A double-entry bookkeeping system that shows you exactly where every dollar goes. Written by a maintainer in the Netherlands named James Cole who has committed 20,767 times to it. Latest commit today. The principle it runs on is one line, straight from the docs. "If you know where your money is going, you can stop it from going there." Not stop spending. Not cut your lattes. Know where it goes. Then decide. Every transaction has a source and a destination. Money does not vanish into a category, it moves between accounts. When you close the month the books balance because they have to. Multiple accounts, multiple currencies, budgets with rollover, recurring bills with forecasting, tags, categories, piggy banks. Imports CSV, OFX, MT940 from any bank. Full REST API. A companion importer that connects through Nordigen and SimpleFIN. Nothing leaves your server. Your data lives in your database on your machine. 23,948 stars. AGPL-3.0. Free forever. No premium tier. No cloud version selling your data on the side. YNAB at $109 a year for five years is $545. Firefly III on a $5 a month Hetzner box for five years is $300, and that box is also running your photos, your notes, and your VPN. Intuit shut Mint down. Somebody in the Netherlands has been quietly building the replacement for twelve years. (Link in the comments)

• 
  Rajan Bhattarai (@cdrrazan) reported 30 minutes ago

  GitHub makes you clear ~6 confirmations and type the full repo name by hand to delete a repo. Fine! Except it does the same thing whether the repo has 100K commits or one commit you pushed 20 minutes ago. That's the tell. The friction isn't calibrated to risk; it's calibrated to nothing. Real "confirm your intent" design scales with blast radius. Deleting a repo with 40 contributors and 2K issues should hurt. Nuking a throwaway you made this afternoon shouldn't. GitHub knows the commit count, the stars, the age, the contributors. It uses none of it. Uniform friction is the easy version to build. It's also the one that trains you to click "confirm" without reading — which quietly kills the whole point. Good instinct. Lazy implementation!