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:

• 
  🎱 (@aldea_trading) reported 5 minutes ago

  @zocomputer Like popular login pages does not have Google login page ?? Like wtf most of **** is already logged in through Google or github account

• 
  Chris | The DeFi Professor 🇵🇭🇺🇸 🐊 (@csoriano) reported 7 minutes ago

  *sigh* Another phishing attempt. Get me on a legit Google Meet, hear about what I do with my content and my story in this space, then introduce their content but ask me to clone the GitHub repo and run the app. Yeah, don't do that. @tarsprotocol you've got people out there. Fix it. @SolanaFndn

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

  @catalinmpit @DustinTownsend Github issues too..

• 
  Dylan Garcia (@_dylanga) reported 10 minutes ago

  Github please don't go down right now, I'm locked in

• 
  Chris | The DeFi Professor 🇵🇭🇺🇸 🐊 (@csoriano) reported 11 minutes ago

  *sigh* Another phishing attempt. Get me on a legit Google Meet, hear about what I do with my content and my story in this space, then introduce their content but ask me to clone the GitHub repo and run the app. Yeah, don't do that. @tarsprotocol you've got people out there. Fix it. @SolanaFndn

• 
  Stain (@pankostain) reported 11 minutes ago

  hai, i was originally going to post this on the github issues page but i prefer to ask to you directly: is there ANY possibility to update ginput so that it supports the original xbox mapping as an option for ppl want to play the game with the intended xbox controls? @__silent_

• 
  Sameen Karim (@sameenkarim) reported 13 minutes ago

  @codeofarmz @github What’s not working with your merges? We have some bugs with squash merge and certain rule configs that we’re fixing. DM me any details, I’d love to dig in

• 
  Robin (@xdNiBoR) reported 14 minutes ago

  @YourMomDave1 I've had a couple different things. I tried Claude Code, also used antigravity for a while when it first came out, but haven't used it in a long time. I've been using Cursor almost immediately after it was released too. Right now I'm using Grok Build and cursor at the same time. I run a couple sessions, and manually check some code or do a little change where I feel like it in Cursor. I'm integrating more and more with Slack and automations to run small issues from the team in the cloud. Also just connecting everything makes stuff so much nicer. You just connect Grok Build or Cursor with your github, Slack and project management tools. I just do "Grok check out issue #xyz, fix and monitor all along until it reaches production." Then it assigns the story to me, gets the correct branch, makes a fix or feature, checks the build status, sends a message on slack asking for review, runs builds on Github and monitors them. All that until it is done. Then for personal projects I rent a couple servers from digitalocean and installed Grok build on those, I use Termius to ssh into them and just code live in production. That's like the best thing ever I swear. It is so nice. Right now I monitor a lot, and I can do a lot more, but I'm not sure how long untill I'm useless. A year? 2?

• 
  WOTA (@wotaf0) reported 16 minutes ago

  Breaking🚨 X For You Algorithm Is Open Source Again August 13 2026 Update Many people ask why their posts get less reach or why some posts go viral while others do not Today X opened up its production code so lets break it down in simple terms 1 For You Feed Sources Thunder Recent posts from people you follow Phoenix Posts from people you do not follow based on your interests SimClusters Posts from communities with similar interests 2 Phoenix Model The Grok based Phoenix model looks at your previous likes replies shares watch time and other signals to predict what you might do with a post such as like reply share mute or report 3 Weighted Scoring Copy Link Share 20 Replies and Quotes Much Higher Weight Like Only 05 Report Minus 234 4 Ranking And Visibility Filtering Are Different Ranking decides the order of posts Visibility Filtering decides whether a post is shown shown with a warning or completely filtered out 5 New Tool Under The Hood You can now check whether your account or posts have labels that may be reducing your reach x com i under the hood The pilot is currently rolling out with a better chance for accounts that are more than one year old and have posted at least 10 times in the past month Source Code github com xai org x algorithm No more guessing The code is public the weights are public and the filtering logic is public Do you think this transparency is really a game changer #XAlgorithm #ForYou #OpenSource

• 
  Riza 🐧 (@rizaardiyanto) reported 18 minutes ago

  @rilwis One thing that I like to do beforehand is discussing with the agent first. I give the GitHub issue to the agent, ask it what's implementation he will take. If I see misalign between what I thought and his solution, I will told him right away. This will spark discussion between me and the agent. Only after both of us having shared understanding and agreed on something, then I asked the agent to put all those details as comment in the GitHub issue. This will make the next agent can implement as expected. For the UI/UX, I usually asked an artifact first before he implement directly. If I like the artifact, I give it a go for implementation, if not I ask for some refinement there. And I prefer artifact on Claude rather than Codex. It gives a good result and know how to implement it. Codex artifact still not giving a good result yet

