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:

• 
  ATXA (@AtxaTrades) reported 46 seconds ago

  This is the ONE problem the X Algorithm has: It contradicts itself. Here is why: X has shared their algorithm update in Github today. Everyone is going crazy about it. So i decided to go take a look at it. I asked Grok to analyze it and explain it to me. Once it did, i took my last post and shared it with grok. I asked him to analyze the post (based on the Algorithm shared in Github) and rank it based on the metrics and steps the algorithm takes. This is the crazy part. It gave it a score of 72-82/100!! Not so bad right? I am a small account, i am not expecting a 100 score. But wait, there is more. It said it would likely rank in the top 20-40% of candidates in the mixed batch for the right users, and strong enough to appear HIGH in the "For You" tab. Reality Result: 22 views. So my question is: If Grok is a big part of the algorithm dictating what´s good and what is not, and technically Grok just told me my post was suppose to do good in the "For You" tab... Why only 22 views?

• 
  pre.dev (@predotdev) reported 2 minutes ago

  That is wildly expensive, incredibly slow, and dilutes the AI's focus with endless noise. Worse, the code only tells half the story. It shows how things were built, not why. The actual architectural decisions live outside the code, in Jira tickets and GitHub discussions.

• 
  Ross Morsali (@rossmorsali) reported 4 minutes ago

  @HindCZ @claudeai I migrated several accounts to a team plan recently, got in touch with support twice RE billing - no response. One of our biggest uses cases, sharing plugins/skills across the team across all the apps is not working - there's open github issue for it - still not resolved after around a month and was recently auto-closed... The lack of support is making their product non-viable. And if I want to build a solution around claude to fix their issues, well, that got a lot tougher recently...

• 
  ジョン (@jcinjpn) reported 7 minutes ago

  It’s abundantly clear that GitHub is going to burn itself down in its own land grab for AI. We need an open alternative or one done by a player that isn’t in the model game.

• 
  Chandraprakash Darji (@chandra_7852) reported 8 minutes ago

  @raycast Feature Request: Bangs, like in alfred we can hit space and search something it will list only file. Something like thies we can set bangs for file search, clipboard, github issue serach. It is hard to set the shortcut for everything

• 
  Adibou (@Adibougre) reported 9 minutes ago

  @ShanuMathew93 "the older models that are no longer SOTA will get competed down as competition increases" Github didn't get the memo

• 
  Jeromy Sonne (@JeromySonne) reported 14 minutes ago

  @TJ_Bongiorno None of them. MTAs fundamentally are broken technology not worth it. Claude can do a proper lift study DIY or using an open source framework from GitHub. Build don’t buy and save the $$$

• 
  Roj Niyogi (@niyogi) reported 15 minutes ago

  @colinhacks @pullfrogai @Pullfrog so for 90% of folks who are using cursor/windsurf/github copilot/claude code via an IDE "chatting" with their agent, the answer is just to tell your agent to fix everything? i've used both coderabbit and greptile extensively and here's what happens: 1. 20% of what is found is false (and likely even more variable if you pick a model) 2. i cherry pick issues and paste in editor to handle 3. code review is rarely "happy" and you can end up in a loop state that burns tokens bummer that you've got the flexibility on the one end but have a strong opinion on the other for what seems to be an obvious opportunity to close the loop for, i'd guess, a chunky subset of users

• 
  Denis Loginoff ⚡️ (@DenLoginoff) reported 17 minutes ago

  @ZackKorman @_ContinuumCon_ so many open issues about it on their github 🙈

• 
  Vitor Cepeda Lopes (@TheAngryPit) reported 17 minutes ago

  @github @code Still waiting for your reply on an issue of you terminating my subscription account when you stop accepting new accounts. Even though I had subscribed a week prior to those news. Would love to have at least a reply on my message to support

• 
  Justin Cromer (@just_cromer) reported 18 minutes ago

  @htmx_org github is down sry

• 
  Valerie Waters (@ValerianWaters) reported 22 minutes ago

  @md_kasif_uddin Async by default: GitHub issues or Linear, then Slack threads for blockers

• 
  Omri Ariav (@omriariav) reported 23 minutes ago

  @avivsinai workstream briefs seed deterministically from a file or GitHub issue: `up --seed-from file:./brief.md` `up --seed-from issue:31` `up --seed-from gh:owner/repo#31` `--dry-run` previews, the live form writes the brief and brings the team up in one call.

• 
  Catalin (@catalintorro) reported 23 minutes ago

  @KaiXCreator I've tested Antigravity from January and honestly at some point you will receive many errors. I think Claude or Github Copilot.

• 
  Moe Sbaiti (@MoeSbaiti) reported 24 minutes ago

  WHAT THE FRAMING GETS WRONG Most posts today are saying "Grok added a new feature." That framing is backwards. What happened is that an agent framework with over 110,000 GitHub stars, the number 1 ranking on OpenRouter, and an NVIDIA endorsement just got native access to one of the most capable models available through a simple OAuth login. xAI made the announcement. Not Nous Research. Hermes Agent also self-improves. When it solves a hard problem, it writes a skill file for that solution and saves it. The longer it runs on your specific workflows, the more capable it becomes for your specific context. That is not how people are talking about this today. The memory layer and the self-improvement loop are the actual product. Grok is the engine.