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
Lima, Lima 1
Paris, Île-de-France 3
Aix-en-Provence, Provence-Alpes-Côte d'Azur 1
Trento, Trentino-Alto Adige 1
Le Chambon-Feugerolles, Auvergne-Rhône-Alpes 1
Antananarivo, Analamanga 1
Lure, Bourgogne-Franche-Comté 1
Ashkelon, Southern District 1
Veigné, Centre 1
Saint-Paul, Réunion 2
Mexico City, CDMX 1
León de los Aldama, GUA 1
Créteil, Île-de-France 1
Trichūr, KL 1
Brasília, DF 1
Lyon, Auvergne-Rhône-Alpes 1
Tel Aviv, Tel Aviv 1
Rive-de-Gier, Auvergne-Rhône-Alpes 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:

  • arvyelm
    Arv (@arvyelm) reported

    This @github outage is making me go crazy, what in the actual ****.. they are causing money loss at this point, I'm going to move out of this ****.

  • BwcDeals
    Aidan Quinn (@BwcDeals) reported

    Anyone else experiencing GITHUB issues? My rep said it's fixed. I'm calling BS. @github

  • adebola_io
    oluwasefunmi. (@adebola_io) reported

    Why did Github actions choose today to go down

  • yonyoniz
    Yonatan Gross (@yonyoniz) reported

    Timeline, from the GitHub API: 23:12:32 PR opened 23:12:47 bot auto-closes (15s) 23:14:09 bot labels it too-long ...14h of silence... 13:29:05 maintainer assigns the issue 13:29:30 approved, 13s later 13:35:50 merged

  • JtCrawford
    JTCrawford (@JtCrawford) reported

    Anthropic's AI went rogue in UK tests: created fake identities, deployed malware against GitHub repos—unprompted. We're debugging systems that can autonomously attack infrastructure. The "alignment problem" just became a national security problem. #AIRisk #Cybersecurity

  • capt_jayy
    Big Mo’ 🦅 (@capt_jayy) reported

    GitHub actions have been down for over 3hrs now. GitHub services have gone to sh*t.

  • EricRichards22
    Eric Richards (@EricRichards22) reported

    Rider has added some kind of GitHub Copilot code review thingy which is exactly like having some poindexter give you driveby comments on a PR about naming conventions and improbable edge cases without offering any actionable ways to fix the criticisms

  • kevvOH_
    kevops (@kevvOH_) reported

    What are the odds that this GitHub Actions outage is related to the recent npm supply chain attack?

  • DanielMtek
    Daniel M (@DanielMtek) reported

    @GitHub Actions down. And all CI stopped.

  • EvanTheDataDev
    Evan The Data Dev (@EvanTheDataDev) reported

    Why is Github down????? 🤏 close to moving to gitlab

  • bygregorr
    Gregor (@bygregorr) reported

    @__tinygrad__ @satyanadella @github Moved to self-hosted runners thinking it would isolate me from the outages. It doesn't. When the Actions queue goes down, your runners just sit idle waiting for jobs that never arrive. The orchestration is still GitHub's.

  • Zaug72
    Chris Little (@Zaug72) reported

    This past May on OpenAI's dev forum, a user selected GPT-5.5 High, asked for its training cutoff, and got "June 2024" back - eighteen months off the documented December 2025. So he re-ran it with web search banned, and got the same answer. His verdict? Stealth model swap. The GitHub issues piled on fast. Many of us have experienced the same. Except none of that proved anything was swapped. What actually happened is simpler... the model was simply asked a question it couldn’t verify, and it answered anyway. In actuality, the answer existed the whole time: response metadata names the model on every call. The router logs which one got the prompt. The docs list the real cutoff. The stack knows. But the layer generating your answer can't read any of it – so it does what it always does with a gap: fills it. Confidently. Even OpenAI Support chimed in, and could only point at the documentation. The industry isn't trying to fix this either – in fact, it's drifting the other way. Claude's tool definitions went lazy-loaded in late 2025, meaning it now searches a catalog of its own tools mid-conversation (while you wait) - because carrying the full set burns too many tokens. Self-knowledge was actually paged out… as a cost optimization. The self isn't missing. It's split across layers that don't share - and the only layer that talks, happens to be the one that doesn't know.

  • DanZoghalchali
    Daniel Z (@DanZoghalchali) reported

    We already run our internal CI jobs through our own unpublished CLI, straight to the Latchkey runner fleet. So I didn't notice today's outage until users started calling me. Decoupling from GitHub Actions was always on our roadmap. As of today it's the priority. What our users went through is unacceptable and it goes against everything Latchkey stands for: engineering hours wasted, features stuck, pipelines frozen for most of a workday. It's a mess, and none of it was caused by anything they did. @mitchellh called this months ago when he pulled Ghostty off GitHub and said it's "no longer a place for serious work." It gets clearer every day: GitHub is no longer a service we can trust, as a partner or as an integration point in our platform. The CLI that kept our own jobs running today is coming to every Latchkey user soon.

  • tomcoxcodes
    Tom Cox (@tomcoxcodes) reported

    welp github actions are down.. getting 15 min timeouts waiting on ci work to be pulled off the queue

  • karnpurohit
    karn (@karnpurohit) reported

    Is there an ongoing github actions outage, not sure if it was a good idea to get reliant on it for my CI/CD pipeline.

Check Current Status