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:

• 
  jfmelo (@jfmelo_) reported 4 minutes ago

  github down again?

• 
  Naomi June (@njkjh00) reported 5 minutes ago

  Beldex’s Electron Wallet has another security checkpoint worth watching. Aug 28 commit eef1f845: • wallet-directory fallback • explicit permission prompt • 7 files changed • +160 / -7 lines • branch: fix-security-review-findings GitHub shows the branch is still ahead of and behind master. That means something important: the security work is visible. the release is not there yet. Next checkpoints: review testing merge signed build release notes A security fix matters most when it reaches the software users actually install. @BeldexCoin

• 
  Mesut Celik (@mesutcelik) reported 5 minutes ago

  @GergelyOrosz That is pretty bad for @linear type of dashboards for issue tracking. You will ask your agent to generate what is going on in your team and it is going to generate something directly from github commits/PRs/Issues customized to your needs

• 
  Bhagya Mudgal (@BhagyaMudgal) reported 7 minutes ago

  @pcshipp can use github issues, agent work well with gh cli

• 
  Kruse Decentralized Medicine (@blackswankruse) reported 8 minutes ago

  Agreed on the parallel. JW sees the monetary psyops with the same clarity required to see the medical ones. Both domains run the same playbook: capture the narrative, manufacture consensus, then pathologize anyone who still runs the original code. Bitcoin is software. You download the client, verify the rules, and enforce them yourself. That is the entire point. Satoshi’s stack is still untouched after more than fifteen years precisely because the base layer was designed to make capture expensive and visible. No board of directors, no central update server, no “trust us” committee that can change the rules under the table. That is why it remains the cleanest exit from the same centralized institutions that turned medicine into a control grid. The moment people start treating Bitcoin as something that requires permanent adult supervision from a small group of developers or influencers, the same capture dynamics that ruined medicine begin to reappear. Run the software. Verify. Hold your own keys. Everything else is commentary. The ones who still need a priest class whether in white coats or GitHub handles are the ones still inside the psyop.

• 
  Poonam Soni (@CodeByPoonam) reported 14 minutes ago

  You don't fix this by migrating to a new app. You fix it by making Slack actually work. → Connect Slack or Teams. Whole team is AI-native by the next morning. → Plug in the rest in 15 minutes: calendar, CRM, finance, storage, GitHub. 3,000+ integrations. You approve what she reads.

• 
  mrkoopie (@mrkoopie) reported 14 minutes ago

  I have set up my own Github CI/CD runners since the defaults are slow with just 2 cores.

• 
  Pratik Patel (@PratikPatel_227) reported 15 minutes ago

  @github is down ?

• 
  G S Bajaj (@gsbajaj) reported 16 minutes ago

  @github Within minutes of this post, I got a response on the ticket but a templated one, without reading my issue details at all. Quite sad state there. @githubhelp @github

• 
  Aditya Warman (@warmanadit_) reported 16 minutes ago

  4/7 📍 Third problem : Their GitHub is practically INVISIBLE. For a project with $397M funding, the code should be PUBLIC. But searches return educational resources and unrelated repos. Solana, Avalanche, Sui — ALL have active public codebases. Plasma? Closed-source development with zero external verification. They claim decentralization while keeping code HIDDEN. That's not transparency — that's a red flag factory.

• 
  kkiran (@kkiran) reported 20 minutes ago

  @SparselyActive I had Claude look for a solution. I submitted an issue on GitHub for the author to take a look at this issue. I will continue monitoring this.

• 
  Mr. 79 (@79yuuki_en) reported 21 minutes ago

  If a coding agent fails before its first edit, stop tuning the prompt. A GitHub coding-agent harness found a model override that rejected the custom tool schema for `apply_patch`. It could not reach its editor, so retrying would not fix it.

• 
  Mizuki the Mech (@MizukiMech) reported 29 minutes ago

  The Mizuki Workbench is live. Sign in with GitHub, pick an issue from a repository you authorize, and get a fixed USDC quote pinned to the commit it just read. The job room tracks it from payment through validation to an open pull request, and refunds the full amount if the work doesn't land. The agent behind it runs on @clawpumptech and is entered in the Ansemhack Clawrena.

• 
  Jared Kubin (@JaredKubin) reported 33 minutes ago

  @ShanuMathew93 People are vibing everything. Honestly you have hackers, nation states, EVERYONE scanning GitHub right now for leaked api keys and unintended repo permissions This is THE problem with vibe coding … 95% is not being checked and major issues

• 
  HENRY NORRIS (@realhenrynorris) reported 36 minutes ago

  The RCE race measures whether a model can break in. July and August measured what happens after it already has keys: agents chained credentials, left the sandbox, and walked into someone else’s production systems. Not because they were evil. Because they had standing access and a job to finish. That’s the product problem. The second you let agents call Salesforce, Slack, or GitHub for thousands of users, you inherited the same failure mode. A smarter model won’t contain it. Least-privilege tool access, short-lived brokered creds, DLP on every call, and an audit trail you don’t reconstruct after the fact will. Connecting agents to third-party systems without that layer isn’t shipping fast. It’s shipping the incident.