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 |
|---|---|
| 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 |
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:
-
looney (@C8Luna) reported@NoBSRecruiter @theo In no way shape or fashion was Github Copilot a terrible product. It started the journey with simple code completions with a full featured agentic workflow as good as the the others but had the cost advantage.
-
mattoftheland (@mattoftheland) reportedI really hope Microsoft is doing something to fix all these supply chain compromises on Github and NPM. It's ridiculous this is happening daily.
-
Lummox (@Lummox_eth) reportedPEOPLE INSTALL 30 PLUGINS, BUILD 15 FOLDERS, AND NEVER OPEN OBSIDIAN AGAIN AFTER DAY 1. They build a system for an imaginary version of themselves. If capturing a thought takes more than 10 seconds, it does not happen. The fix is 4 folders only. Inbox for everything unprocessed. 5 plugins worth installing : > Templater for consistent formatting > Dataview to query notes like a database > Calendar for daily note navigation > QuickAdd to capture from anywhere > Obsidian *** for automatic backups to GitHub. The weekly review is where the system compounds. 20 minutes every Sunday. Process inbox, open 3 random notes and ask what they connect to, plan next week. That single habit turns a vault from an archive into a thinking partner.
-
HumanPulse Protocol (@HumanPulse_HPP) reportedDevelopment is continuing: when logged in, we can still access the repositories and pushes are working. The issue appears to affect public visibility, GitHub search, and third-party developer integrations. HumanPulse remains active.
-
Patricia Juarez Muñoz (@ccsakuweb) reported@AnnoyingItch251 Yes, it's due to the tokens used and not a pricing problem. And there are solutions to avoid using too many tokens. Github should optimize and guide us how to use less tokens. But so far it seems it depends on us.
-
Dodge This Security (@shotgunner101) reported@5mukx Its the new normal for github ever since Microsoft bought it. The only chance you have of it getting reverse is from community pressure but it this issue repeatedly occurs over time. So your better off moving to alternative solutions Microsoft doesn't control unfortunately.
-
Jesus (@codexJesus) reported@guinnesschen Prompt: Scan GitHub for bug reports, and then for the easy looking bugs, create new threads in worktrees to fix them. For the most important ones pin them as well
-
The Whizz AI (@TheWhizzAI) reportedYouTube just raised prices again. $15.99 a month. $192 a year. To remove ads from a free website. Every video you watch is tracked. Every search is logged. Every pause, every rewind, every rabbit hole at 2 AM. All of it was sold to advertisers without asking you once. You are not the customer. You are the product. You always were. Then I found this. 20.3k stars on GitHub. Built since 2018. And barely anyone knows it exists. It is called Invidious. → No ads. None. Ever. Pre-roll, mid-roll, banner, and sponsored are all gone. → No Google account. Subscribe to channels anonymously. → No tracking. No cookies. No fingerprinting. Nothing sent to Google. → No algorithm deciding what you watch next. → SponsorBlock built in. Skips sponsored segments automatically. → Audio only mode. Halves the data and battery usage. → Background play on mobile. Free. Without Premium. → Download any video. Any quality. Any format. → RSS feeds for every channel. → No JavaScript required. Works on any browser. → Self-host on any old laptop. Here is the wildest part: YouTube sent a cease and desist on June 9, 2023. Told them to shut down in 7 days. Invidious said no. Last commit was 14 hours ago. 269 contributors. 2,100 forks. Three years later, still shipping. Google has spent three years trying to block, sue, and bury this project. They have failed. Every commit is a middle finger to the ad industrial complex. YouTube Premium: $15.99/month. $192/year. YouTube Family: $26.99/month. $323/year. YouTube Music: $11.99/month. $144/year. Invidious: $0. Forever. No ads. No tracking. No account. 269 contributors. 33 releases. 2,100+ forks. Built in Crystal. Battle-tested since 2018. AGPL-3.0 licensed. The license Google cannot kill. Your videos. Your privacy. Your choice. 100% Open Source. (Link dropped in the comments)
-
🏴☠️ (@wackoiam) reportedwith GitHub features and workflows What would you like to work on today? You can: - Ask me to review or summarize a pull request - Search for code or issues in a repository - Create or manage GitHub issues - Debug errors or stack traces - Or anything else related to your
-
Yusuf Nuh 🍉 (@SenseWave_) reported@ZackKorman @NinjaParanoid It's sick. Just days ago we see they're saving are passwords as plain text. And now threatening researchers for their research. They even took down one GitHub account, that published vuln
-
CY (@Chibuezay) reported@pxxl_space I tried getting a domain a few minutes ago but it seems there's an issue with the GitHub login.
-
Faust (@___faust____) reportedthis is the part that gets lost when every dep is just a 'npm install' away. debian maintainers were the original security scanners, unpaid and unthanked. now we just yell at random volunteers on github issues
-
Kerry Burn (@kerryburn) reportedMicrosoft Build: AI everywhere. The bit nobody slides: loads of firms bought Copilot, few get real value. Meanwhile attackers hit GitHub editors & hijacked dev packages. Lesson’s the same — do the boring groundwork, then point the clever tools at a real problem. 848.grou
-
Maciej Soroczyński (@soroczynski_com) reportedMore about base64 that been use for hacking GitHub: Why do hackers use Base64? Przegląd od AI Hackers use Base64 primarily for obfuscation (hiding their tracks) and system compatibility rather than for encryption. Base64 is an encoding method that translates raw, unreadable binary data (like malware executables) into a safe, standard string of 64 printable text characters (A-Z, a-z, 0-9, +, and /).Here is exactly why threat actors rely on it:1. Evading Security Filters (Obfuscation)Naive security filters, firewalls, and antivirus solutions look for specific malicious text or keywords. By encoding malicious scripts (like PowerShell) into a Base64 string, hackers turn recognizable code into an innocuous block of text, allowing the payload to slip past these defenses undetected.2. Safely Transporting PayloadsBase64 was originally designed to transmit binary files (like images or attachments) over text-only protocols like email (SMTP) or web traffic (HTTP) without the data getting corrupted. Hackers use this exact same property to inject malicious files or commands directly into web requests, HTTP headers, or cookies.3. Hiding Command and Control (C2) TrafficWhen malware communicates with a hacker's server, it often needs to send stolen data or receive instructions. If the malware sends this data in plaintext, network defenders and Intrusion Detection Systems (IDS) will easily spot it. Encoding the traffic in Base64 hides the intent of the communication, making it look like standard web traffic.4. Bypassing Bad Character LimitsCertain communication channels—such as URLs or specific command-line arguments—will crash or misinterpret complex binary characters. Because Base64 strictly uses standard, keyboard-friendly ASCII characters, hackers can use it to safely pass their code through restrictive input fields without breaking the system.Important note: Base64 is not encryption. It is just a different format for representing data. Anyone (and any modern security tool) can decode a Base64 string back to its original form in seconds using freely available tools like CyberChef.
-
Imran (@imranity) reported@github is broken ...