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:

• 
  Henning Kilset 🇺🇦 🌻 (@HKilset) reported 2 minutes ago

  Hey @thsottiaux and team at @OpenAIDevs - since the last update, Codex App has been insanely CPU hungry on my Mac. There are dozens of issues about it on GitHub. The culprit seems to be the Codex Helper and Codex Helper (Renderer) processes. It's getting to the point where the app is hardly usable. Fix on the horizon?

• 
  Edgex (@SahilExec) reported 4 minutes ago

  5. GitHub's Own Storage Layer - Spokes GitHub built a custom storage layer called Spokes that manages repository replication. Every repo has 3 live replicas at all times. Reads are served from the nearest one. Writes are confirmed only after 2 of 3 replicas acknowledge. This is the same pattern as most distributed databases. GitHub just built it specifically for *** objects. 100 million developers. 330 million repositories. Not one commit lost. The reliability isn't magic. It's ***'s design + smart replication + a storage layer built for exactly this problem. Every time you push - you're trusting a system that was designed to be more reliable than any single machine can be.

• 
  Moyosore (@Moyowalker) reported 5 minutes ago

  GitHub needs to fix this rate limits bugs. Daily limit, then boom weekly limit.

• 
  deepak (@depx_____) reported 7 minutes ago

  - Claude for coding. - Supabase for backend. - Vercel for deploying. - Namecheap for domain. - Stripe for payments. - GitHub for version control. - Resend for emails. - Clerk for auth. - Cloudflare for DNS. - PostHog for analytics. - Sentry for error tracking.

• 
  Sean Rivard-Morton (@thunkoid) reported 12 minutes ago

  I’m part of the problem I’ve used 3000 minutes of CICD time in GitHub actions last month Sorry guys

• 
  Bruce (@DegenToDisciple) reported 12 minutes ago

  @1__of_1 Since April last year you can see who lost it all, some survived till 10/10, some then survived until this January You see more and more desperation and scam posting, I just saw a dude post an obvious fake github, must be down bad to do so

• 
  Heavy Polo (@RLPCFelix) reported 13 minutes ago

  @github @GitHubCopilot I pay for Copilot Pro and the mobile coding agent is failing before it edits anything. Simple task: create 3 basic JS smoke-test files. Actual failure: *** rev-parse --abbrev-ref HEADHEAD exit 128 Then: *** checkout copilot/add-js-smoke-test exit 1 This looks like an agent setup bug, not a repo/code issue. Can someone help route this?

• 
  Giorgio Iezzi (@GIezzi18020) reported 14 minutes ago

  @romainhuet @adahstwt I cant connect GitHub to Codex...it keeps showing error in the plug in..

• 
  Anthony Hobday (@hobdaydesign) reported 16 minutes ago

  @henry_daggett One of the recurring issues I’ve had over the years is that some types of software are hard to experience properly unless you spend a wasteful amount of time preparing (e.g. creating a project and using GitHub to keep the code). I’d prefer to listen to other people’s experience.

• 
  Chidanand Tripathi (@thetripathi58) reported 17 minutes ago

  You need an AI pair programmer to write boilerplate, debug logic, and speed up execution. What are your options? GitHub Copilot sends your proprietary codebase to Microsoft servers to feed their massive models. ChatGPT requires you to paste your sensitive intellectual property directly into a public web interface. Cursor forces your entire development workflow through a centralized cloud proxy. In 2026, writing code at speed requires either paying permanent rent for cloud subscriptions or surrendering your company's intellectual property to corporate training engines. Someone built an architecture to bypass this entirely. It acts as your own private AI pair programmer. No data scraping. No cloud dependency. It is called Continue. Install the extension directly inside VS Code or JetBrains. Connect it to a local model running on your own hardware via Ollama. You get lightning-fast autocomplete and chat that never touches the internet. The technical leverage: - Absolute sovereignty. Your proprietary code, logic, and API keys never leave your physical hard drive. - Zero subscription fees. You stop paying a monthly tax to Microsoft just to generate basic functions. - Deep local context. It indexes your exact workspace securely, understanding your specific architecture without uploading it to a third-party server. - Offline execution. You can generate code on an airplane with zero latency. The corporate system wants you renting access to basic intelligence. They build artificial paywalls around code generation to extract recurring revenue forever. Continue tears down the AI monopoly. It is open-source, highly performant, and keeps your intellectual property exactly where it belongs: entirely under your control. Stop playing by their rules. Stop leaking your codebase. Build your own leverage and direct your own reality.

• 
  Sean Rivard-Morton (@thunkoid) reported 23 minutes ago

  @llmDestructor 👀 I think part of the problem is running chron jobs w/ github actions. Should just do it on my own machine

• 
  Scott Wilcox (@hereandtomorrow) reported 24 minutes ago

  Well it was nice while the Opus4.6 and Claude Code and GitHub actions setup was humming along for me....but having to rethink with Opus4.7 and the most recent Claude Code updates. Doing a review and refactor of my agents, memory claude code. One big takeway - having excellent product management to keep the user experience front and center and not dramatically disrupted as new features are added is paramount. Anthropic has fallen down on that front IMHO. Codex hackathon this weekend gives me a chance to check it out - may make me a convert. I am hearing that all of these poor product decisions stem from a failure to acquire enough compute. Uggg. I'll give it the day to see if I can get back on track. I need to release before Monday for a customer.

• 
  Jonas (@wisplite) reported 25 minutes ago

  @TylerNickerson @github React isn't necessarily the problem. React makes it easier to write bad frontend code, because it makes it easier to write frontend code in general.

• 
  I Pun Daddy (@IPunDaddy) reported 25 minutes ago

  GitHub down again? Who else is suffering? #github

• 
  Beelzebub 🇺🇲 (@AtomicBeelzebub) reported 26 minutes ago

  @planefag Github could fix this issue and still appease the devellopers in the replies by just making it so when you first visit the website asking if you are a Contributor or a User, creating a cookie, then giving an extremely similified view with just the downloads and readme for users.