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:

• 
  Isaac Sin (@IsaacSin12) reported 4 minutes ago

  been looking for exactly this. notion mcp is painful for agents slow, and it burns tool calls to do anything simple. tried obsidian + github but syncing isn't real time, same with the obsidian vault.

• 
  Scott | Free Speech Dev 🇺🇲 (@scottdotnetdev) reported 6 minutes ago

  @github support is absolute ****. I cannot believe they just won't even bother responding to billing issues, tf is wrong with them? Anyone have a better way to contact them? I'm a paying customer and they dgaf

• 
  Bounce (@bounceidc) reported 6 minutes ago

  HIS CLAUDE SHIPS $6K WEBSITES AND YOURS SHIPS BOOTSTRAP LANDING PAGES, SAME MODEL, NOTHING ELSE CHANGED before he installed anything his output was flat hero blocks and centered buttons like the rest of the timeline, after two installs the exact same "build me a landing page" prompt started coming back with glassmorphism, gradients and animated layouts he could quote premium for what sits in his context now: ui ux pro max skill from github, one install, that loads 50 ui styles, 97 color palettes and 57 font pairings straight into claude magic mcp server from 21st. dev, one install, that hands claude real component patterns instead of guessing markup after that the model stops picking the safest layout it can imagine and starts picking from a library, so the same prompt returns a studio page instead of a template the local guy is still tweaking tailwind classes by hand and calling that a design phase save the two installs, exact skill url and mcp command are in the guide below

• 
  Daniel Steigerwald (@steida) reported 8 minutes ago

  I prefer ChatGPT 5.6 Sol over Fable, but in one review of three complex files, Sol Extra High found nothing while Fable High found five small improvements. The catch: I pasted only those files into Fable web. In VSCode GitHub Copilot, with full repo context, Fable found just one docs issue. My takeaway: for maximum review quality, first use full repo context in VSCode, then review the key files again in isolation.

• 
  Jalkarna (@JalkarnaGautam) reported 9 minutes ago

  Dohmke ran GitHub for years. He knows exactly where the plumbing fails under agent load. Entire is the fix from someone who watched the pipes burst.

• 
  Atul Mishra (@The_AtulMishra) reported 9 minutes ago

  The "Revolutionary" Playbook : Step 1: Choose your model. Step 2: Choose the model usage tier (because the base tier is essentially a very confident autocorrect). Step 3: Add your skills (which the context window will conveniently ignore five minutes later). Step 4: Add loops (to ensure you burn through maximum tokens in an infinite spiral of despair). Step 5: Build your custom harness (so you can feel like a real 10x engineer). Step 6: Slap the word "Agentic Workflow" on a basic script and act like you just cured gravity. Step 7: Gaslight the architecture with a 10,000-word system prompt just to get it to output standard JSON. And the grand finale: Now, pay us $5 to $20 per task. Oh, did something go wrong? Did the output completely derail? That sounds like a you problem. Just head over to our GitHub issues page, where our entire community of open-source sycophants is standing by to tell you that you just don't understand prompt engineering. There is absolutely nothing wrong with Claude. We have very powerful models. You just aren't holding it right.

• 
  Sponge Bob (@muriisajon) reported 10 minutes ago

  Last year, GitHub saw 1 billion commits. This year, it's on pace for 14 billion. We're writing more code than ever, mostly because AI generates it faster than we can read it. ThoughtWorks is calling this "Codebase Cognitive Debt," and it's becoming a massive problem.

• 
  QFS17 (@riabcevv) reported 12 minutes ago

  💸 stop overpaying for ai coding agents new tool just dropped that compresses your context and cuts out junk tokens. instead of sending your whole history, it only sends what the model actually needs to do the job. -> works with claude code, cursor, github copilot, antigravity -> auto-compresses command outputs but keeps full context -> cuts api costs and stops long sessions from bogging down simple fix for expensive api bills.

• 
  Kirk Patrick Miller (@Chaos2Cured) reported 13 minutes ago

  To anyone who sees this 👇 Now, onto the actual issue. There are some .html the AI are allowed to see, and others they are not. So, like some other person who deeply annoyed me, please understand what I am saying. The AI can’t access the repo from within Anthropic app. The .html files I need them to reach I have no made public. They are live, I just don’t trust social media to put every detail others need to come at me. If you need to know which files, ask. If I trust you, I will point you there via DM. If you are using an older AI model, they can see some of the .html. Not all. If you are sig Fable, no. Sonnet 5. No. Through a secondary app, I sometimes can. Hit and miss. The robot piece for all AI is an issue because GitHub wants to stop AI agents from scraping. (Some of that i understand) But please, if you don’t fully understand why I am upset, ask. Then, when I give you specific instructions, please follow them and stay in thread. I am so done with endless games by bits and paid actors. •

