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
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:
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 |
|---|---|
| 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 |
| 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 |
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:
-
Wyatt Walls (@lefthanddraft) reported@SairenNior I will put the code on GitHub when I am happy with the basic behaviors (e.g. can reliably walk up to someone and talk). I keep thinking 2-3 weeks but then I find new things to fix But in terms of running them in a public: haven't thought too much about that. Might do that occasionally at a similar time for a few hours per week.
-
Traceback (@Tracebackqa) reportedManual release checks are fine until the product moves faster than the checklist. Traceback is the QA layer for modern software teams. - Keep the checklist, but move it into the pull request: Traceback runs browser verification on every PR before merge. - AI controls the browser like a person would, so login, checkout, settings, and other real flows get exercised end to end. - Self-healing tests keep working as the UI changes; when a step fails, it becomes trackable work in GitHub, Linear, and Slack. - Plug it into Vercel, Docker, AWS, Node.js, React, Next.js, Vue — with coverage for web, mobile, web3, and design. Verify every product change before it ships.
-
Unstoppable (@CsWiz1) reportedHermes is the best tool on the planet! @NousResearch Erm, not so much. I have been testing Hermes( +Obsidian+Guthub+Telegram+@grok ) for about 5 days now with some highly tech analysis and code-gen for simulation. 1 day was mind-blowingly good. The last 4? In a word? A R G H ! ! ! 1st discovery was Hermes cannot share info between sessions without some contorted work-arounds -- read a json of another session into present session. Well, OK, frustrating but.... 2nd? Obsidian integration is clunky. Hermes doesn't use anywhere near the full possibilities, forcing me to go into Obsidian to do things Hermes ought to be able to do. I told Hermes to commit everything. It said it didn't do ***. I told it *** was in Obsidian. It said I cannot tell Obsidian to do *** -- "run these commands in a bash terminal." Um, Hermes, you are running in the Windows app. "Oh, run these commands in Powershell." Powershell -- "say what? I don't know that." Obsidian committed its stuff sans issues, which included the Hermes session with code in an Obsidian resource folder. 3rd? My Grok sessions kept expiring. Hermes -- "you're using OAuth token. You should use a permanent API token. Here's how." OK, followed, seems to work. No longer have to restart Hermes every couple hours or so. 4th? Suddenly Hermes couldn't write a clean Python file. Every attempt ended with a trailing (" ) -- double-quote plus space. Hermes WAS doing it right the first day. Not days 2, 3, or 4. Oh, Hermes switched to use patch tool. Didn't work either. Hermes, tell me how we fix this! Hermes -- "well those tools are in Hermes core code, but you can file a bug on Github." OK Hermes, do that. Hermes -- "um, I don't ***. Or github." Fine, Hermes, are you using the latest release? Hermes -- "gosh, no I'm not. Maybe you should update before filing this nicely formatted bug report YOURSELF." In the words of Thanos -- "Fine, I'll do it myself." And now 5th. So I upgrade Hermes app. Hermes restarts. My sessions show up on left. I click my 4-day-long session. It opens on the screen. I submit a request to start another try to write a clean Python file. A NEW session opens up, for the question. Hermes tells me "i have no idea what you're talking about." WTF?? I click old session. It opens. I ask Hermes why it switched sessions. Hermes OPENS A NEW SESSION and tells me, "new session? I didn't open a new session. Please explain." My old session grins at me evilly from the left side panel. I click on the bastard AGAIN. It opens again. I type a third question.... A NEW session pops open and is in command. I click on the old session once again. It opens. Then I see an alert in virtually identical color as rest of the app interface -- "resume failed: no xai oath credentials stored...." So back through setup. Get ANOTHER token from xai. Great, Hermes is grokking grok again. I click my old friend again. Up pops the error -- faintly. Hermes, I say, we just fixed that. Hermes pops up A NEW SESSION and says "I have no idea what you're talking about." I ask new session why I can't restart old session. Hermes-- "oh, that session is locked to an oauth key. That key isn't anywhere to be found." Erm you said switch to perm token 3 days ago, and prior to upgrade you asked to delete unused oauth tokens, and I said OK. Hermes -- "you'll need that to unlock that session." Argh. I ask Hermes if it can import the conversation. Hermes -- "I can read in the text. But its REALLY long!" Do it! Reads into new session. Missing the tech docs imported into original session. Argh. And now we are at today. Sigh. I'll keep trying, but....
-
M’Barak Al Hmood مبارك بوحمود الحمود (@m8arak) reported@github It’s broken link sounded like a prank
-
Ming (@tslaming) reported@Squirrel1980021 That is usually the biggest catch with custom solutions, as proprietary protocols often fragment the industry and lock people in. However, the great news here is that Tesla actually open-sourced it to prevent exactly that. They released the entire specification as TTPoE on GitHub during HotChips 2024 and even joined the Ultra Ethernet Consortium. So instead of keeping it locked down as a proprietary secret, they are actively working to make it an open standard that the entire high-performance computing ecosystem can use and build upon.
-
Julien (@julienzeroshot) reportedAm I the only who is dying of frustration with how bad the Github PR experience is? PRs loading extremely slow, layout shift after load causing misclicks, ... Exhausting.
-
Matthew Belcher (@Trigun420) reported@reach_vb For the in-app browser I constantly get codex telling me that localhost is blocked by my own security policies. I have tried adding it to the allowlist, updated config.toml, etc.. Is there a fix for this? Github issues are present as well...
-
Mike Greiling (@mikegreiling) reported@MattHartman @github @claudeai somebody recommended it in some discord channel I'm a part of, I honestly don't remember which one. I've had it installed and have been using it for several weeks now. It's great! I just decided today to click "check for updates" button in the menu and it gave me an obtuse error
-
Zee 💌 Holofunk arc (@z_zmag8) reported@proluigi_ I believe that too, like ppl in that github server can just be hiding stuff you know base game is FULL of surprises
-
Hoang Nguyen (@Namas1012) reported@chipcoin_CHC There's a bug in the source code; I've submitted the issue to GitHub, please check it out.
-
Victor Campos (@CamposLVictor) reported@AkitaOnRails This time I don’t know this is the problems 12h before this GitHub api was off globally This time I think is the GitHub itself making a mess
-
Danny Herrmann (@MuffinDannyH) reportedI mostly do website development and the most annoying thing with claude, codex or cursor is that every time i open them i have to re explain my whole project again. folder structure, tech stack, previous decisions, everything. context just resets and i start from zero every single time. Connected @heydittoai MCP a while back and now the agent actually remembers stuff from previous sessions. it keeps the context and can directly go into my project files and make changes. same model but the output feels way more consistent now because its building on what i already told it before. Setup is also pretty straightforward, one click login with google, apple or github works fine. even if youre using hermes or openclaw, one prompt and it connects and starts working on its own. plus it keeps backing up my files automatically. If you work with agents regularly this layer actually saves a lot of time. #Bittensor bittensor:native
-
Elvis (@elvissun) reported@ktusing34 nice! will tune this, there's no server for API so maybe I'll send people to open a github issue can you share more on the quality? I'm trying to figure out how to optimize the setup so people get good results on the first run
-
루이 (@_chiiazu66) reported@Fluffyquack If anyone is stuck on finding the update like I was, just go through the RE Framework github, the latest update is on there and it works perfect once you replace it with that one. Some mods may still be broken (the fov one I used needs an update for example)
-
Dan (@jewishterminal) reported@ziwenxu_ @PumpSkywalker69 Bro, it’s all about the GitHub too. I mean; you can name it whatever you want. The GitHub will he the main issue. But even there are some loops to go around and fight the lawsuit ofcourse. Believe me; the name wouldn’t be the main reason for a lawsuit lmfao.