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
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
West Lake Sammamish, WA 2
Parkersburg, WV 1
Perpignan, Occitanie 1
Piura, Piura 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:

  • Gezi_lzq
    Gezi (@Gezi_lzq) reported

    I noticed that issues created by github-actions can be queried via gh cli, but cannot be seen on the page. It should be a GitHub BUG... @githubstatus @github

  • Gezi_lzq
    Gezi (@Gezi_lzq) reported

    @morizotter Same issue here, the issues I lost were also created by GitHub Actions

  • Frooxius
    Frooxius @ MFF - frooxius.bsky.social (@Frooxius) reported

    @hideki Would you be willing to make GitHub issues with a report on those issues so we can address them?

  • adelbucetta
    Adel Bucetta (@adelbucetta) reported

    @github the problem is, most people don't actually want their project to be accessible.

  • dr_kabanov
    Ilya Kabanov (@dr_kabanov) reported

    What happened last week worth your attention? Verizon's 2026 DBIR puts vulnerability exploitation as the #1 breach vector at 31%, while full CISA KEV remediation fell to 26% from 38% last year. Separately, 8 GitHub repos with 172K combined stars resell unauthorized Claude, GPT, and Gemini access, and almost half of calls hit a different model than advertised while every prompt is logged on the operator's server. And an IEEE S&P 2026 paper from Columbia and USC showed an official deep-learning compiler silently flips predictions in 31 of the top 100 HuggingFace image classifiers, no attacker involved. Plus LLM monitors that lose 2-30x detection rate as agent transcripts grow, and LLM IR drafts that flip recommendations on identical breach data. Happy Tuesday!

  • quentinkasseh
    Quentin Kasseh (@quentinkasseh) reported

    I've started to get suspicious of the phrase "agent-ready". GBrain hit GitHub a few weeks ago, YC put company-brain shape on its Summer Request for Startups, and I'm getting the same itch about that phrase too. Both sound as if the important milestone is the system finally talking to tools, finally remembering things. The agent can call APIs, move between apps, fire off actions without a person hand-holding it the whole way. The brain can recall every meeting, every account, every thread. That does matter. But it also creates a slightly misleading picture, because it makes the infrastructure milestone sound like the trust milestone. The trouble usually shows up earlier than people expect. Not in the action itself, and not in the memory either, but in what the action and the memory inherited. Say a duplicate cluster gets treated as one account when it really contains several distinct business objects. Or a regional entity gets treated as the whole company. Framed that way, "context" starts to sound like too soft a word for what's going on. What's actually sitting underneath is a set of design decisions about boundaries, permissions, rollups, history, and identity. The agent doesn't invent those. The brain doesn't either. Both inherit them. So when people treat the whole thing as a prompting problem, or a memory problem, they're often looking in the wrong place. The model can only work with the object it was handed. If that object arrives in a distorted shape, clean reasoning just produces a cleaner mistake. A brain wired to the same object remembers the mistake longer. Memory isn't the layer. Meaning is.

  • mureithi_me
    Njuguna Mureithi (@mureithi_me) reported

    The problem here is marketing. I bet such platforms exist on Github and Gitlab. In marketing you will be competing with Uber which is willing to take a $5bn loss per year.

  • one_dheeraj
    Dheeraj (@one_dheeraj) reported

    $100 in AI tokens and 2 hours later... my @github self-hosted runner still isn't doing anything. No error messages. Just pure, silent failure. I am losing my mind. 🙃📉 #TechStruggles #DeveloperLife

  • sanxiaozhizi
    Kevin Deng 🦋 @sxzz.dev (@sanxiaozhizi) reported

    The npm registry has no proper issue tracker. Feedback gets dumped into a GitHub Discussions space, mixed with everything else, rarely getting an official reply. npm is critical infra for millions of devs. It deserves a dedicated, staffed, public tracker. This isn't optional.

  • SiliconForested
    Chris Kearney (@SiliconForested) reported

    I started ChonkBlocker as a free-time puzzle game back in Dec 2018. The old demo.gif I’m attaching was from the scrappy “can I even make this work?” era. Fast-forward to today: 731 commits, 168k LOC, 112 PRs, 517 GitHub issues, and roughly 240 active commit-session hours later, it’s becoming a real shipping game. Linux, macOS, Windows. Steam + Mac App Store paths. Online head-to-head multiplayer, matchmaking, Steam-friendly stats, broad SDL2/Steam Deck/controller support, native installers, CI release builds, and a lot of late-night “why is this one frame wrong?” energy. It started as a toy. Somehow it became a game.

  • g_giovanii
    Gian Giovani (@g_giovanii) reported

    @github any issue with action dispatching?

  • Samhanknr
    Zengineering (@Samhanknr) reported

    @ai_ops_lead Also GitHub slack etc have predictable per seat pricing and they are quite cheap all things considered. So the ROI was never top of mind. AI is expensive that’s the problem

  • i9carnation
    Snorlax ⸙ (@i9carnation) reported

    **** I can't login into github.

  • Quan2m2
    Allison M. (@Quan2m2) reported

    Ofcourse github actions are having a ******* outage right when I am testing a new autonomous coding agent that I didn't think to add a flag to for ignoring github actions. come on @github how can you be so unreliable

  • hi_dep_g
    ひで🎖️🎖️hidep (@hi_dep_g) reported

    @Bob_Kowalsky Thanks! It looks like GitHub Pages was having some issues on their side. It seems to be working fine now.

Check Current Status