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
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
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:

  • crystalwizard
    Crystalwizard (@crystalwizard) reported

    how about you now fix the false positive triggers - i put in an issue about this on github yesterday, and discovered there were already a number of other identical issues - from other people, that had been opened for a while now and that are being 100% ignored

  • KaluraDeepesh
    Deepesh Kalura (@KaluraDeepesh) reported

    Filed as GitHub issues: #336: Phone operators need stable unique IDs (not just phone number) #337: Auto-heal sticky assignments when a node dies Future imp task

  • ooluwatobig
    Oluwatobi O (@ooluwatobig) reported

    More trouble for GitHub as Cursor has launched Origin, a product which is essentially GitHub for AI agents

  • SolutionsCay
    Jose (@SolutionsCay) reported

    @petergyang /goal make me app does not work for me 😰 but /goal complete GitHub issues #90, #91, #92 works very well

  • momo5502
    Maurice Heumann (@momo5502) reported

    @disarray00 If you have concrete recommendations, I would love to hear them, either as GitHub issue, maybe even a PR. But also as a comment here, I'd appreciate it. So when speaking about redundancy, what precisely?

  • Artur_roses
    Arti | AI Builder (@Artur_roses) reported

    Claude Code can take a GitHub issue, write the code, run tests, and open a reviewed PR — no human keystrokes required. The dev loop isn't getting faster. It's being removed.

  • metalagman_dev
    Alexey Samoylov (@metalagman_dev) reported

    @geminicli Antigravity CLI is a trash, closed source, full of bugs. They don't even read issues on the github.

  • namespacelabs
    Namespace (@namespacelabs) reported

    Behind every API, webhook, event pipeline, there are people trying to keep things running. And keeping these things running is not an easy task. At Namespace, we try to work with those people. Earlier this week, Gihub events were dropping fields we depend on and customer jobs were stalling. We reached out to work on the problem together and had a fix in under an hour. The @github team was ready to help. We just had to ask.

  • meranaamkhann
    Asad (@meranaamkhann) reported

    Let's see what people are building these days!! Drop your project link or github Links down here

  • programmers_app
    Programmers.App (@programmers_app) reported

    @Lovable @claudeai One very big fix is the Claude Github connection which fails many times, now #Lovable MCP solves that, great job! 🚀🚀🚀

  • aisama_code
    aisama.code (@aisama_code) reported

    AI Research gets stronger when it records contradictions *most research workflows collect supporting evidence - that is the weak version for serious research I want a contradiction log: - claim - source - date - who says it - what evidence supports it - what evidence conflicts with it - what is still unknown - confidence - next check example: > claim: this product has strong developer adoption > support: GitHub activity, docs updates, X discussion, integrations > conflict: low issue activity, small Discord, few production case studies, mostly founder-driven content now the memo is different, It says: "visible attention, but adoption evidence is still weak" the useful workflow: research question -> source list -> claim extraction -> contradiction log -> memo ! сode is good at assembling text ! AI is good at comparing disparate text ! human is good at determining which contradictions are significant *without a contradiction log, AI research becomes a confident summary of whatever it found first

  • RedZenCloudLLC
    Red Zen Cloud LLC (@RedZenCloudLLC) reported

    Cursor's Origin platform and Claude's GitHub imports both solve the same problem: developers automating code work need their tools to understand context, not just generate tokens. The winner isn't the smartest model—it's whoever reduces handoffs between agent and human.

  • 0xZoZoZo
    Zo (hiring) 🐦‍⬛ (@0xZoZoZo) reported

    I was telling a friend that @github needs to be replaced post agents and he asked me to explain why. I started stumbling, and doubting. Perhaps it's fine? Sitting down at my desk, let me try to explain why, and see if it make sense. Agents operate best when they have good context, which has made a lot of devs converge into large monorepos that combine all systems into a single location. This improves agents, but our GitHub actions become messy; like now we need to create these complex workflows to decide which action should run when, and GitHub's setup was not really meant for it. Another issue is the overall dev loop: an agent writes the code locally, you push out a branch, @cursor_ai reviews, then you copy paste the notes into the local agent, to fix and push up again. This is slow and cumbersome. You can hack your way by creating supervisor agents that orchestrates this dance, but it's annoying. Perhaps, there is some magical repository, that combines code, cloud agents, and deployment. You prompt, and this magical space will run through the entire process until you get some thumbs up back, and you're good to go. It can also combine all your backend data, product analytics, customer feedback, and perhaps start giving you product guidance, so you can just feed prepared prompts to this system. This seems magical.

  • realTads
    Tad 𝛑 (@realTads) reported

    @robertpreoteasa Sir, the ION project is still on the right track and successful, I don't see any updates on github and ION's products are almost not working or working together, we need the answer of the project leaders, hope to receive a response from you soon, thank you

  • petrusenko_max
    Max Petrusenko (@petrusenko_max) reported

    A GitHub repo called Microsoft Activation Scripts has 178,783 stars and has run for six years without Microsoft taking it down. It activates Windows 7, 8, 10, and 11 plus Office 2010–2024 and related products for free, using four methods, including one for permanent Windows activation. Meanwhile, Microsoft licenses for these start at $139 and go up yearly for 365 bundles. The repo costs zero, requires one command, and remains active with recent commits under GPL-3.0. Do not install it. via @heynavtoor

Check Current Status