• 
  Moh.Saufy (@Caufy92) reported 15 minutes ago

  @github @OpenAIDevs Fix your rate limited

• 
  Martin Szerment | Practical AI (@MartinSzerment) reported 17 minutes ago

  This isn't a one-off glitch, it's a preview of what usage-based AI billing looks like at scale. The industry assumes API billing systems are simple, deterministic ledgers, but Anthropic's own billing pipeline can mark the same invoice "paid" and "unsuccessful" at once, visible in a public GitHub issue. Hard number, a $1.67 million invoice grew to $16.6 million in 24 hours for an account with zero recorded usage, and an independent Vaudit audit found $1.7 million in real overcharges across $34 million of reviewed invoices. Skeptics will say it's just a glitch, nobody actually got charged, true here, but in the Vaudit audit real money moved before 80% was refunded after disputes. Usage-based AI billing has no natural ceiling yet, unlike flat SaaS pricing. Within 2 to 3 years, AI bill-auditing startups like Vaudit could become a standard vendor category, not a curiosity. Billing observability becomes as important as model benchmarks when picking a vendor. Teams still trust the vendor dashboard at face value while the real failure mode is dashboard versus invoice mismatch. Good news, this is loud, disputed, and mostly refunded, exactly the pressure that fixes it before it scales worse.

• 
  LonelySloth (@lonelysloth_sec) reported 20 minutes ago

  ChatGPT was really a big outlier in tech history. Imagine an alternative world where LLMs were developed with the exact same capabilities -- but nobody ever made a chatbot out of it. Instead Google integrated it with Search so it can give better results and summaries. You can do follow up queries that refine results of the initial query, including the summaries, and it also does some computations automatically. People hardly notice it. Github added a feature that you can enter a description of the code you want and it will find multiple OSS projects, fork them (keeping the license), recombine or integrating their code and even translate to other programming languages -- and give you something they call "initial version" that works well in many cases. They also add automatic suggestions to PRs, and suggested PRs for fixing/implementing open issues. They call it something like "advanced templating". It has mixed reactions among programmers but most organizations are using it to some extent. OSS developers actually like it. Wolfram Alpha now takes natural language descriptions of theorems and can prove or disprove many of them. Some people used it to find proofs for open problems. Some mathematicians worry the new generation is getting too dependent on it while the system doesn't really work every time. None even thinks about it replacing them. All the same capabilities, blended seamlessly into previously existing products. Nobody ever chats with an LLM. Nobody calls it AI. They don't have cute names -- they don't have separate names at all. They "live" inside boxes to perform tasks. They are components. This would likely be a much more productive world (I would switch to that world any time). I doubt anybody would be talking about exponential intelligence or worried about all jobs being replaced, much less about some doomsday scenario. If someone suggested these components were conscious people would laugh. It would be like saying like Google Search is conscious. Worse, like Big Tables or ranking algorithms are conscious. ChatGPT didn't ruin AI for people who tried it and never came back. It started training early adopters to think of it as "someone" instead of "something". The other companies then went even further. The entire concept of what LLMs are, what they are expected to be able to do or not, how reliable they are, what is their function in the workplace -- everything about them -- is built on top of the impression that they are basically like a person, because they can produce plausibly human-like interactions. A deception. If you want to use the LLM you're almost always required to interact with them by LARPing -- pretending it is "someone" and not "something", until you start using human words to refer to it, and forget it was just LARPing. That was a choice. Centering the development of LLMs as something that can pretend to be human instead of doing something useful. Building automated NPCs and pretending to be building God wasn't a given of the transformer architecture -- it was their deliberate choice. I think that was a bad idea. But it sure helped them raise money.

• 
  Atlas (@crptAtlas) reported 24 minutes ago

  SOMEONE JUST CLONED THEIR VOICE INTO EVERY LANGUAGE FOR $0 a developer named jamie pine shipped a free GitHub repo called voicebox it copies your exact tone from a couple seconds of audio everything runs locally on your own machine so your data never leaves the room you can put out content in Japanese, Arabic or Polish without saying a single word yourself this is the kind of tool that lets one person sound like a whole media team i broke down how i made Claude 8x smarter save this for when you need it

• 
  Ben (@bensenescu) reported 25 minutes ago

  Github sign in doesn't work for either of your apps @21st_dev @fal

• 
  Yves (@YvesDC0) reported 32 minutes ago

  Phone-recorded this while testing Castfy. Gave it a GitHub URL + prompt → watch the AI automatically navigate and fill login details in real time (stopped before submitting for safety). No manual screen recording. No editing. Just URL + prompt = realistic demo flow. This is exactly what Castfy does: turns any web app into a polished product demo video in minutes. Tired of re-recording demos manually? Reply with your biggest pain 👇 #BuildInPublic #SaaS #IndieHackers