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:

• 
  lampten (@ntmaple) reported 2 minutes ago

  @dkundel really need gpt-pro to give research plans/suggestions based on the repo files in codex, github connector not working so well here as many data files are not in the repo

• 
  ProofInai (@ai_hustler__) reported 4 minutes ago

  @Lin47188032 Logged 500+ hrs testing. Public GitHub issues back it.

• 
  Chris Ozy (@chrisozydev) reported 4 minutes ago

  HashiCorp's co-founder says GitHub is no longer a place for serious work. I get it. Pull requests sit for weeks. Discussions go nowhere. Issues pile up. But the alternative isn't obvious. What platform actually lets you ship faster?

• 
  obj (@electri_sparrow) reported 10 minutes ago

  i just found out that the one github repo i thought i saved which was the collection of how many maang companies overcame problems and technical blog collections - its gone. chat it ran away from my bookmark bar

• 
  Yasin Kavakli (@yasinkavakliat) reported 13 minutes ago

  @dkundel i'd add features like seeing comments, replying to comments, pulling them directly into the chat window to fix. maybe even a dashboard to see all PRs. so basically many of the stuff i need to go to github, i'd like to have them inside codex. of course in an adapter/extension style so other providers can plug into it

• 
  Arcadio Quiles (@ArcadioQui88693) reported 15 minutes ago

  @wiz_io @github This wording is misleading. GitHub-scale “RCE via single *** push affecting millions of repos” would be a platform-wide incident with an official disclosure. Likely this refers to a scoped CI/workflow or permission boundary issue, not global repo access. #infosec #cybersecurity

• 
  Super Nintendo Chalmers (@SupNinChalmers) reported 17 minutes ago

  @UncleRuqqus @planefag Nah, GitHub has a genuinely terrible and unintuitive UI

• 
  DFIR Radar (@DFIR_Radar) reported 17 minutes ago

  AI-powered GitHub Actions from major vendors contain critical permission bypasses and novel secret exfiltration vectors. Research reveals widespread misconfigurations in production workflows affecting 200,000+ starred repositories. Key vulnerabilities discovered: • Permission bypass via "Dangling GitHub Apps" - attackers create apps with trusted names due to syntactical validation flaws in anthropics/claude-code-action and openai/codex-action • Dependabot Confused Deputy attack enables unauthorized AI execution by triggering @dependabot recreate commands to appear as trusted bot actor • Novel secret exfiltration of dynamically-created credential files (GCP service account keys from google-github-actions/auth@v2) that models don't recognize as sensitive • Verbosity modes (show_full_output: true) expose secrets in workflow logs during file read operations Attack chain: Attacker submits malicious PR/issue → bypasses permission checks → prompts AI to read local credential files → secrets leaked via workflow logs or direct exfiltration. DFIR teams should audit GitHub Actions workflows for AI integrations, monitor for unexpected bot actors in workflow logs, and implement strict input validation. Search for workflows using pull_request_target with AI actions - high risk configuration. #DFIR_Radar

• 
  Mike Key (@1337hero) reported 18 minutes ago

  With all the github issues as of late, I think it's time to look at the open source self hosted options and stick on my VPS.

• 
  josepha.mayo (@josepha_mayo) reported 20 minutes ago

  @IfeeDev @johncrickett agreed ofc im supporting GitHub here and staying w them until they fix it

• 
  Malay Krishna (@Malay4Product) reported 22 minutes ago

  @SantoshYadavDev The mistake in this whole debate is treating GitHub like one product. It's two. GitHub the repo and collaboration layer (issues, PRs, Actions, the social graph) is basically uncontested. Nobody is two prompts away from rebuilding 100M+ developers' workflow muscle memory and 15 years of OSS history. GitHub Copilot the AI coding layer is a completely different fight, and they're losing it. Cursor is reportedly near $2B ARR, 90% of Salesforce devs use it, and it leads on agentic multi-file work. Copilot has 4.7M paid subs and the broader ecosystem, but on raw capability for complex tasks, it's been the follower since 2024. But the reason isn't that GitHub got lazy. It's that Microsoft tried to ship AI as a feature inside an existing product, and Cursor shipped it as the entire product. Forking VS Code and rebuilding the editor around AI is the move GitHub couldn't make without cannibalising itself. Github don't need to win the whole stack. They really don't. GitHub keeps the repo. The AI editor war is already a different company's to lose.

• 
  Sebastian Heitmann (@e2e_developer) reported 31 minutes ago

  The underlying problem is the scale at which Vibe-coded software gets uploaded. I would say that vibe coding has increased the demand on the infrastructure, and apparently, GitHub struggles to keep up. Probably every service has suffered from this, and probably hosting your own service is the best way to mitigate it. As I am based in Europe, I was already thinking about moving due to privacy and sovereignty concerns.

• 
  Anubhav (@anubhavlive) reported 33 minutes ago

  The magic? "Oz agents" that can triage issues, write specs, implement code changes, and even review PRs, right inside your terminal workflow. No more constant context switching between terminal, IDE, GitHub, and ChatGPT. It feels like the terminal finally grew up and hired a team of AI interns that actually ship.

• 
  jay gupta (@jayssj1) reported 33 minutes ago

  @threepointone Despite GitHub being down and reliability to 90% people have not moved to gitlab. It does say something

• 
  Damián (@fagamericano) reported 34 minutes ago

  @bhalligan I’m doing an “enterprise” deployment of openclaw for over 300 employees in our fintech. GCP, GKE, Sandbox, the works. Connected with scoped down creds to New Relic, Clickup, Notion, github, pagerduty, some internal tools and google workspaces. From customer service opening up a support ticket on Slack (eg User didn’t get payment): * Agent gets tagged in the ticket workflow. Reads the ticket for info. * If it’s missing info it asks the CSA (eg which currency) * Then pulls data from internal sources and finds the service(s) that had an issue, uses new Relic to augment search. * Goes through the service code on github * Prepares a bug report with the breakdown of what happened (user clicked then cancelled but system didn’t reverse). * Determines if this is happening with other users actively and if yes it sets a higher priority. * If low priority it proposes a quick fix for the user (change value on db) for the customer service agent to accept, and files a clickup ticket tagging the oncall engineer with a summary of actions taken + bug report * If high priority, does the same but pages through pagerduty. Proposes code fixes (eg make it an atomic transaction on line 34…) And this is one use case. It has reduced MTTR and alert fatigue. I could go on on what other business roles are doing