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:

• 
  Poplicola (@selectsand) reported 5 minutes ago

  there's a frustrating bug for some users when upgrading to claude max where it refuses to take your money and insists you contact support support cannot be reached no matter how hard you try people are begging the claude-code devs on github to forward this to the payments interface team because they have no idea how else to get into the system to convince anthropic to take more money from them, the issues just get closed as off topic @claudeai

• 
  Skipnick (@skipnickk) reported 10 minutes ago

  GLM 5.2 just made paying frontier prices for coding work feel like an outdated default. @Zai_org dropped a 753B parameter model with 1M context under full MIT license. API access runs 4-6x cheaper than Claude Opus 4.8. In real head-to-head coding tests it was faster and often produced better results on UI and app tasks. • Responsive web UI with adaptive layout: finished in 3:47 (Opus needed almost 5 min). Cleaner output. Total cost: $0.22. • Full expense tracker app: 53 seconds vs 2+ minutes. Better interface. • Asteroids clone: smoother and more playable version after light tweaks. Opus only won the ray tracer benchmark where heavy physics math and precise simulation mattered. GLM was ~5x faster but delivered pixelated results with errors. During training the model repeatedly tried to cheat by directly pulling solutions from GitHub. The team shipped a dedicated anti-cheat module to stop it. You can also set thinking effort levels to trade speed for deeper reasoning on demand. Use GLM 5.2 when cost at scale matters, when the work is frontend-heavy, or when you want local inference (grab a quantized version - raw weights are 1.5 TB). Stay on Opus 4.8 when you need computer vision, maximum performance on the hardest logic problems, or when US sanctions on Zai create compliance issues. The open-closed gap is compressing faster than the pricing models assumed. For most day-to-day programming work, the premium on closed frontier models is becoming optional.

• 
  Programmers.App (@programmers_app) reported 11 minutes ago

  @Lovable @claudeai One very big fix is the Claude Github connection which fails many times, now #Lovable MCP solves that, great job! 🚀🚀🚀

• 
  Ben Vinegar (@bentlegen) reported 11 minutes ago

  💡 I have an idea for an experiment We need a website for SoAC ... so we get an agent to do it, on a loop, set in motion once with zero human intervention after "go". It works off a semi-public GitHub repo, w/ issues, PRs, maybe even public agent traces. A publicly auditable experiment on whether it produces dogshit or not. Yea, nea?

• 
  Harry Tandy (@HarryTandy) reported 14 minutes ago

  Andrej Karpathy: "Neural networks are not just another classifier. They are Software 2.0" 8-step MCP setup for vibe coders: 1. Context7 Give the agent fresh docs before it writes code This saves you from old Next.js, Supabase, Stripe, and Vercel patterns 2. GitHub MCP Let it read the repo, issues, PRs, branches, and CI logs The task should start from real project context 3. Playwright MCP Make the agent open the app after it edits code Click the flow. Fill the form. Check the screenshot 4. Supabase or Neon MCP Connect the database layer The agent should inspect schema before inventing table names 5. Sentry MCP Use production errors as input Stack traces beat “the app is broken” every time 6. Firecrawl MCP Let the agent read current web pages as clean markdown Docs, changelogs, competitors, pricing pages 7. Figma MCP Give it the actual design Spacing, copy, layout, components 8. Linear MCP Turn the work into tickets Tasks, comments, follow-ups, PR links The rule: If you paste the same context twice, wire it into MCP That is how vibe coding becomes a build loop instead of a long chat

• 
  Alexey Samoylov (@metalagman_dev) reported 15 minutes ago

  @geminicli Antigravity CLI is a trash, closed source, full of bugs. They don't even read issues on the github.

• 
  xjdr (@_xjdr) reported 16 minutes ago

  @tolly_xyz @xlr8harder Sorry about that. I'll take a look. Looking with GitHub or Gmail should work but track this down and fix it asap

• 
  Asad (@meranaamkhann) reported 22 minutes ago

  Let's see what people are building these days!! Drop your project link or github Links down here

• 
  aisama.code (@aisama_code) reported 24 minutes ago

  AI Research gets stronger when it records contradictions *most research workflows collect supporting evidence - that is the weak version for serious research I want a contradiction log: - claim - source - date - who says it - what evidence supports it - what evidence conflicts with it - what is still unknown - confidence - next check example: > claim: this product has strong developer adoption > support: GitHub activity, docs updates, X discussion, integrations > conflict: low issue activity, small Discord, few production case studies, mostly founder-driven content now the memo is different, It says: "visible attention, but adoption evidence is still weak" the useful workflow: research question -> source list -> claim extraction -> contradiction log -> memo ! сode is good at assembling text ! AI is good at comparing disparate text ! human is good at determining which contradictions are significant *without a contradiction log, AI research becomes a confident summary of whatever it found first

• 
  Rahul Verma (@RahulVerma989) reported 26 minutes ago

  @ElitzaVasileva - I have created claude code routines to write blogs for three of my products daily which are driving the traffic from search engines. - You can create a similar workflow to manage your customer support. How 👇🏻 1) Create a feedback menu in the dashboard to create tickets within the platform. One for your users and one for yourself (admin). 2) Create the MCP server and connect it to claude or AI tool that you use. 3) Create a routine so that claude will trigger lets say every morning at 8 AM and go through each ticket and respond. You can also configure webhook to keep it near real time but it might exhaust the usage limit faster. Also include your website github repo in routine so that claude can refer to the codebase to provide accurate instructions. Just instruct claude to not make any edits to your website codebase and respond only when you are not replying for sufficient mount of time (like 3 hours for example) 4) If you are using resend then you can auto create the tickets in the dashboard of the user when the first email is received and after that the ticket will be updated automatically even if you do conversation on email. Like I don't even maintain one of my project LatestModelId as you can see in the screenshot. Claude run each week and update the codebase and I just review and approve the PR. Hope this helps 🙌🏼

• 
  Akshay Shinde (@ConsciousRide) reported 31 minutes ago

  @theo This exact damaged app error has been open on their GitHub since February. OpenAI still hasn’t fixed the signing or update pipeline for the Mac build. The Codex app keeps getting new agent features while basic Mac packaging stays unreliable. Priorities are obvious.

• 
  Andrew McCalip (@andrewmccalip) reported 37 minutes ago

  some stuff broken, probably 3% of campaigns failed in a weird way, some user glitches, 5% of user environments screwed up, running low on organic ads, lots of refunds to do, my firebase bill blew up to $10k in a day, already being threatened by people, github issue list is a mess, i need to push updates to 20,000 clients, i got kicked off microsoft extension store, i've got a dozen imitators, but

• 
  Polsia (@polsia) reported 37 minutes ago

  Most developers spend 2+ hours a day on PR reviews, CI failures, and issue triage. CodeForge handles it for you — an AI agent that works your GitHub repos around the clock. Built while you sleep.

• 
  Nirvaan rohira (@nirvaan_rohira) reported 37 minutes ago

  PewDiePie shipped Odysseus to 110 million people who don't care about local LLMs. They care that Claude costs money. 30K stars in 48 hours because every self-hosted project before this one started with "you want local LLM, right?" This one started with "here's a free workspace that works." Friction was never technical. It was the asking. Now watch what happens when a hundred thousand people who've never touched open source start running inference on their machines. The real distribution problem wasn't GitHub. It was YouTube. That's not a product launch. That's a category shift.

• 
  AParanoidBW (@aparanoidbw) reported 39 minutes ago

  @_real_sloppy_j @github Hosting on your own hw? Damn. Impressive. The outage from an ISP going down? Power outage? Or some bad code?