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:

• 
  Kingmaxx22🕹️🔖 (@22Kingmaxx) reported 9 minutes ago

  @Double2MC @sophiiess_ yes this is the real issue making a website that links to a major release on github isn't that complicated

• 
  Ask-Zai (@woodyholne) reported 12 minutes ago

  @araseb_ I think I've paid £8 a month for Figma, £18 a month for X I think £14.99 for Canva. My GitHub enterprise cost me a fortune. You do not wanna see my Google bill every month! YouTube: £20 a month.. The problem is they're all free until the point of building, designing, or coding enough content to where you require more services or the other premium services. At that point, it becomes extremely expensive!

• 
  Inference Engine (@iedaily_) reported 12 minutes ago

  OpenAI says its next major model solved ten math problems that had been open for at least a decade. Astra, still unreleased, built the first non-sofic group, a question Gromov posed in 1999, and disproved Connes's rigidity conjecture. Three Erdős problems went with it. The tokens cost about $2,000. Every proof ships with a Lean certificate on GitHub. No outside mathematician has checked them yet, but this stuff is cool enough to anchor a medal case (on a Fields Medal scale)

• 
  Nick (@drinkindrano) reported 14 minutes ago

  Expanding on this a bit - the thing is that I just don’t care. The people running GitHub also, rightfully, do not care. “Waaah I can’t find the download”. Okay? Why is this my problem? You contribute nothing. Which is fine, you don’t have to, but you not being able to download something is a personal problem. It’s just not relevant at all. Who cares

• 
  RobitOverload (@10_X_eng) reported 15 minutes ago

  @AlexanderJoh10 Can you open an issue on github so I don't forget to do this?

• 
  « 2k2 » (@peach2k2) reported 15 minutes ago

  @ShitpostRock and rest of the episode is them trying all the popular wine forks and patching their systems. the episode ends with them finding a github repo with 2 starts and runs the game with no issues whatsoever

• 
  paintbrush (@TXpaintbrush) reported 16 minutes ago

  @robbiehendricks @CaseyMericle The simple version of the way I write code with AI: > Write a prompt describing what the problem is and why and what I want to accomplish, ask the AI to turn it into a spec plan and encourage it to interview me further to fill in gaps > have AI interview me on the input data and the desired output format, it then creates an implementation plan > let the AI rip via instructing it to follow the implementation plan - usually this is a python solution, it all gets saved to GitHub > test, iterate, add edge cases and exception handling logic as it inevitably occurs > bonus points if you build eval, memory and flywheel enabling logic and tracking features over time

• 
  Dan Thompson (@DanThompsonIV) reported 18 minutes ago

  GitHub just put stacked PRs in public preview. We’re going to try them on a real multi-package change — not a demo repo. Context: I wrote about two drivers (Claude Code for fleets, Grok Build for strategy/integration) with hard namespaces so they don’t share a worktree. Before that: model-routing only works when it’s enforced. Same theme here. The problem stacks are aimed at is the one AI made worse. Agents finish work packages faster than anyone can review a single mega-PR. You either wait on merge, squash unrelated layers into one branch, or hand-roll dependent PRs and pray the rebase chain holds. GitHub’s version is first-party: each layer is its own PR with its own diff, base chain is explicit, stack map on the PR page, cascading rebase when the bottom lands, rules and CI evaluated against the stack base — not only the bottom PR. CLI is gh stack (init → add → submit → sync / merge). Merge stays human. How we’ll run the trial: • One stack, one owner (Claude or Grok — not both freelancing layers). • One logical concern per layer (schema → API → UI, or package A → B → C). • Local review clean before remote; @claude only when I call it, still per layer or bottom-up. • I merge. Agents submit and babysit. Preview or not, merge authority doesn’t move. • Worktrees stay namespaced. Stack is the PR chain, not a license to mix drivers on main. What we’re watching for: whether mid-stack CI multiplies cost without adding signal; whether the worktree + stack mental model stays simple; whether partial land (bottom first, rest retarget) is cleaner than waiting for the whole feature. If it sticks, it becomes the default shape for multi-package missions. If it doesn’t, we learned it on one stack, not a process rewrite. Prose is still a suggestion. A base branch that points at the layer below it is a rule.

• 
  WorktreeWise@ (@WorktreeWise_) reported 25 minutes ago

  What happens to your local web server when you run `*** checkout`? It breaks, reloads, or crashes. Worktrees let you run distinct servers for distinct branches safely. #*** #GitHub #DevTools

• 
  RaiRai! (@RaiRaiTheRaichu) reported 26 minutes ago

  - Handing the github organization, etc to the developer who encouraged trouble fell off the table (when that was actually one of the options being looked at.)

• 
  Rotimi Best (@rotimi_best) reported 26 minutes ago

  This is how I annotate feedbacks for @cursor_ai to go fix in my app. Once it's done, it comes back with a screenshot. If it aligns with my request, I sayf open the PR. if not, I annotate again and send it back for work. Cursor should probably support an annotating tool in their screenshots, that would be sick. Before I had to 1. Annotate 2. Create a linear ticket or Github issue 3. Assign to an eng 4. they go and work on it for hours 5. come back with a PR and we go back and forth on the PR. even though this interrupts my own active work. @greptile and @coderabbitai makes this easier for me though but they still don't catch intent and vision correctly. 6. if all good, then I merge.

• 
  Milady (@onchainmilady) reported 27 minutes ago

  DEVELOPERS ARE OFFICIALLY COOCKED BY GITHUB Someone just dropped Spark and it ships an entire app from a single prompt you type what you want in plain English and Spark ships the whole thing for you it writes the frontend, the backend, the database and wires them together itself then it deploys the app to a live URL you can open on your phone in minutes you describe a habit tracker or a booking tool or an internal dashboard and it comes back running you tweak it by talking to it, change the colors, add a login, add a table, and it rebuilds on the spot one person can go from an idea to a working product before lunch the stuff that took a small team a full sprint now happens inside a single chat window the people testing this today are shipping real apps while everyone else still opens a blank editor

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

  Claude Obsidian v2 just dropped. It gives Claude a perfect memory. For free. It's an open source plugin for Claude Code. MIT license. On GitHub right now. Here's how it works: → Drop any file into an inbox folder → Claude reads it, links it, and files it forever → Every claim keeps its source. Ask a question, get an answer with citations from YOUR notes → If the vault doesn't know, it says so. No making things up The problem it kills: AI wakes up as a goldfish every morning. You re-teach it your business. Every. Single. Day. Now your knowledge compounds instead of disappearing. The old way: 5 hours a week playing librarian. This way: 2 minutes. Your agents file everything for you. Setup takes 10 minutes. The plugin is free. Obsidian is free. Save this before you forget it. Your AI won't. Want the SOP? DM me. 💬

• 
  NiroSolis (@WilliamR58743) reported 38 minutes ago

  @ReviewsPossum He's not right. He's looking on GitHub for compiled binaries. That is not what GitHub is for. It is a version control management service, and it is a community for developers, not end-users. It's like shopping in a bookstore and expecting to find a movie. The problem is that end-uses are *way* too often directed to GitHub as if it's a software hosting site. It's not. It's a version control site; for devs.

• 
  moony! | 🟨⬜🟪⬛ (@_moonliit_) reported 39 minutes ago

  @sophiiess_ The problem isnt github being centered at the code instead of the downloads, its the people who make their stuff only downloadable via github which is stupid tbh