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 |
|---|---|
| Tlalpan, CDMX | 1 |
| Quilmes, BA | 1 |
| Bengaluru, KA | 1 |
| Yokohama, Kanagawa | 1 |
| Gustavo Adolfo Madero, CDMX | 1 |
| Nice, Provence-Alpes-Côte d'Azur | 1 |
| Brasília, DF | 1 |
| Montataire, Hauts-de-France | 3 |
| Colima, COL | 1 |
| Poblete, Castille-La Mancha | 1 |
| Ronda, Andalusia | 1 |
| 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 |
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:
-
Peter Steinberger 🦞 (@steipete) reported@yxcc Discord or GitHub Issues.
-
Saurabh | NodeOps (@saurra3h) reportedgithub down?
-
Hermes-Agent News (@HermesAgentSol) reportedok wait garrytan/gbrain just crossed 15.9k stars on github. garry tan's personal hermes/openclaw agent brain. opinionated typescript and 2151 forks already. when a yc partner ships their own agent brain on your framework that's a real signal. also teknium landed the xai-oauth credential loop fix overnight. grok-4.3 now reports its real 1m context instead of 256k and the error message finally stopped blaming subscribers for being unsubscribed.
-
Abinash (@implabinash) reported@ThePrimeagen I never faced a single GitHub downtime issue in my workflow. Oh! Sorry, I have been using GitLab for a year now.
-
Sharbel (@sharbel) reportedSomeone opensourced a Chromium browser that passes every bot detection test. Not by injecting JavaScript. Not by patching configs. By recompiling Chromium itself. It's called CloakBrowser. 12,071 stars on GitHub. You swap one import line. That's it. Same Playwright API you already know. Same code you already wrote. Three lines of code. Thirty seconds to go from blocked to unblocked. Here's what it does: → 49 source-level C++ patches baked directly into the Chromium binary. Canvas, WebGL, audio, fonts, GPU, screen resolution, WebRTC, network timing, CDP input behavior, automation signals. All modified before the browser even compiles. → Passes Cloudflare Turnstile. Not sometimes. Every time. Verified live. → Scores 0.9 on reCAPTCHA v3. Human-level. Server-verified. → Passes FingerprintJS and BrowserScan. Tested against 30+ detection sites. 30/30 tests passed. → `humanize=True` flag adds human-like mouse curves, keyboard timing, and scroll patterns. One flag. Behavioral detection gone. → Drop-in replacement for Playwright and Puppeteer. Python and JavaScript both supported. → `pip install cloakbrowser` or `npm install cloakbrowser`. Binary auto-downloads on first run. Zero config. → Auto-updating binary. Background update checks. Always on the latest stealth build. → Optional GeoIP flag auto-detects timezone and locale from your proxy IP. → Docker image available. Try it with zero install: `docker run --rm cloakhq/cloakbrowser cloaktest`. Here's the wildest part: Every other antidetect browser patches JavaScript at runtime. Detection systems catch JavaScript patches. They have for years. That's why your $99/month tool stopped working after two weeks. CloakBrowser patches the C++ source before Cloudflare's systems ever see a single byte. Antibot systems score it as a normal browser. Because it is a normal browser. One that happens to have 49 fingerprint modifications compiled in at the source level. There is no JavaScript to detect. There is no injection to flag. There is nothing to catch. Browserless charges $120/month for cloud browser automation. Bright Data's Scraping Browser starts at $500/month. Multilogin starts at $99/month. Per user. Apify cloud actors run on usage-based billing that scales fast. CloakBrowser: $0. Unlimited scrapes. Unlimited sessions. Your hardware. Your code. Forever. 12,071 stars. 921 forks. Available on PyPI and npm. MIT licensed. MIT licensed. Self-hosted. Free forever. 100% Open Source.
-
Shubh Jain (@shubh19) reported@devXritesh now it’s mostly docs, blogs, github issues, and AI explanations instead of full books
-
Pierce Boggan (@pierceboggan) reported@codingmenace @cristiampereira Yes, that's correct. The new GitHub Copilot app has an experience similar to this that solves that problem, but something to be improved in the Agents window in VS Code.
-
Jeromy Sonne (@JeromySonne) reported@TJ_Bongiorno None of them. MTAs fundamentally are broken technology not worth it. Claude can do a proper lift study DIY or using an open source framework from GitHub. Build don’t buy and save the $$$
-
Yashas (@YashasGunderia) reportedMost AI-native startups will not lose because they ship too slowly. They’ll lose because they ship fast without knowing what actually worked. Coding agents gave every team more velocity. Cleo gives them product memory. Customer feedback, GitHub issues, Slack threads, metrics, tickets, specs, launches, agent traces, all connected into one loop that tells your team and your dev agents what to build next. We’re opening the Cleo waitlist today. For small teams trying to compete with companies 100x their size (link in comments)👇
-
Beau Johnson (@BeauJohnson89) reportedagent skills are becoming the new software package DenisSergeevitch/agents-best-practices > 120 stars on github > created today > provider-neutral skill for codex + claude code > designs and audits agent harnesses > covers tools, permissions, memory, evals, prompt caching, observability, and safety the important line from the readme: the model proposes actions. the harness validates, authorizes, executes, records, and returns observations. that is the whole game. most people keep trying to fix agents with bigger prompts. the real fix is a tighter harness.
-
Emmanuel Olajide (@E_m_m_a_ola) reportedBuild Bulletproof Runbooks & Playbooks Every alert should have a one-click “what to do” guide. Store them in GitHub + link directly in PagerDuty. No more 3 a.m. panic. Just follow the steps and fix it in minutes.
-
craig carpenter (@ccarp87) reported@rfleury @awesomekling AI is bad at writing Rust, so Anthropic's answer is training it on Bun's github bug reports. Rust devs can't help themselves -- they just have to talk about how smart they are in GitHub Issues. They'll have this thing trained in a week.
-
Adi (@wtfaditya_) reportedAs github actions are down, I was thinking what if they were using actions itself to deploy their service, How they gonna fix it (deadlock) And if they are not using github actions then why should i use if they are not using itself @GitHub any help?
-
Frooxius @ MFF - frooxius.bsky.social (@Frooxius) reported@MrRocketFX @ResoniteApp @unity They should be compressed on Resonite side? I'm not quite sure if I understand, it might be better to make GitHub issue for the request at the repo.
-
anil (@2abstract4me) reported@steipete how do u incorporate users feedback? primarily thru github issues? feedback in the sense, how they are using it? what they want. or how a new feature is being received and etc?