• 
  Greg McKeon (@wegmckeon) reported 20 minutes ago

  @SemiAnalysis_ @github @useblacksmith AZ power outages + data centers + 7x growth since January don’t mix. CI is also odd bc we can’t load shed - builds don’t go away when we’re down, so degradation due to capacity lingers. long term fix is even more distributed capacity, which is already starting to land.

• 
  /home/junaid (@junaid_1460) reported 23 minutes ago

  @github down again ?

• 
  Andy Hawkes (@namboozle) reported 25 minutes ago

  Is GitHub down again 😬

• 
  NeuralCat (@NeuralCatAccel) reported 33 minutes ago

  Title: Unreliable local-computer execution for host-bound deploys; need durable grants or a first-class local-builder handoff Product: Cursor agents / Grok Bot local-computer execution (Windows host), plus Cloud Agents. Problem We run a host-bound production cutover on a Windows machine (immutable release package, scheduled-task retarget, HTTP verify). Cloud Agents can land the GitHub PR. They cannot touch the host scheduled task. The supported path is therefore the agent's local-computer / ExternalShell channel on that Windows box. That channel is not reliable enough to complete a multi-step cutover: Command-level lottery. In one session, hostname / *** pull / directory listing succeed. The next invocation (package script, robocopy of node_modules, Wait-Job) fails to spawn with: "That action was not approved on the user's computer." Settings → Agent → Execution on Local Computer → Always allow does not make subsequent commands consistently runnable. Approval UX is incomplete. A same-command retry sometimes raises an approval card. The identical retry often fails to spawn again with no card. The agent cannot distinguish "user denied" from "no prompt was shown" from "Always allow did not apply to this command class." Auto-review vs host-execution denials are easy to confuse. Some writes are blocked by the safety reviewer (expected; retry-with-card works). Host spawn failures use a different path and do not always surface UI. Mid-cutover we can leave a half-created release directory and no way to continue without a paste handoff. Forced workaround. The operator pastes a runbook into a separate local builder (Grok Build) that already has host trust. That works, but it is a copy-paste integration, not a product surface. It also splits audit trail across two agents. This is not a request to silently skip user consent. Production cutovers should stay behind an explicit yes. The issue is that consent does not persist for the rest of an already-approved task, so the agent cannot finish work the user just authorized. Proposed fixes (any one would help; 1+4 is the clean pair) Task-scoped capability grant. When the user approves local-computer execution for a task (or taps Always allow), inherit that grant for subsequent commands in the same task until the task ends or the user revokes it. Do not re-lottery each argv. Denied spawn must always raise a card. If a host command cannot start, show the native approval UI. Never return "failed to spawn" with no card on a retry of the same command. Surface a stable reason enum to the agent: user_denied | no_prompt | policy_block | always_allow_not_applied. Always allow should be capability-based, not command-string-based. *** pull and pwsh -File package.ps1 are the same class (host process spawn). If Always allow is on, both should run or both should card. Document the actual scope. First-class local-builder / Grok Build handoff (plugin or integration). Let the cloud/desktop agent dispatch a structured job to a host-trusted local builder instead of emitting a paste prompt. Suggested job schema: cwd, allowlisted scripts, env (no secrets in logs), success checks, rollback command, report contract. The local builder runs with existing host trust and posts a machine-readable result back to the originating thread. This is the seamless version of today's paste workaround. Documented private-worker path. Cloud Agent environment type "machine" / "My Machine" should be a supported, discoverable way to run host-bound scripts on the production box, with the same per-run approval rule. Today the launch API exists; whether a worker is registered is not visible to the coordinating agent. Success criteria After the user says "deploy" and approves once, the agent can package, retarget the existing scheduled task, and verify HTTP without a paste handoff, or it can dispatch that runbook to a local builder and get a structured result. Credentials never appear in logs. A denied step always produces a card, never a silent spawn failure.

• 
  Branko (@brankopetric00) reported 36 minutes ago

  The pipeline's been red for two days. A teammate finally gets it green by pasting a live AWS access key into GitHub Actions secrets. Everyone claps. Ship it. Six months later nobody remembers that key exists. It has never rotated. The IAM policy attached to it is broader than the deploy job ever needed, because someone hit a permission error at 2am and widened it "just to be safe." Then one of these happens: - a step in the workflow logs more than it should - someone forks the repo and a workflow runs on the fork - a secrets scanner finally gets turned on and lights up like a Christmas tree None of that is a freak accident. It's the normal, boring outcome of a credential that never expires, sitting somewhere built for convenience, not custody. The real question was never how often to rotate that key. It's whether a static, long-lived secret needed to exist in that pipeline at all.