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
West Lake Sammamish, WA 3
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:

  • TomGiant1
    TomGiant (@TomGiant1) reported

    GitHub's CISO yesterday: investigating unauthorized access to GitHub-owned repositories. Notification only if impact is discovered. Two rules I bake into every agent I run: 1. Permission per action, not per session. A read action and a write action get separate gates. "Do research" is one ask. "Make it live" is a different one. Even with everything else open. 2. Reads stay alive when writes go down. When the write path breaks, the read path keeps reporting truth. No silent retries that mask the failure. Headline is GitHub. The mechanism applies to anyone running automation that touches real systems.

  • jsolisu
    jsolisu (@jsolisu) reported

    Bye Bye @github What terrible service!

  • deggen
    Deggen (@deggen) reported

    @Neggia5 @mohrt Sounds bad. Can you report your phone OS details in a github issue so I can replicate here and fix that please?

  • yayriri
    yeri (@yayriri) reported

    Finding AI agents buried in GitHub and giving them a face. Repo 1 done. Two versions shipped. V1: clone the repo, install Python, get API keys, run localhost. Full financial data. Real accuracy. For devs. V2: open Claude, drag in the file, pick a stock. No install. Web search powered. For everyone. Same 18 AI investors. Same debate. Different door. One repo taught me more about this problem than all the research combined: 1/ The agent isn't the bottleneck. The door is. 2/ 51K people starred ai-hedge-fund. Most of them never ran it. Not because it's bad — because poetry install is a wall. 3/ V2 isn't better than V1. It's just... reachable. That's what I'm building. Not better agents. Better doors :)

  • camtrew
    Cam Trew (@camtrew) reported

    GitHub just got hacked... (And somehow I'm not surprised) With AI-written code and AI hacking tools everywhere, this is only going to get more common. The latest victim is GitHub, the platform where most of the world's code is stored. This week, a hacker group stole nearly 4,000 of GitHub's own private projects and listed them for sale online. And they did all of this without hacking a single server... Here's what happened: 1. How they got in VS Code is the world's most popular code editor. Developers install small add-ons called extensions to make it work better. Hackers poisoned one of those extensions. A GitHub employee installed it, and the attackers got access to everything. 2. What was stolen They walked out with the source code for GitHub's own internal tools, including Copilot. These are tools used by 100 million developers every day. GitHub says no customer code was taken, but their own was. 3. They're selling it for almost nothing Everything was listed for $50,000. Their message: "If nobody buys, we leak it for free." GitHub hasn't said whether anyone paid. In fact, they haven't said much at all... If this doesn't make you think twice about what you install, it should. The tools are getting smarter. The attacks are too. Do you trust the software you use every day?

  • voixoo
    Voixoo (@voixoo) reported

    @TristanRobert7 @koboateng And they also want to pass a bill that will discourage people from solving this problem with AI. Imagine needing a certificate to push code to GitHub

  • PsiKrotic
    Givemhell (@PsiKrotic) reported

    Inside the library: 5 code-quality (review, security, perf, a11y, dead-code) 3 testing (gen, coverage plan, flake detector) 4 design (refactor, API, schema, type-tightener) 2 bug fix 2 migrations 4 docs/*** 1 logging 2 i18n/config 2 infra (Dockerfile, GitHub Actions)

  • thecyberdevhq
    CyberDevHq (0xSEC) (@thecyberdevhq) reported

    @segoslavia @skyletmoringa That's not true. Not even the entire video. He actually showed a *** feature that actually enables one to create their own repo on an SSH server, whether local on remote. Making GitHub not necessarily needful unless one wants to make some repo public, which you can just mirror if needed. Nothing related to any hacks, not that of GitHub

  • upstatefederlst
    Upstate Federalist (@upstatefederlst) reported

    "Why is Github constantly down?"

  • 0xbobaaa
    0xbobaaa (@0xbobaaa) reported

    an Anthropic engineer just demoed their agent closing a real bug in a stranger's repo -> zero human commands Boris Cherny, creator of Claude Code live at Code with Claude 2026. only 5 min. free agent opens Bun -> finds a github issue -> reproduces the bug -> writes fix + test -> opens PR they call it Routines. set a cron or a github event wake up to a PR waiting for review 5 min. better than any reel you'll watch today

  • NyllRe
    Nyll - Ali Sokkar (@NyllRe) reported

    @alvarosabu I personally still search for videos to learn about new tech even things like Hermes agent, issue is most tutorials now are tailored for people with almost no knowledge about the field and now I have to skip the part where they explain what "Github" is

  • Abubakar_2005
    AYS ⌘ (@Abubakar_2005) reported

    5/ The DAST implementation was the most interesting problem. DAST requires Docker to run. My laptop can't run Docker locally. Solution: move DAST execution into GitHub Actions. When code is pushed, the CI/CD pipeline spins up the container and runs the scan there.

  • piobid
    intergalactic spice trader (@piobid) reported

    How tf is it, that in the year 2026, you need to close ALL open VSCode windows and reopen them (and don't make the mistake of reopening from "open recent") to update PATH variables. And this is an open issue on the vscode GitHub since EIGHT YEARS.

  • dyazincahya
    Kang Cahya (Tech Dev) (@dyazincahya) reported

    Here's the gist: GitHub is changing the format of their App Installation Tokens to be stateless (carrying their own data without pinging the main server constantly). The side effect? The token size is inflating massively. What used to be short will now hit ~520 characters! 🤯

  • OmarFaruk0x01
    Omar Faruk ✨ (@OmarFaruk0x01) reported

    Hey @prelineUI, Maybe you guys are not too interested in Preline security, right? I tried to reach out via email and DM about a security issue in Preline, but you are not responding. The support team told me to create a public issue on GitHub. Should I do that?

Check Current Status