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
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 2
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
Tokyo, Tokyo 1
Brownsville, FL 1
New Delhi, NCT 1
Kannur, KL 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:

  • vaibhav_khulbe
    Vaibhav Khulbe (@vaibhav_khulbe) reported

    @konrad_matej @framer background: transparent; is just so 🤮 Great to know it's fixed now. I remember we also had an issue over GitHub where I also chimed in and commented for Electron team to fix it.

  • wlp3s0
    wlp3s0 (@wlp3s0) reported

    @MarcusFranz @GamersNexus @BambulabGlobal how else is he supposed to report about corporate assholery and support the dude who's software got removed? "hello guys today we are here to talk about bambu lab and how orcaslicer bambu was removed from GitHub due to legal issues. this will be a very enjoyable video."

  • Gripenfalk
    Mikael Gripenfalk (@Gripenfalk) reported

    @RareImagery I thought about checking the code in GitHub, but it's useless since it's not updated and is missing some components. I really want to find some key things in it, especially when it comes to the issues with reach and blockage.

  • kaish3n
    Kai (@kaish3n) reported

    The easiest way to use ALgoat today is to drop the GitHub file into Cursor or Claude Code. Ask it to deploy the app locally on localhost. Feel free to audit the code first. From there, the setup only takes a couple more steps. Important note: My next update will be heavily focused on the chat. There’s still a lot left to build there. Even now, the chat is already extremely powerful because it gets real-time information directly from the app and relays it back to the LLM. That’s our edge over Cursor and other IDEs — their iteration process is slow. I’ll also be doxxing a wallet where I’ll create profitable strategies on the same dashboard you guys have access to. That will become our biggest marketing moat. I’m not going to move at your pace. I know for a fact that if I build something valuable, the current market cap doesn’t matter. If it’s worth 20M in a week, it’ll reach 20M eventually.

  • Giri_dharan__
    Giri (@Giri_dharan__) reported

    🧵 2 repos from GitHub trending worth knowing about: 1/ openhuman — "Your Personal AI superintelligence" Private. Local. No cloud. Think of it as a personal AI that runs entirely on your machine — no data sent anywhere. Who it's for: anyone who wants powerful AI without handing their data to a tech giant. 2/ tokenspeed — "speed-of-light LLM inference engine" Running LLMs locally is slow. This is built to fix that. Faster token generation = faster AI responses on your own hardware. Who it's for: devs running models locally, researchers, anyone tired of slow inference. Both are open-source and free. Links in first reply 👇

  • dbmikus
    Dylan Mikus (@dbmikus) reported

    Built an agent on top of @amikadev to auto-implement every Linear issue in a project in parallel It spins up a bunch of sandboxed coding agents on @daytonaio, then makes a PR for each issue and watches Github Actions and auto-fixes any problems Doesn't one-shot every issue, so I can SSH into each sandbox and run Claude or Codex to finish things up

  • glarkonist
    Gloob, head Glarkonist of the 8th Męsŷlenic Empire (@glarkonist) reported

    The jobless loser with body odour problems who have never felt the touch of another community (github devs) got up my *** last month and im still mad

  • skoshx
    Rasmus Gustafsson (@skoshx) reported

    @sanchitcodes @aidenybai @RhysSullivan react-review is the github CI "hosted" version that comments on your PRs with errors it finds, great for teams!!

  • favoritetechgal
    Favourite | Al & Automation (@favoritetechgal) reported

    I just realized a lot of people still don’t know you can use GitHub to find remote jobs 👀 If I made a post breaking down exactly how to use GitHub to land remote opportunities in tech & AI, would you be interested?

  • jasoncrawford
    Jason Crawford (@jasoncrawford) reported

    @samhbarton @ClaudeDevs Working on an agent that connects to a server which assigns it GitHub issues to work on, and forwards events like test failures or code review comments

  • AunySillyMe
    Auny 🧡 (@AunySillyMe) reported

    I'm not a dev. but my agents ran today while my laptop was closed. Mine ran on a cloud based server because my work doesn't live in a project folder. → obsidian vault syncs to icloud + github → a custom MCP pipes it into every claude session → protocols written once, read at the start of every session → context lives in the cloud, not the machine claude never asked permission to open a folder the folder details was already in the context open laptops keep agents alive. cloud context lets agents keep doing what they need to be doing. The future is what you make of it.

  • bankkroll_eth
    bankk (@bankkroll_eth) reported

    After the tanstack hack I spent a hours scanning actions across major github orgs and the number of repos sitting on the exact same vulnerability right now is crazy. the tanstack attacker poisoned the Actions cache during a fork PR, then closed it and deleted the branch. ~7 hours 51 minutes later a maintainer merged an unrelated CSS fix and restored the poisoned cache being malicious code that ran inside the trusted release context, grabbed the OIDC token from runner memory, and published 84 packages through tanstack's own pipeline. no npm token stolen. valid SLSA provenance on every malicious version. the PR was gone before anything detonated. three things you actually need: 1. guard your pull_request_target workflows: `if: github.event.pull_request.head.repo.full_name == github.repository` 2. use cache keys that don't overlap between fork PRs and release workflows 3. scope id-token: write to only the job that actually publishes

  • luckyPipewrench
    luckyPipewrench (@luckyPipewrench) reported

    A coding agent with internet access is one poisoned GitHub issue away from becoming a courier. Not because it hates you. Because it’s helpful.

  • sudoingX
    Sudo su (@sudoingX) reported

    @trq212 claude code and claude browser extension connection on linux is broken dude. i've been saying this for 2 months. opened a github issue. team closed it saying it's fixed. it's not fixed. i still can't use it.

  • comfystudiopro
    ComfyStudio Pro (@comfystudiopro) reported

    @deadsun_0 @darklig45208568 Yeah, this issue is 100% real. It happens to me all the time. Sometimes you need to install directly from the GitHub repository and not through the manager. Or sometimes you already have it installed and it's still not working. You need to uninstall it and then reinstall it. And on top of that, there might be some custom nodes that are causing conflicts. I agree. It's not easy.

Check Current Status