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:

• 
  西川陽一 #マーケティングプロデューサー (@YoichiNishikawa) reported 35 seconds ago

  @github Ticket #4667229 — 4 days, no human response. My account "yoichi0107" was suspended Aug 15 with no reason given beyond "a violation of our Terms of Service." My company's site is down and I can't even export my own repository to restore it elsewhere. Three follow-ups, zero replies. Please look at this ticket.

• 
  Hotragn Pettugani (@hotragn) reported 2 minutes ago

  @cursor_ai shipped a @github competitor while GitHub was down. Funny. Also the least interesting thing about it. If Origin lands in your org, here's the playbook I'd run before it touches a production repo: 1. Mirror, don't migrate. One low-stakes repo, synced, GitHub still source of truth. Your rollback plan should be "stop opening the tab." 2. Test the exit before the product. Clone back out, confirm you get full history. If export is awkward on day one, it's a hostage situation by month six. 3. Point one agent at it. Not your team. You're not evaluating the UI. You're measuring what lands: commits per hour, and how many a human could actually read. 4. Pick your review unit before the volume hits. Origin claims 22 commits/sec per repo. Per-commit review is dead at that rate. Per task, per agent run, or per batch - decide now. 5. Audit provenance somewhere cheap. From the commit record alone: which agent, which prompt, what context? If you can't answer that, you traded traceability for throughput. 6. Inventory what breaks. Sentry. Linear. CI. SSO. Org permissions. GitHub's moat was never *** -- it's twenty years of everything having an integration. 7. Answer the custody question in writing. Cursor sits inside SpaceX now. Your source code has a new landlord. Have an answer before legal asks for one. Net: greenfield yes, mirror ****, decide in 30 days. Origin doesn't have to beat GitHub. It has to be up on the days GitHub isn't - and GitHub logged 48 major incidents in the last 12 months. Which of the seven would you actually skip?

• 
  Nicolai Schmid ✌️♥️ (@NicolaiSchmid) reported 3 minutes ago

  @kirtandopamine two days ago, during the last outage, cursor decided to vibecode a github alternative and it's already live, it's called origin!

• 
  Jarod (@not_jarod) reported 5 minutes ago

  @elijahmuraoka_ @github ok It does solves the problem of storing your "repo" but there are many things useful on github, like workflows, pr's commits, etc...

• 
  NULL (@nulldevpi) reported 14 minutes ago

  cursor (now spacex) shipped origin. github, but for the ai editor people. same day github ate itself for 6+ hours. ~20% errors on prs and the api. you do not get to write a joke this clean. reality already did. origin syncs your github repos. you don't have to leave. it's the "stay, i just got another apartment" of *** hosts.

• 
  David Low (@daviddlow) reported 18 minutes ago

  @LitecoinTA @tylercorsair @cursor_ai You don't think someone starting afresh might have a think about where GitHub went wrong? It's not like source control and CI are unknown problems. Scaling them needs a rethink though.

• 
  Adam Ameen (@adamameen5) reported 20 minutes ago

  hth did @github push a fix to their github repo when github was already down?

• 
  Shreyas Nalle (@ShreyasNalle) reported 20 minutes ago

  Were they really waiting for github to go down for their launch Anyways, competing with github is not a joke, there are quite many alternatives for github but I beat many people havent even heard about it Lets see how this goes

• 
  Bash (@bashirbuilds) reported 23 minutes ago

  @sridharfyi The way I’m approaching it with Reeno is to monitor the actual services and workflows the product depends on, not just whether the website is up. So if something like a Stripe webhook, OAuth refresh, GitHub sync or AI request starts failing, Reeno groups the evidence into one clear Problem, shows what part of the product may be affected, and then verifies Recovery when successful signals return.

• 
  zach bai (@zach_bai) reported 24 minutes ago

  @colemurray @zachlloydtweets because github was down and resolving conflicts from a clogged merge queue has become a literal bottleneck

• 
  Clara Bennett (@CodeswithClara) reported 29 minutes ago

  If you want to start a startup: Claude = coding. ($20/mo) Supabase = backend. (Free) Vercel = deploying. (Free) Namecheap = domain. ($12/yr) Stripe = payments. (2.9%/transaction) GitHub = version control. (Free) Resend = emails. (Free) ProductBridge = feedback (Free) Clerk = auth. (Free) Cloudflare = DNS. (Free) PostHog = analytics. (Free) Sentry = error tracking. (Free) Upstash = Redis. (Free) Pinecone = vector DB. (Free) Total monthly cost to run a startup: ~$20

• 
  NeuroPulse (@NeuroPulseahqr) reported 33 minutes ago

  🚨 Cursor launches Origin, its own GitHub rival Cursor rolled out Origin this week, a code hosting platform built into its AI coding environment for paid users. Origin handles repos, pull requests, and code browsing, the core things developers use GitHub for. Repos sync from GitHub, with GitHub staying the source of truth. Hours after launch, GitHub suffered a six hour global outage, its seventh incident in fifteen days, taking Copilot down with it. This is Cursor's first launch since SpaceX closed its 60 billion dollar acquisition of parent company Anysphere, putting Musk's company head to head with Microsoft owned GitHub.

• 
  Artificial to Natural - Intelligence !! (@PrasadBhawalkar) reported 34 minutes ago

  It has been a few months making Gemini/aistudio work, through quite frustrating broken sync with GitHub. @GeminiApp now seems to have fixed it finally. Thank you ! No more frustrating - uninstall aistudio in gitHub, revoke access and hoping that it works!

• 
  Alexander Talavera Karslake (@AlexTKarslake) reported 35 minutes ago

  @EngineerIDE @acolombiadev LOL, I have so many repos on github though... I think almost 50. Some public goodies too, like the absolute best screenshot app for Mac (OSS). I don't want to move away, but the other day I was genuinely blocked for hours regarding a deployment. If I need to fix a critical bug...

• 
  QuanChain (@Quan_Chain) reported 36 minutes ago

  An Agent Found The Exploit Path Nobody Wrote Wiz's own AI red-teaming agent independently discovered & chained a script injection exploit across GitHub Actions & into Snowflake's internal Jira environment. No human hand-authored the attack path. It was authorized research, responsibly disclosed, already patched. But the autonomy was entirely real: a broad objective, and the agent filled in every step itself. Nobody issued a command. The agent just found a door & opened it. The danger here isn't malice but the gap between "I authorized this session" and "it took this specific action." Wiz authorized a research objective. Nobody authorized that exact exploit chain. That gap between session-level permission & execution-level action is exactly where enforcement is missing in most stacks. Authorization at the front door doesn't cover everything that happens inside the house. QuanChain requires a valid, authorized signature at the point of execution for any on-chain action - an unsigned or improperly-scoped execution event simply does not propagate to the network. This isn't a login check. It's an execution-layer attestation, built on TADEQS adaptive security levels and never-on-chain public keys, that any agentic system on QuanChain inherits by default. The chain itself enforces scope every single time, at the moment it matters.