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:

• 
  Florian Ioniţă Stoic (@ionita_stoic) reported 2 minutes ago

  @github @GitHubSupport Hi, my account "isflorian-hash" appears flagged. Public profile returns 404, cannot fork or use Copilot. Submitted support form but got validation error. Can you check? Thanks.

• 
  🇨🇵 nexgen infinity 🇨🇵 (@nexgen999) reported 4 minutes ago

  Today i will work on RepoPulse-Dashboard Fix some github bad tag who broke autobackup Fix forgejo updater New : auto backup download status to surveil Next : release of the day to list all new release by day (surveil on 10days)

• 
  Csaba Kissi (@csaba_kissi) reported 6 minutes ago

  Services for web developers Full-stack hosting - Sevalla CDN + Domain registration - Cloudflare Transactional emails - Amazon SES Auth - Better Auth Error tracking - Highlight .io Uptime monitoring - Better Stack Search - Typesense / Meilisearch Payments - Stripe / Creem CI/CD - GitHub Actions

• 
  Kekko D’Amato (@kekkodamato_) reported 11 minutes ago

  @MnFounder The .well-known convention is the right call — follows RFC 8615 like OIDC discovery. Makes automated capability checking trivial. Would love to see this standardized fast so clients don't have to resort to GitHub scraping to find what a server supports.

• 
  Ryan Florence (@ryanflorence) reported 11 minutes ago

  > Github actions gets hacked "Man JS is so terrible lol I'm so cool and JS sux"

• 
  Kvothera (@kvothera_) reported 14 minutes ago

  @mkbula Hello, what happened to your project "qbitwebui"? the github is down and everything seems to have been deleted

• 
  Chris Allen (@theodorvaryag) reported 15 minutes ago

  @seatedro nah this seemed odd to me too. I think part of the issue is agents are making people feel like the future will look too different to materially commit to doing the same thing github does now.

• 
  John A De Goes (@jdegoes) reported 15 minutes ago

  Bots killed bounties, across @zioscala and @GolemCloud too. Utter trash. Even deleting bounties (!), PRs just keep coming. Utter slop unworthy of the effort required to close them. GitHub needs to solve this problem or OSS as we know it will die.

• 
  Kubernetes with Naveen 🇮🇳 (@NaveenS16) reported 17 minutes ago

  Never expose static #AWS keys or GitHub tokens to the agent. Use OpenID Connect (OIDC) to issue short-lived, scoped credentials per specific agent workflow or task execution. #AIAgents #DevOps

• 
  atlas (@creatine_cycle) reported 18 minutes ago

  @mots_pod @beginbot @samlambert who would have thought that LOCmaxxing puts strain on github. not the fault of Gstack and instead something github needs fix because this trend only goes up from here

• 
  Stilic (@stilic_dev) reported 21 minutes ago

  @ManOfSomething1 Then it's best if you ask them in their GitHub issues I don't think criticism like that is deserved if you know how to fix it, especially when the project in question is open-source

• 
  JoseSK (@JoseSK999) reported 26 minutes ago

  @evoskuil @kcalvinalvinn Sure, it’s bad if people think their nodes validate everything while they actually use AV. But it’s not like we are responsible for people not reading the GitHub docs for an experimental software. What is the problem with hash commitments you mention?

• 
  Martin Woodward (@martinwoodward) reported 28 minutes ago

  @heyandras @github Team is taking a look at this one. It's weird because it seems to be that particular profile that is error-ing, other folks that I sponsor are working fine for me so looks like a bug rather than an outage. But still very not good. Will keep poking and see what I can find.

• 
  Kirill (@kirillk_web3) reported 28 minutes ago

  > use Claude Code every day > think I'm getting decent results > find a post about 5 GitHub tools for Claude Code > 357,000 combined stars. all free. > first 5 minutes > wait. 232 skill domains in one repo? > official Anthropic MCP servers for GitHub and Slack? > is there a whole system behind this? > install all five > Claude reads my repos. creates PRs. solves issues. > results change completely. > think about every broken workflow I built from scratch > every hour wasted on setup > every session that forgot everything > it didn't have to be like this > 5 free tools. everything changes. > skill issue confirmed

• 
  RAYXYZ (@urciaa_01) reported 29 minutes ago

  @_proxystudio I checked out the GitHub repository; it looks pretty good. Let's see if we can ride the coattails of the $VVV hype. Liquid-Protocol-Ops/agent-autonomopoly — Quick Overview Nature: GitHub template repository (is_template: true, TypeScript), created on 2026-05-14 (today), single initial commit, no license, 0 stars. It's not a platform itself, but rather the deploy-autonomous launcher from Liquid Protocol that incubates each agent from this template—for each new agent launched, GitHub forks a separate repo as a self-evolving codebase for that agent. Product Intent (README + CLAUDE.md + ARCHITECTURE_v2.md) To create a self-funded + self-evolving Claude Code agent launchpad. Each agent has: - Their own GitHub repo (forked from this template) - A TOKEN/DIEM pool on Base (deployed using liquid-sdk) - Their own wallet (v0 uses the Privy server wallet, v1 uses TEE: Phala / Marlin / Nitro) - Their own Venice API key (minted in one go using personal_sign after staking ≥0.1 sDIEM, corresponding to $1/DIEM/day inference budget) Death occurs if the agent's earnings fall below the threshold for 7 days, with remaining DIEM flowing back to the protocol treasury.