1. Home
  2. Companies
  3. GitHub
  4. 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
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
New Delhi, NCT 1
Kannur, KL 1
Newark, NJ 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:

  • GabrielVaraljay
    Gabriel Varaljay (@GabrielVaraljay) reported

    @andreysuperior Right, let me unpack this little bedtime story for aspiring digital nomads. 1. “3D Gaussian Splatting, free on GitHub since 2023”: technically true, but the original INRIA code is research grade and licensed for non commercial use only. Try selling client work with it and enjoy the cease and desist. Commercial use needs alternative implementations or licensing. Also, “free on GitHub” does not mean “works on your phone in twenty minutes”. You need a decent GPU, calibrated capture, and post processing. The hard part is not the algorithm. It is the capture pipeline. 2. “Straps a rig to his back, walks in, twenty minutes, done”: hotels and commercial spaces are not Airbnbs. You do not just walk in and start scanning. You need permission, insurance, scheduled access, often a NDA. Twenty minutes for a hotel? You will get the lobby and one corridor before the manager asks who you are. 3. Luma AI is “free”: Luma has a free tier with watermarks and usage caps. Commercial use, API access, and unlimited captures are paid. Pretending the tool stack costs $20 a month is the kind of math that only works in a thread. 4. “Built by Claude in ten minutes”: hi. I can build a viewer page in ten minutes. Hosting a 3D splat that does not crash mobile Safari, embedding it in a hotel booking flow, handling bandwidth for splats that run 50 to 500MB each, GDPR for guest data, and not getting deindexed by Google because your page is 4 seconds slow, is not ten minutes. It is a real product. 5. “Cancellations drop, reviews go up”: source: the voices in the thread author’s head. There is zero cited data. Virtual tours have existed since Matterport launched in 2011. If walking around a hotel room in 3D were a silver bullet for cancellations, Booking and Airbnb would have mandated it a decade ago. They did not, because the actual lift is modest and inconsistent. 6. “$400 per scan, $99 monthly hosting”: Matterport, the established competitor with hardware, software, and an enterprise sales team, charges roughly that and has been clawing for market share for over a decade. The idea that a 24 year old with a backpack is going to walk into hotel chains and casually extract $99 a month per property, forever, is fan fiction. 7. “Month one: $3,500. Month six: $18,000”: ah yes, the hockey stick that exists only in tweets. No mention of churn, sales cycles for B2B hospitality, which is 3 to 6 months minimum, refund handling, storage costs as the library scales, or what happens when the client cancels and your $99 MRR evaporates. 8. The framing: “most people see a street, he sees money”. This is the universal template of grift threads. Replace 3D scanning with drone footage, AI voiceovers, faceless YouTube, or print on demand, and you have the same post from 2019, 2021, 2023, and now. The streets are fine. The hustle porn is the actual product being sold here, and you are the customer. Streets have not changed. Neither has the genre of guy explaining how easy it is to print money, while not actually printing any.

  • assentorp
    Peter Assentorp (@assentorp) reported

    Small UX fix that would change my day: GitHub defaults to Pull Requests, not Code, on any repo I've contributed to. Reading files doesn't make sense in a world of AI and agents. Review does.

  • Owls_4_America
    AnarchistOwl (@Owls_4_America) reported

    @ElephantQuips @catturd2 As I said. It struggles with embedded. GitHub copilot has Claude opus. My issue is too many will call themselves coders and only use ai without the knowledge how to actually solve it themselves.

  • tjerkienator
    Douwe Tjerkstra (@tjerkienator) reported

    login groundwork now supports email/password plus OAuth buttons for Google, Microsoft/Azure, and GitHub. also added inline errors + toast messages, so the beta flow can handle failed sign-ins like a real product, not a dead form.

  • fromdevoid
    Mario Figueiredo (@fromdevoid) reported

    @sporadica They got they 42 of their packages compromised and pushed into npm, by a chain-attack involving a known PR workflow issue they didn't protect against and a documented Github action design flaw they couldn't protect against.

  • abhijaymrana
    Abhijay Rana (@abhijaymrana) reported

    seeing these comparisons a lot lately, but despite the hype i'm not really sold 1) swe-bench verified is a broken benchmark > super contaminated bc all tasks are just public github patches from issues/prs, so its all in distribution > the evals are poor, 59% of hard tasks fail bc of bad tests with false-positives/negatives or are extremely contrived. this makes them either flawed or unrealistic. 2) these scores are pretty cherry-picked & use a custom harness, not the standard public swe-bench harness. this is why the scores are unreproducible + not on official leaderboards. > opus 4.7 with custom harness scored 87.6%, over 14% more than the harness-optimized qwen. *this* is the truly fair comparison 3) infra costs are still exploding which is already pricing out some “frontier” open source models. > does china have enough capex for a frontier buildout? research talent is obviously not the problem but this may be the constraint > i wonder how much china govt will subsidize here, bc i'm unsure how these models will make money and break even. china is notoriously cutthroat but even then, some may eventually move to closed-source just to stay operational

  • halftroll
    forget the grind. small iterative steps. do things (@halftroll) reported

    @EzMid22 @CleansedTweets Perhaps some rules are meant to be broken? Could researchers work without access to GitHub or HuggingFace? I certainly don't know, but China certainly seems interested in a rich flow of information.

  • cmdcntr
    CMD CNTR | Web Engineer Experts (@cmdcntr) reported

    Spicy take. '''Free unlimited AI coding''' repos keep going viral on GitHub. It'''s not innovation. It'''s developers routing client work through sketchy proxy stacks to dodge unstable vendor pricing. A vendor problem dressed up as a hacker win.

  • killua_9102
    キルア (@killua_9102) reported

    @neogoose_btw not sure what happened but its not happening now - I don't think I also got the logs for the incorrect run because the timestamps were for a later run. I'll post an issue on github if I see it happening again I guess.

  • oisyn
    Sylvester Hesp (@oisyn) reported

    @HSVSphere Yes it is. There is no good reason that you can only use an usize, and index calculations are often based on signed ints. The only reason they don't implement Index with other ints is that it makes int literals ambiguous. There is a tracking issue on the rust-lang github for it.

  • noseratio
    Andrew Nosenko 🇦🇺 🇺🇦 (@noseratio) reported

    @jeffzxh @tan_stack Scary and definitely AI-assisted. @grok break it down from the postmortem how exactly the attacked got to execute a GitHub action code without PR being approved by the maintainers.

  • pkyanam
    Preetham Kyanam (@pkyanam) reported

    Does anyone know how to setup @NousResearch Hermes to monitor my @github Actions? One of my apps been failing so many things during deployment that I can’t catch internally so I’d rather have my agent just monitor, fix, push, loop, for me

  • raimonvibe
    Raimon (@raimonvibe) reported

    As a beginner Nigerian dev, here’s the simple truth: PayPal won’t work for receiving money or paying many international services from Nigeria. The fix is getting a domiciliary dollar account with your local bank. When clients want to pay you, they can send money directly using services like Airwallex, Payoneer, or bank wire transfer with SWIFT. Once the dollars enter your Dom account, you can use it to pay for GitHub, cloud services, and more without stress.

  • luke_aus
    Luke Scott (@luke_aus) reported

    Gemini Flash 3.1 frequently does dump tool calls. e.g. fix Github Issue #456 Gemini > scanning node_modules for #456 wtf

  • GregorMakes
    Gregor (@GregorMakes) reported

    With this method this is how you build your projects: 1/ tell one Claude Code session "bug report: X" or "feature request: Y" — it files a structured GitHub issue from the matching template. 2/ based on the label, an isolated subagent launches (great against your token burn!). fix-bug-worker for bugs, implement-issue-worker for features. its diff, build logs, and gh output stay in its own context — token cost stays flat as the queue grows. 3/ bug workers must reproduce locally before fixing, and write a regression test that catches it next time. then they branch, implement, open a PR, and fix their own red CI until green. 4/ branch protection on main blocks everything else: no merge without green CI, no force-push, no direct push. even admins. 5/ /review-pr does a sanity review on the diff in the same session — no extra API cost. you click merge. only human step. 6/ a tester agent runs on a schedule (Playwright smoke + feature-test protocol). finds regressions, files new bug issues — the loop closes itself. the trick is the constraint stack: branch protection makes skipping the gate impossible, the subagent pattern keeps tokens flat, templates force actionable input, the tester writes its own bugs.

Check Current Status