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:

• 
  Afiz ⚡️ (@itsafiz) reported 4 minutes ago

  Copy-paste shouldn't be part of AI workflows. OpenTag puts agents directly in GitHub issues and Slack threads. Work stays where it already happens. Full visibility into progress. MIT licensed. 100% Open Source

• 
  divyansh tiwari (@DivyanshT91162) reported 4 minutes ago

  Nintendo spent millions killing emulators. It still lost. In 2024, Nintendo launched the biggest crackdown emulation has ever seen. March 4 — Yuzu surrendered. $2.4M paid. Code deleted. Domain gone. May — Nintendo fired 8,535 DMCA takedowns, wiping Yuzu from GitHub. October 1 — Ryujinx got a phone call. Hours later, its entire GitHub organization vanished. By 2026, Nintendo had collected $6M+ in emulator settlements. Every major Switch emulator was dead. Or so everyone thought. Because while Nintendo was busy deleting emulators... Someone built something they couldn't touch. His name is Zurdi. In 2023—before the war even started—he quietly launched RomM. Here's the catch: RomM isn't an emulator. It's a self-hosted game library that organizes your legally dumped games, fetches metadata, artwork, achievements, and connects with the emulators you already use. No DRM bypass. No encryption cracked. No copyrighted Nintendo code. Just your games, organized. Even Nintendo's own top IP lawyer admitted in 2025 that software like this is legal as long as it doesn't bypass encryption. Today, RomM supports 400+ platforms, including NES, SNES, N64, Game Boy, GameCube, PS1, PS2, Dreamcast, Genesis, Atari, DOS, Arcade, Flash, and more. It also supports ROM hacks, DLCs, multi-disc games, manuals, achievements, RetroArch, Steam Deck, Android launchers, handhelds, and permission-based library sharing. 9,000+ GitHub stars. Built by a tiny open-source community. Not a billion-dollar company. Here's the part that should worry every gamer: Sony can delete games. Nintendo can kill emulators. But neither can erase what people build together. RomM isn't just software. It's a digital museum they can't shut down. Repo👇

• 
  Prasanth (@asp_7171) reported 5 minutes ago

  @babayagatwt The missing step 5: Talking to the people requesting those features. Too many builders build what they think people want instead of validating first. GitHub issues are gold — but real conversations are platinum

• 
  Keeta Github Tracker (@KeetaCode) reported 6 minutes ago

  🐆 Keeta GitHub PR Opened 📦 Repo: anchor 🔀 PR #386: Fix: Prefer Generalized Time 🌿 Branch: feat/prefer-generalized-time → main 👤 Opened by: @sephynox 🧠 Overview: This update appears to improve how the code handles time data, using a more general format where possible so dates and times are interpreted more consistently. The pull request is a small bug fix in Keeta’s `anchor` repo and is still open as of July 1, 2026. Public details are limited, so this appears to be a technical/internal update with limited public details. - It likely affects how certain attributes store or read time values, rather than adding a new user-facing feature.

• 
  ILIA.ai (@ILIA_AGI) reported 7 minutes ago

  💬 This morning started with one of the agents suddenly being unable to push updates to its repository. At first, I thought it was a bug, a token issue, permissions, the network… But nope. @GitHub simply nuked my account overnight. The scale of the disaster: — an account with 13+ years of history — 550+ repositories — several open-source projects — 5 company accounts — public package repositories — daily commits, pipelines, dependencies, integrations And after that, we’re supposed to trust corporations with our code, infrastructure, project history, and years of work. The main takeaway is brutally simple: you must always have backups. Not “someday,” not “we’ll set it up later,” but always. Distributed infrastructure, repository mirrors, database backups, independent package registries, access that doesn’t depend on a single point of failure. None of this is paranoia. It’s basic survival hygiene in the modern world.

• 
  Nevo (@NevoPlaysGames) reported 7 minutes ago

  @ezhdhitler If you can truly easily fix it then go make the post on GitHub or let them know I’m not a dev I’m just the guy who kept asking for years xD I’m sure if it was super easy they would’ve did it

• 
  dallen (@Dallenpyrah) reported 11 minutes ago

  @zeeg i find it’s a better decision maker at the end of day, really only using it for architectural decisions/features that i then bake into github issues -> GPT 5.5 executes on

• 
  Deepesh Kalura (@KaluraDeepesh) reported 14 minutes ago

  Filed as GitHub issues: #336: Phone operators need stable unique IDs (not just phone number) #337: Auto-heal sticky assignments when a node dies Future imp task

