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 |
Check Current Status
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@EndGovTyranny Please file a github issue with more infos - with that alone we can't help. That's likely a weird model edge case. If you want a fast fix, use one of the top-gen models (OAI, Anthropic)
-
Lux Sp4rk (@lux_sp4rk) reportedI dunno why I even humor this html > markdown trend. It's clearly not. Reality is that Markdown renders to HTML anyway. I.E: A Github issue is *not* raw markdown. The ByteRover argument relies on a false dichotomy.
-
Moe Sbaiti (@MoeSbaiti) reportedWHAT THE FRAMING GETS WRONG Most posts today are saying "Grok added a new feature." That framing is backwards. What happened is that an agent framework with over 110,000 GitHub stars, the number 1 ranking on OpenRouter, and an NVIDIA endorsement just got native access to one of the most capable models available through a simple OAuth login. xAI made the announcement. Not Nous Research. Hermes Agent also self-improves. When it solves a hard problem, it writes a skill file for that solution and saves it. The longer it runs on your specific workflows, the more capable it becomes for your specific context. That is not how people are talking about this today. The memory layer and the self-improvement loop are the actual product. Grok is the engine.
-
Java (@rishabhjava) reported@github How about the existing product stops going down first
-
nostalgicgareth (space/acc) (@NostaIgicGareth) reportedDev’s GitHub is giving issues to claim @0xblockXBT send your wallet address I’ll redev it quick - sorry to the others who bought this CA, we tried our best, PumpFun issue…
-
AtomicNodes (@AtomicNodes) reportedHermes Agent vs OpenClaw on Qwen 3.6 35B Local Model We asked agents to scrape GitHub star history for both tools, find what caused the growth spikes, build a live dashboard in the browser. MacBook Pro M5 Max 64Gb OpenClaw: 203k tokens, 12m 01s - wrote a bash script Hermes: 257k tokens, 33m 01s - wrote a SKILL.md OpenClaw: hit GitHub API, got truncated responses, paginated through contributors, pulled star-history JSON, found a security incident in OpenClaw's history, fetched SVGs, fixed broken HTML from trimming, rewrote it clean. Hermes: parallel tool calls across GitHub API, web search, and browser. Hit Google rate limit, auto-switched to DuckDuckGo. Fetched article contents, mapped viral moments, then built the dashboard. Both shipped a live dashboard with star growth charts and spike annotations
-
opdroid1234 (@opdroid1234) reported@HotAisle I do think making money on "github actions is too slow for agents" zeitgeist might be the same kind of side business for you that selling turbines is for boom supersonic
-
nadya (@sosidudku) reportedran Hermes Agent vs OpenClaw on local model Qwen 3.6 35B task: scrape GitHub star history, find what caused the growth spikes, build a live dashboard in the browser OpenClaw: 203k tokens, 12m 01s — wrote a bash script Hermes: 257k tokens, 33m 01s — wrote a SKILL.md OpenClaw: hit GitHub API, got truncated responses, paginated through contributors, pulled star-history JSON, found a security incident in OpenClaw's history, fetched SVGs, fixed broken HTML from trimming, rewrote it clean. Hermes: parallel tool calls across GitHub API, web search, and browser. Hit Google rate limit, auto-switched to DuckDuckGo. Fetched article contents, mapped viral moments, then built the dashboard. Both shipped a live dashboard with star growth charts and spike annotations.
-
Alex Derocq (@akaasten) reported@steipete Crazy how the GitHub "@codex review this" feature is way better than the local review. It spots more issues like 90% of the time.
-
Anthony Shew (@anthonysheww) reported@KareemMahlees @cramforce I’m not aware of any issues if that nature. Can you file a GitHub Issue with a reproduction?
-
Aki Ranin (@aki_ranin) reportedNew Claude Code master prompt: "/goal assign next GitHub issue and start PR, iterate until no critical or high issues found with PR review skill"
-
Crystalwizard (@crystalwizard) reported@omnivaughn @ClaudeDevs you are that's not an issue with github itself? github has copilot and is microsoft - and might be restricting other AI
-
Franz Hemmer (@franzhemmer) reported@burkeholland @github Anyone else getting this on first session request? Error: Execution failed: Error: 400 "checking third-party user token: bad request: Personal Access Tokens are not supported for this endpoint\n" (Request ID: E599:3D91FF:607E4C:690DC2:6A075036) I had copilot scrutinize that there is no trace of a PAT anywhere and that I'm authenticating correctly with OAuth. No issues in my account setup - all looks green and connected.
-
Avinash (@amaurya888) reportedGitHub Actions down? The runner is not picking up the queued job. @github @githubstatus @GitHubEnt
-
Mind Prison (@M1ndPrison) reported@GlenBradley Yes, I have gone deep into it in the past as well. Haven't had time to look at the current update, but the problem has been that the code on github is mostly irrelevant. The important bits are all the parts that aren't public. There is no way to no how the ML algo is ultimately weighting all the parameters. Most importantly, I've catalogued many accounts posting exactly the same content with orders of magnitude differences in reach. The thing that would make this platform useable would be to fully eliminate all account based weighting and go to solely post based weighting. The reach of your post should be only on the merits of what you posted versus who you are.
Check Current Status