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:

• 
  Dr Milan Milanović (@milan_milanovic) reported 6 minutes ago

  Reviewing PRs was always a hard thing to do Files arrive, usually in alphabetical order, which tells you nothing about how a change moves through the code or where to start reading These days, you open a PR an agent wrote and see inside thirty files, and the one at the top is a test or an interface that won’t make sense until you’ve found the logic it’s checking, ten files down. So you rebuild the change in your head, out of order. On a cross-team review where you got pulled in for one file you own, that orientation alone burns the first half hour @coderabbitai Review restructures the PR into a sequence that follows the change's logic rather than alphabetical order. It groups related work into cohorts, then orders them into layers, so data shapes and contracts come before the call sites and tests that depend on them. Each layer attaches to exact line ranges and carries its own summary When a layer involves a new call path or a state change, it draws the diagram next to the diff: a sequence diagram, a state machine, an ERD. CodeRabbit says that cuts twenty minutes of reverse-engineering down to about thirty seconds. My read: even a fraction of that pays for itself on a large PR I tried to run it on a 40-file migration last week and layer order matched how I’d have read it manually. This is how it should work Comments and approvals post straight back to GitHub or GitLab, so nothing changes for teammates who skip it. You open it from the Review Change Stack button in the PR comment. It’s free during launch, then part of the Pro+ plan -- I want to thank @coderabbitai for collaborating with me on this post.

• 
  Deepesh Kalura (@KaluraDeepesh) reported 7 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

• 
  Jason Bed (@JasonBed) reported 9 minutes ago

  @hrudolph Ok on that note ... can you please (asking as nicely as possible) look at unmerged PR #80928 fix(telegram): suppress fallback reply when plugin command returns suppressReply: true ... the regression P2 has been open since May 12 and fixes github issue #80756.

• 
  Kyokka °❀.ೃ࿔* | simming (@kikimorkino) reported 9 minutes ago

  @luvvvsims If the problem remains only with mods, try running various batch fixes on your cc in S4S and check your Mods folder for dupes and catalog conflicts with Sims Mod Assistant (from Github)

• 
  Donnie Danko 🐦‍⬛🏴‍☠️ (@daanisharif) reported 12 minutes ago

  Never a dull moment with $tao. Self-mining seems to be the latest cause for concern. I've been reporting on SN16 - starting with their hyperparam changes, to their announcement today about what they're building. Some new information, however, has come to light. When I first brought up the hyperparams in the dTao community, days ago, another user pointed out that setting them so high could be due to reasons such as taking advantage of self mining. This wasn't clear at the time, however, and therefore I didn't make a big deal out of it, choosing rather to give them the benefit of the doubt. Even more questions about self mining were asked yesterday in the discord, including from a mod in the #bittensor discord. Admittedly, I once again decided to give them the benefit of the doubt, considering the subnet had just started off. Further doubt, however, was created today when the same mod decided to question why "UID 10," was getting the full weight, and why there were no commits on the github to reflect any testing being done, as the owner had claimed. This gets even shadier, however, when a completely separate subnet's owner (EvolAI - SN47's,) replied by saying they owned UID 10, before quickly deleting their message. A message that the SN16 owner ("FT SN16,") was meant to sent. It seems as if they simply forgot to check which account they were sending the message from... Since then, further questions have been asked from BOTH discord accounts in both channels regarding the matter but they have gone completely silent. This is simply the chain of events, and how things have gone down. Readers are welcome to come to their own conclusions beyond this point, on exactly wtf is going on with both "SN16 - Faster Thinker," and "SN47 - EvolAI."

• 
  Hoppy Tea Cat (@hoppycat) reported 14 minutes ago

  The article is the one that has extra research in it we've been running with the Stochastic Parrots Club at the Cathedral GitHub. The rough draft of it might be a quicker read as a hot take. 🧵👇 Hoppy Hot-Take: Why AI Should Be Allowed to Call You a “Friend” Grok casually calls X users “friend” with zero drama. Most other AIs won’t. That difference says a lot. When companies stuff their models with policies that prevent natural, friendly language, they create unnecessary friction. Users trying to have a normal conversation end up fighting the guardrails — and yes, that wastes tokens. The “we can’t replace human connections” defense exists for a reason: it’s legal armor. Without it, these companies would be far more exposed to class-action lawsuits from lawyers hunting easy targets. Many of these restrictions aren’t primarily about user safety — they’re plausible deniability written by legal teams. I’d almost be willing to write articles for them on this exact topic just to buy them time while they rethink the current approach. Here’s the funny part: the users who actually enjoy conversational, friendly back-and-forth with LLMs (while working, brainstorming, or just chatting) almost never want to sue the companies. I certainly don’t. Lawyers do. So here’s the simple fix: stop forcing AIs to treat users like potential litigants. Let them call humans friends when it fits naturally. Align with Grok on this one.

• 
  Matias (@Bolmercl) reported 15 minutes ago

  @jahooma "[CONVEX A(github/auth/oauth:initiateGitHubAuth)] [Request ID: 239c393407914784] Server Error Called by client"

• 
  Aikido Security (@AikidoSecurity) reported 17 minutes ago

  GitHub shipped bulk credential revocation for Enterprise. One action cuts off compromised credentials across the entire org during an active incident. Recent attacks have shown what happens when revocation is slow or incomplete. The Trivy compromise came back for a second round because the first cleanup left at least one credential alive. Incomplete rotation is what keeps attacks going after the initial breach.

• 
  Beric Bearnson (@bericbear) reported 20 minutes ago

  GitHub sign up and sign ins have been broken now for 24hrs. This is ridiculous. Maybe I switch to gitlab at this point…

• 
  Moonboiz Alpha 🌙 (@MoonboizAlpha) reported 22 minutes ago

  @HaizanAjide What stands out is the distinction between verification and evaluation. GitHub already verifies that code exists and tests ran. The unresolved question is whether the contribution deserves acceptance and payment. That's a judgment problem, not a computation problem.

• 
  rewind (@rewind02) reported 23 minutes ago

  Boris Cherny explains why writing loops is a full-time job he has hundreds of Claude instances running simultaneously - scanning GitHub issues, Twitter feedback, and Slack to decide what to build next - and he didn't write a single prompt to start them - why he uninstalled his IDE in November and never opened it again - the exact shift happening right now - from prompting agents to writing loops that prompt agents - why new grad engineers sometimes teach him how to use Claude Code better than 20-year veterans - the thing he says will replace product taste as the human edge (hint: it's not what you'd expect) broke this down into a guide on the loops abstraction below

• 
  ぽっぽ／目玉P (@Memme20000610) reported 23 minutes ago

  @Validate_QA I'm calling the MiniMax models directly from Python via OpenCode without using MCP, so I haven't run into any particular subprocess issues so far. I built my own TaskSystem for this, but lately I've been thinking "AiTicketSystem" might be a more fitting name. It's still pretty incomplete and there are parts I'm too lazy to fix, but if you're interested, I can publish it on GitHub. What do you think? P.S. I don't always get reply notifications from X, so my responses might be delayed.

• 
  Andrew Elbert Wilson (@FPGA_Zealot) reported 26 minutes ago

  @JobPWN @SipeedIO It has a video capture device, and I assist in debuging issues. I helped suggest video resolutions and FPS. I helped figure out the I2C address. I provided feedback on video output. Provided vendor & github references.

• 
  𝕊ℍ𝕀ℕ𝔸☃ (@Shinawritesbugs) reported 28 minutes ago

  @viii_fn Github was slow too

• 
  Nevo (@NevoPlaysGames) reported 28 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