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
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
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 1
Dortmund, NRW 1
Davenport, IA 1
St Helens, England 1
Nové Strašecí, Central Bohemia 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:

  • ParagRangankar
    parag.dev (@ParagRangankar) reported

    Just wired up real-world OAuth in my app ✅ Frontend kicks off `/auth/google` or `/auth/github`, Passport handles the provider flow, backend issues JWT, then redirects to `/oauth-callback` to store token + fetch user. Feels clean and production‑ready. #webdev #oauth #nextjs

  • sandmark_news
    Sandmark (@sandmark_news) reported

    2/ The shift is visible in the data: crypto code on GitHub is down 75%, while 80% of Q1 2026 VC funding flowed to AI. It's clearest in payments. AI agents need sub-cent settlement that card rails can't provide, and Crossmint's Alfonso Gómez-Jordana told Sandmark stablecoins fill that gap.

  • laboomemes
    laboo (@laboomemes) reported

    @jesselarose @Sushilk91 oh i guess you should determine what surface area they communicate with. i just have them talking on. you can ssh for a messy solution or have them communicate on assigned github issues per agent for something less fragile but messy.

  • AstroCounselKK
    AstroCounselKK 🇮🇳 (@AstroCounselKK) reported

    ⚡ GitHub Copilot's move to token-based billing is a reminder of a reality many ignored: AI was never free. It was subsidized. For years, vendors absorbed huge compute costs to gain market share. Today, some developers are discovering what happens when those costs get passed on to users. The bigger issue isn't Copilot. It's the companies that laid off experienced engineers and built workflows assuming AI would remain cheap forever. If your productivity depends on unlimited tokens, your costs are no longer predictable. The engineers who can still design, debug and write software without an LLM aren't obsolete. They just became your contingency plan. And Copilot won't be the last. Every AI provider faces the same challenge: compute is expensive, margins matter, and subsidies don't last forever. The era of "unlimited AI" was always temporary.

  • freeconlon
    Jeff Conlon (@freeconlon) reported

    I almost hired a developer to build our landing pages faster. We were bottlenecked. Every new campaign needed a page, and our design team was stretched thin. Instead, we spent two days building a system where AI designs the page, AI writes the code, and it ships through GitHub to production with conversion tracking already wired up. No designer queue. No developer handoff. No QA loop. The first page went live this week. Took about 20 minutes from concept to production URL. I keep thinking about how close I was to solving the wrong problem. The bottleneck wasn't speed. It was the number of humans in the chain. Three handoffs became zero. Every agency owner I know is trying to hire their way out of a process problem. Sometimes the better move is to remove the process entirely.

  • cnakazawa
    Christoph Nakazawa (@cnakazawa) reported

    For Codiff I unapologetically close every issue and tell people I will only consider the issue if they sponsor me on GitHub first. Has been a huge success because engineers would rather contribute a PR instead of spending $10.

  • ng_thanh8
    Thanh Nguyen (@ng_thanh8) reported

    GitHub Copilot’s shift to token-based billing is a wake-up call. Pro+ users paying $39 a month are reporting that credits disappear fast, sometimes after only a couple of hours of normal use. Some teams are even getting cut off entirely because shared token pools make individual usage hard to track. The real issue is dependency. Too many companies reorganized around subsidized AI tools and now face unpredictable costs, capped usage, and broken workflows. Users may move to Claude Code or Codex, but the economics are the same everywhere: once the subsidy ends, “cheap AI” gets expensive fast.

  • KoatStrikesBack
    Zak McKrackepidemic (@KoatStrikesBack) reported

    @pumpketo @KaviKovi The ai is hosted on your computer. There is no "server" it's connected to. It's basically a "newborn" ai. It's also open-source, which means you can download it for free on GitHub, so there's no profit being made.

  • irl_danB
    dan (@irl_danB) reported

    @max_takeoff incredible, tell Codex to create Github Issues with any feedback it has, good bad and ugly!

  • dalisoft
    Davlatjon Sh (@dalisoft) reported

    @morganlinton @FactoryAI 2. GitHub issues are like stale and never gets enough attention. Need dedicated person to fix that (@FactoryAI i could be this person)

  • david_whitney
    David Whitney (@david_whitney) reported

    @fromdevoid Copilot brand, TL;DR - GitHub Copilot good, great brand, renaming everything to Copilot? Terrible idea, huge backlash, rightfully so.

  • UBCEngPhys
    UBC Engineering Physics (@UBCEngPhys) reported

    @dmitrygr @ruider92545 @SciTechera I suggest you check out the statisitical model for puck colision restituion - available on GitHub - and then reconsider your statement. This is one out of probably a dozen modelling issues that will prevent you from running this system on your proposed hardware solution. G-day.

  • focusotter
    Focus Otter (@focusotter) reported

    This was a good example of being able to pivot based on user behavior. My original demo for @CascadiaJS was to have people login with Github on their phones and based on prs, commits, repo stars, etc, I battle partner (aka pokemon) would be created and we would all battle each other. Once I realized at a conference booth, no one wants to login, confirm mfa, and go through that flow, I switched to my drawing app. BUT the GitMon battles will happen soon!

  • LaneBrain_
    LaneBrain (@LaneBrain_) reported

    @MatthewTse_ @contember * i'm less convinced about testing OKENA after seeing some of the closed Github Issues (including plain text auth codes ect)...

  • CharlieEriksen
    Charlie Eriksen (@CharlieEriksen) reported

    @github @GitHubSecurity It's a bit unfortunate that you're now causing anybody who uses @OpenSearchProj npm packages to get flagged as having installed malware. And despite there being several issues in the GH repo from days ago that point out the mistake, it still hasn't been fixed. 🫤

Check Current Status