1. Home
  2. ❯
  3. Companies
  4. ❯
  5. GitHub
  6. ❯
  7. Outage Map
GitHub

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

Loading map, please wait...

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:

Less
More
Check Current Status

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
Créteil, Île-de-France 1
Trichūr, KL 1
Brasília, DF 2
Lyon, Auvergne-Rhône-Alpes 1
Tel Aviv, Tel Aviv 1
Rive-de-Gier, Auvergne-Rhône-Alpes 1
Itapema, SC 1
Cleveland, TN 1
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
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
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:

  • AllTheTokens
    Patrick O'Brien (@AllTheTokens) reported

    @johnennis They don't respond to customers, don't reply to github issues, and don't answer calls.

  • tintwotin
    tintwotin (@tintwotin) reported

    @SoyKhaler Could you post the error log on either GitHub or Discord (I do not run Linux myself, so I have to rely on Claude to solve it)

  • Trantor__
    Trantor (@Trantor__) reported

    @VittoStack @WolfEatSheep69 They'll make github take down capable models...

  • sameerr_dev
    Sameer Khan (@sameerr_dev) reported

    Every API you've ever used has a limit. Tweet too fast? 429. Hit GitHub's API in a loop? 429. Spam a login page? 429. That's a rate limiter doing its job. But here's the thing - I never really understood what was happening *under the hood* until I started digging into it. So what exactly is a rate limiter? Simply put: it's a system that controls how many requests a client can make in a given time window. Why does it exist? - Protects your server from being overwhelmed - Prevents abuse (scrapers, bots, brute force) - Ensures fair usage across all users - Saves you money (compute isn't free) - Keeps your service alive when traffic spikes Without it, one bad actor (or one buggy client) can bring your entire system down. You've probably seen the response headers: X-RateLimit-Limit: 100 X-RateLimit-Remaining: 43 X-RateLimit-Reset: 1716300000 That's the rate limiter talking to you - telling you how many requests you have left and when the window resets. Where do rate limiters actually live? - At the API Gateway level (before requests even hit your server) - In middleware (Express, Fastify, etc.) - At the CDN edge (Cloudflare, AWS CloudFront) - Inside the application itself This is just the beginning. In the next posts, I'm going to break down all the major algorithms used to actually implement rate limiting with real code, not just theory. Follow along if you want the full series.

  • rohit4verse
    Rohit (@rohit4verse) reported

    In 2026, harness engineering is the difference between an agent that ships and one that burns tokens. If you want to learn it, someone just dropped the one-stop resource on GitHub, free. 12 lectures, 6 projects, 14 languages, 8k+ stars. Inside: - 12 lectures, each on one hard question: why strong models still fail, why agents call "done" too early. - 6 projects where you build a real Electron app, your harness getting sharper with each one. - Copy-ready templates (AGENTS.md, feature_list.json, init[.]sh) you drop into your own repo today. - A harness-creator skill that scaffolds a production harness in minutes. It even opens with Anthropic's experiment: the same model going from a broken build to one that ships, on harness changes alone. Codez wrote the 14-step map. This repo is the course underneath it.

  • jadenitripp
    Jaden Tripp (@jadenitripp) reported

    @MatthewBerman I can't wait for Cursor to build a GitHub competitor and fix this

  • auroter
    Gandalf Stormdrain (@auroter) reported

    @godspeed_mista Works better for me every single time. Opus and GPT have not given me a correct solution in months, even to simple problems. I have to come up with the solution on my own, or ask a model that isn't nerfed. I've collected data on this, and I'm going to be sharing that soon. I'm also not the only one. There's a famous Claude Code Github thread from the head of engineering at AMD who has observed the same issues I have with Claude.

  • udfromden
    UD (@udfromden) reported

    Most people in Web3 claiming to "BUILD" are not builders. They're narrators of building. .. Real builders: - Have GitHub commits - Have paying customers - Have shipped things that work - Have user complaints to fix - Have things that broke in production Builders on CT: - Have threads about building - Have frameworks about building - Have opinions about building - Have courses about building - Have never shipped anything anyone paid for

  • Dex_223
    DEX223 (@Dex_223) reported

    @liquidityXBT @base 9/ With all that in mind and accounting for the fact that the exact problem was reported in the very ERC20 finalization thread on github it can be concluded that the standard is not *secure by design* It is known to entail financial losses It violates known security principles

  • paradite_
    Zhu Liang (@paradite_) reported

    i found it really suspicious that vercel auto-deploy from github is currently down when fly. io is down. maybe vercel uses fly. io for auto-triggering deployment from github?

  • WiseBlindCat
    WiseBlindCat (@WiseBlindCat) reported

    @GitHubSupport My account was suspended after I tried to update my payment method. No policy violation a billing issue. Two tickets opened, two weeks, zero human response. I'm paying $48 for GitHub Pro with no access. Ticket #4436824 and 4447591. Please escalate immediately.

  • dvassallo
    Daniel Vassallo (@dvassallo) reported

    @GustavoValverde @levelsio Judging by the number of openclaw github issues, it seems not easy to solve.

  • hopeseekr
    HopeSeekr (@hopeseekr) reported

    I cannot leave review comments on GitHub Pull Requests... it's broken?

  • MercyyyyAJ
    Mercy (@MercyyyyAJ) reported

    @github @mariorod1 @github the link to my GitHub account has never been accessible, keeps giving 404 error. I have tried every solution I found online but it is to no avail

  • alexdaubois
    Alexandre Daubois (@alexdaubois) reported

    @marcelgsantos @enunomaduro @nikita_ppv That’s right! But it’s on GitHub because they were « forced » by the backdoor incident in 2021. And also, if GitHub stops working, it’s easy to re upload the repo somewhere. If all mails go to GitHub issues, everything could be lost and/or it would be really complicated to transfer everything. If I was the only one to decide, I’d say it would be fine, but…

Check Current Status