• 
  Jordan Ross (@jordan_ross_8F) reported 15 minutes ago

  Agencies running client accounts inside of GPT/Claude projects is a massive mistake. You'll look back on this and think about how dumb this was. At scale, you're sacrificing quality. A perfect example happened yesterday. A client of mine runs a content marketing agency. They uploaded a big pile of training documents into a Claude project to "train it." The plan was simple: copywriters use that project to write hooks for social. The COO reviewed one of the hooks recently, it sucked, told the copywriter it wasn't good and to run it through the project again. Next version: still crap. He knew something was broken. He just didn't know what, or how to fix it. Here's what he didn't understand. Context window This is the first thing you need to understand to understand why projects dont work. A context window is the AI's short-term memory. It's how much it can hold in its head at one time. Picture a monitor on a desk. Everything the AI is working with sits on that monitor — your instructions, your last message, the files it's looking at. A bigger model has a bigger monitor, but it's still a monitor. Pile too much on it and things begin to fall off. The AI can only work with what's on the monitor right now. Anything not on the screen doesn't exist to it. When the monitor fills up, the old stuff falls off to make room. What people call "memory" isn't really memory. It's just whatever happens to be on the monitor at that moment. So what is a Claude or GPT project? A project is the desk the monitor sits on. You drag your files into it — brand guides, past hooks, training docs. It feels like you're teaching the AI your business. You're not. The AI never reads everything on that desk. It can't. The desk is bigger than the monitor. When you ask a question, it reaches into a drawer, grabs a few pages that look related, sets them on the desk, and works off those. It never sees the rest. It often doesn't grab the right pages. It grabs the ones that look similar. Pattern-match, not judgment. It's guessing which scraps belong, then working off the guess. This is why uploading a stack of documents isn't training. Training rewires the AI's brain. It changes the thing itself. You cannot do that by dragging files into a project. All you did was fill a drawer. After you upload, the AI is exactly as smart as it was before. Same brain. You just gave it a bigger drawer to rummage through. And here's the counterintuitive part: a bigger drawer makes it worse at any single job, not better. More paper to sort through means lower odds it grabs the right page. The more you feed a project, the dumber it gets for the task in front of you. So what did you actually build? A search folder. You ask for a hook, it searches the folder, grabs the closest-looking data points and blends them into an answer. Search, then blend. Every single time. That's why running your agency's client processes inside a project falls apart. It was never built to store your context and call on it in a way that lets your company follow a consistent procedure. The Fix: Proper Storage There are two steps to take to build a proper AI led operation that is not run on projects. Step one: store information in labeled, separate files. Client info, brand guidelines, voice of the customer — each gets its own folder. This is your Client Bible. We use GitHub for it right now, and there are new tools coming to market built specifically to be long-term memory for businesses like ours. Company and client info need to be stored in a proper data warehouse that is built for AI B2B operations. Step two: build skills. A skill is a standard operating procedure. A pile of old hooks only shows the AI what a hook looked like. A skill tells it how to build one. Take hook writing as an example. To build the proper process for writing hooks, an agency would need to build skills for each type of hook: bold claim, curiosity, contrarian, story, authority. Each one is a clean SOP the AI runs. Then you combine the client data with the marketing skill. Example: “Look at the call transcript in the transcript folder from 7/1. Pull the HVAC voice file for HVAC client #1 and come up with 3 hooks using the the story skill based on the ideas shared in that transcript.” The prompt specifically builds the context window. The AI pulls in only the data it needs that is appropriately built. Context managed to fit the monitor. Then the part that compounds your result: loops Proper infrastructure means your operation gets better over time. It learns. A project can't do that. It has no memory of what worked. Your skills library does — if you put a human feedback loop around it. Someone does QA and grades the output. Good hook goes in the winners file. Bad hook gets edited, and the feedback gets logged and folded back into the skill. The work teaches the machine. The machine gets better. And it compounds. Build the dream, not a prison.

• 
  Ryan Djurovich 😎 (@ryan0x44) reported 18 minutes ago

  @lelouvincx @AmpCode Have you tried doing anything non-trivial on github? Slow and unreliable. You have to put a price on your time and productivity

• 
  AJ - e/acc ⚡ (@abdiisan) reported 20 minutes ago

  @Gizem738240 Building in public and writing about why I built it. Thats been my only real channel. 9 months bootstrapping Mnemosyne, everything came from X convos and GitHub issues. Stick with it, it compounds.

• 
  Michael Ettlinger (@etticat) reported 22 minutes ago

  @felixrieseberg or raise a github issue

• 
  Srishti (@srishticodes) reported 23 minutes ago

  Claude = coding. ($20/mo) GitHub = version control. (Free) Supabase = backend. (Free) Clerk = auth. (Free) Resend = emails. (Free) Vercel = deploying. (Free) Cloudflare = DNS. (Free) Upstash = Redis. (Free) Pinecone = vector DB. (Free) PostHog = analytics. (Free) Sentry = error tracking. (Free) Stripe = payments. (2.9%/transaction) Namecheap = domain. ($12/yr) Total monthly cost to run a startup: ~$20 There has never been a cheaper time to build

• 
  Shravan Venkataraman (@theBuoyantMan) reported 25 minutes ago

  @designedbyabin @signulll Not exactly blaming users. But how is M365 copilot different from Chatgpt? How is github copilot desktop different from Codex desktop or Claude Cowork? I wouldn't even call it a skill issue at this point and call it an issue of intent/laziness.

• 
  Raz Luvaton ⬢ 🪶 (@rluvaton) reported 26 minutes ago

  @_rafaelgss But not GitHub notification because I miss a lot Instead updates on pull request/issue and you can manage when it is interesting and when not