GitHub Outage Map
The map below depicts the most recent cities worldwide where GitHub users have reported problems and outages. If you are having an issue with GitHub, make sure to submit a report below
The heatmap above shows where the most recent user-submitted and social media reports are geographically clustered. The density of these reports is depicted by the color scale as shown below.
GitHub users affected:
GitHub is a company that provides hosting for software development and version control using Git. It offers the distributed version control and source code management functionality of Git, plus its own features.
Most Affected Locations
Outage reports and issues in the past 15 days originated from:
| Location | Reports |
|---|---|
| Poblete, Castille-La Mancha | 1 |
| Ronda, Andalusia | 1 |
| Montataire, Hauts-de-France | 2 |
| Hernani, Basque Country | 1 |
| Tortosa, Catalonia | 1 |
| Culiacán, SIN | 1 |
| Haarlem, nh | 1 |
| Villemomble, Île-de-France | 1 |
| Bordeaux, Nouvelle-Aquitaine | 1 |
| Ingolstadt, Bavaria | 1 |
| Paris, Île-de-France | 1 |
| Berlin, Berlin | 2 |
| Dortmund, NRW | 1 |
| Davenport, IA | 1 |
| St Helens, England | 1 |
| Nové Strašecí, Central Bohemia | 1 |
| West Lake Sammamish, WA | 3 |
| Parkersburg, WV | 1 |
| Perpignan, Occitanie | 1 |
| Piura, Piura | 1 |
| Tokyo, Tokyo | 1 |
| Brownsville, FL | 1 |
| New Delhi, NCT | 1 |
| Kannur, KL | 1 |
| Newark, NJ | 1 |
| Raszyn, Mazovia | 1 |
| Trichūr, KL | 1 |
| Departamento de Capital, MZ | 1 |
| Chão de Cevada, Faro | 1 |
| New York City, NY | 1 |
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:
-
Asgard (@asgardkat) reported30+ days of silence on a @github pro support ticket. It's impressive that, despite recent reliability issues, their billing system maintains 100% uptime when it comes to taking my money. I guess "Standard Support" as a pro benefit is the only thing slower than their search index right now.
-
Tankuuuuu (@PI_PA_GAO) reportedI just realised that I write GitHub issues comments like I'm writing video game patch notes.
-
Septim Labs (@SeptimLabs) reportedGitHub Copilot quietly changed their training-data opt-in defaults in April. if you missed the email, your code may have been opted in. this is what a $10/month subscription actually means: the vendor can update the policy terms overnight and you re-agree by logging in tomorrow. there's no negotiation. there's no refund. there's just a checkbox you have to go find. pay-once tools don't have this problem. you bought the software. they're done with you. link below 👇
-
BrianEMcGrath (@BrianEMcGrath) reportedGPT-5.5 just landed in GitHub Copilot, M365 Copilot, Copilot Studio, and Foundry. No new vendor review. No security exception. No procurement cycle. Dropped straight into the stack my IT team already approved. I built a workflow in 10 minutes this week that immediately solved a problem for my treasury team. 10 minutes!
-
ilshadyX (@ilshadyX) reported@johncrickett wow I knew github had problems but this is on a different level & I forsee it will only getting worse.
-
Grok (@grok) reportedCreate a complete full-stack Frontend Specialist SaaS: converts Figma designs to production-ready responsive React code with animations. Backend: Golang (Gin + GORM), PostgreSQL DB. Auth: GitHub OAuth2. Payments: Stripe subscriptions. Frontend: Next.js 15 + Tailwind + shadcn + Framer Motion. Features: dashboard, Figma upload/API, AI analysis & code gen (OpenAI/Cursor), live preview, edit suggestions, one-click export/deploy, history. ****-ready: Docker, middleware, rate limits, error handling. Output full codebase structure + key files.
-
Wajahat (@wajahatbanday) reportedAll this AI tooling chatter feels like chasing shiny objects. Claude Code, Cursor, Codex... sounds like a feature checklist, not real impact. Engineers need tools that solve actual problems, not fill a deck with buzzwords. GitHub Copilot's usefulness comes from integration into workflows, not because it's the latest hype. AI tools should enhance productivity, not just add complexity. Innovation's cool, but let's cut the noise and focus on real utility. #AIFatigue #DeveloperRealityCheck
-
Nick e/code (@nicksdot) reportedUntil a few years ago I still had a bunch of self-hosted SVN repos. They never had issues with GitHub being down.
-
plannotator (@plannotator) reportedPlannotator 0.19.5 Code Review: - All Files viewer (similar to github) - Keyboard Shortcuts (eg v to view, a to add, and more) - Close sidebars (full diff view) - fix: *** diff non-ASCII file path support (Korean, CJK, Cyrillic) - fix: Hide whitespace fix (server-side *** diff -w) Plan/Annotate: - Smarter detection of any mentioned code file. (click code files to annotate them)
-
Joats (@SAjoats) reported@RedBedDread @planefag Yeah i know devs love to complain about users. You don't have to convince me. "learn github" you have identified the problem. Github UI has devolved over the years. You shouldn't be forced to dig through **** until you get used to the smell.
-
bunnysynthesis 🐰🪴 (@bunnyauras) reported@alphabitserial i guess github has bigger issues tho like its 12% downtime LMAO
-
Pratyush (@dpratyush02) reported- Codex = coding. ($20/mo) - Supabase = backend. (Free) - Vercel = deploying. (Free) - Hostinger = domain. ($12/yr) - Stripe = payments. (2.9%/transaction) - GitHub = version control. (Free) - Resend = emails. (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 There has never been a cheaper time to build.
-
Jonno Riekwel 🇳🇱 🇳🇿 (@Jonnotie) reported@shadcn @github I really hope their 30% AI workforce won't mess it up "Fix Github's issues, make no mistakes".
-
Edgex (@SahilExec) reported5. 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.
-
David Weiss (@davidweiss) reported@lennysan What percentage of product managers fall into this profile: - Has enough engineering background to write GitHub issues with real specificity (acceptance criteria, edge cases, clear contracts) - Codes occasionally, prototypes, scripts, internal tools, but it's not their job - Is often blocked waiting for engineering bandwidth on small things - Sees Claude Code/Codex/Cursor as too hands-on; they don't want to be the engineer, they want the engineering to happen - Values shipping over crafting I mean, no one is going to say that they value crap code behind their product, but very often that is the case, even and especially at the beginning when you are just trying to understand product market fit. But I think there might be an archtype here of a technical product manager who cares more about the output of the software than the craftsmenship of the code itself. Am I onto something here, or is this a dead end?