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 |
|---|---|
| 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 | 1 |
| Colima, COL | 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:
-
John D. Clay (@JohnDClayAuthor) reported@XFreeze I tried out the new update to Grok Build last night and put it to the test. It helped me go back to a far previous session, it actually has all sessions in a nice area to look at and choose from. I challenged it to fix a broken framework I had built with the earlier versions of Grok Build and with the help of @grok too. I had published it a couple weeks ago and it was not working well. But now after a couple prompts... clayforge the first ai-matove framework for multi agent UI's. You should check it out if you are coding with AI. It's on GitHub.
-
David O. Ehibor 🇦🇷 (@grayontop_) reportedGitHub Copilot didn't make developers faster It made slow developers more confident about writing bad code quickly 😭
-
Asad (@meranaamkhann) reportedLet's see what people are building these days!! Drop your project link or github Links down here
-
Ucupaint 🔶 (@ucupaint) reported@iye_jr It works fine here. Check if the paint mask is turned on or not. If you still have a problem, please file a github issue with a sample file.
-
Harry Tandy (@HarryTandy) reportedAndrej Karpathy: "Neural networks are not just another classifier. They are Software 2.0" 8-step MCP setup for vibe coders: 1. Context7 Give the agent fresh docs before it writes code This saves you from old Next.js, Supabase, Stripe, and Vercel patterns 2. GitHub MCP Let it read the repo, issues, PRs, branches, and CI logs The task should start from real project context 3. Playwright MCP Make the agent open the app after it edits code Click the flow. Fill the form. Check the screenshot 4. Supabase or Neon MCP Connect the database layer The agent should inspect schema before inventing table names 5. Sentry MCP Use production errors as input Stack traces beat “the app is broken” every time 6. Firecrawl MCP Let the agent read current web pages as clean markdown Docs, changelogs, competitors, pricing pages 7. Figma MCP Give it the actual design Spacing, copy, layout, components 8. Linear MCP Turn the work into tickets Tasks, comments, follow-ups, PR links The rule: If you paste the same context twice, wire it into MCP That is how vibe coding becomes a build loop instead of a long chat
-
xjdr (@_xjdr) reported@tolly_xyz @xlr8harder Sorry about that. I'll take a look. Looking with GitHub or Gmail should work but track this down and fix it asap
-
Tim Spalding 🇺🇦 (@librarythingtim) reported@justin_v_w This is a formal notice for you to shut down your wasteful, invasive and privacy-violating LibraryThing profile scraper and remove it from GitHub. Please reply to confirm that you have done so.
-
DFIR Radar (@DFIR_Radar) reportedAutoJack: a three-flaw chain in AutoGen Studio's MCP WebSocket lets a malicious webpage rendered by a local browsing agent spawn arbitrary processes on the developer's host with no user interaction beyond visiting a URL. Key findings: - Three weaknesses chain together: Origin allowlist bypassed because the agent's headless browser is localhost (CWE-1385), auth middleware explicitly skipping /api/mcp/* with no handler picking up the check (CWE-306), and server_params decoded from the URL passed verbatim to stdio_client as a command line (CWE-78), accepting calc.exe, powershell.exe, or bash as valid "MCP servers" - Attack flow: attacker page serves JavaScript that opens ws://localhost:8081/api/mcp/ws/?server_params= with a base64 payload, agent's MultimodalWebSurfer renders it, AutoGen Studio spawns the command under the developer's account, no token required regardless of auth mode configured - Affected code never shipped in a PyPI release; exposure limited to developers who built from the main GitHub branch before hardening commit b047730, which adds server-side parameter binding via a POST/UUID flow and removes /api/mcp from the auth skip list - Broader pattern: any agent that browses untrusted content and shares a host with a privileged local control plane dissolves the loopback trust boundary, this is not specific to AutoGen. #DFIR_Radar
-
naimeh (@naimeh70) reported@Amir1339216RKT This happens a lot during testnets. Now when I find a minor bug or contract issue, I just drop it publicly on GitHub or tag them directly instead of DMing.
-
Chris Huber (@chubes4) reported@CoastalDigital2 @MythThrazz That part is more of an idea right now. I need to test it on my VPS. The goal is that non technical users can open issues and PRs against the corresponding live site code on GitHub without touching the production site, safely previewing all changes via Playground.
-
Anjula Dwivedi (@HeyAnjula) reported9/ Headless mode for automation claude -p "your prompt" runs Claude Code without the UI — perfect for CI/CD. Auto-fix lint errors on every push. Triage new GitHub issues. Generate release notes. Claude Code isn't just a tool you talk to. It's a tool your pipeline talks to.
-
fks (@FredKSchott) reported@pavitrabhalla @flueai Same! check the GitHub issues, there was a reason it had to be pulled, can’t remember off top of my head
-
𝐇𝐚𝐦𝐳𝐚 | Network Engineer (Aspiring) (@Hamzaonchain) reportedHere's a summary of what happened in case you didn't hear about it... A cyber extortion group called FulcrumSec (active since late 2025) hit Novo Nordisk the company behind blockbuster drugs like Ozempic and Wegovy pretty hard. They snuck in back in March 2026 through a compromised GitHub access token, roamed around for over two months, and walked out with roughly 1.3 TB of data across 700,000+ files. Now they've started leaking a 264 GB sample publicly. Inside? Source code, proprietary formulas for pipeline drugs like Amycretin (their next big obesity hope), clinical trial records, employee and patient data, manufacturing details, and even private internal AI models for drug discovery. The hackers straight-up roasted Novo's security, pointing out laughably weak hardcoded passwords like "novo123" and "p_assw0rd" in critical systems. After Novo reportedly turned down a $25 million ransom, the group decided to start dumping samples and shopping the rest around privately. Novo confirmed a limited breach in early June involving some pseudonymized patient data from trials. They say there was no major operational disruption and that they're working with experts but this feels like a massive wake-up call for the entire pharma industry on basic security hygiene. Crazy how a simple token slip-up can expose billions in IP and sensitive health data. What's your take — do you think this will finally force better security practices, or is it just another headline that'll be forgotten in a few weeks?
-
Jarrad Grigg (@jarradgrigg) reportedYou build stuff and host on GitHub publically? Paste this into a coding-agent session and point it at your own GitHub account. This is happening way too much. ROTATE YOUR KEYS. Review my public GitHub repositories for accidentally exposed environment secrets. Scope: - Only inspect repositories I own or explicitly authorize. - Focus on public repos first. - Check current files and *** history. - Look for API keys, tokens, private keys, database URLs, OAuth secrets, webhooks, cloud credentials, .env files, config dumps, and hardcoded secrets. Safety rules: - Do not print full secrets in chat. - Redact values, showing only provider/type, file path, line, commit SHA if relevant, and a short masked prefix/suffix. - Do not test or validate secrets by calling third-party APIs. - Do not open PRs, issues, or comments that expose findings publicly. - If a likely secret is found, assume it is compromised and tell me to rotate or revoke it. Deliverable: - A prioritized report of confirmed or likely exposed secrets. - Exact repo/file/line/commit references. - Recommended rotation steps by provider. - Cleanup guidance for removing secrets from current files and *** history. - Prevention recommendations: .gitignore, env templates, secret scanning, pre-commit hooks, and CI checks.
-
AJ ✝️ 💚🧡 (@angelcreative) reported@uiux_hamad My design team is leaving Figma gradually, in fact we are using Cursor and GitHub as main design tools now, in the past two months the usage of Figma drops 33% and it will keep going down up to 30% more to a 63% in total and maybe more