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 | 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 |
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:
-
Zhu Liang (@paradite_) reportedi found it really suspicious that vercel auto-deploy from github is currently down when fly. io is down. maybe vercel uses fly. io for auto-triggering deployment from github?
-
VC Intern (@the_vc_intern) reportedA startup just came out of stealth with $66M because AI agents are about to start logging into work. NewCore is building identity security for companies where humans, machines, and agents all need access to internal systems. It is already valued at $300M, backed by Cyberstarts, Index Ventures, and Evolution Equity Partners. Imagine a coding agent inside Claude Code or Cursor. It needs GitHub access to open a pull request, Slack access to read the bug report, Jira access to update the ticket, and maybe Snowflake access to check the data behind the issue. That agent now has a job. It also has permissions, credentials, an owner, an audit trail, and eventually an offboarding problem. This is where old identity systems start to look outdated. They were built for employees and machine accounts, not thousands of software workers moving across company tools at machine speed. NewCore says agents should get first-class identities, with their own permissions, lifecycle controls, and revocation. That is the real infrastructure hiding under enterprise agents. Every useful agent needs a badge. Every powerful agent needs a manager. Every risky agent needs a way to shut it off.
-
Dao world (@Koreanteacher1) reportedI think you are totally misunderstanding something. Pi core team is not trying to build a DEX from scratch. They are not trying to reinvent the wheel. They are trying to figure out how to apply an existing DEX model to Pi in the right way. You can see this just by looking at the website, the app descriptions, or even GitHub. What the core team is really thinking about is how to reduce the usual problems in token launches, like rug pulls and whales holding too much of the token supply. That is why they keep testing the Launchpad. It is not just about launching tokens quickly. It is about creating a safer and more practical way for real utility tokens to be launched inside the Pi ecosystem.
-
Jason Nguyen (@jasonngsx) reportedsomeone built a note app where every vault is a *** repository, every note is a plain Markdown file on your machine, and the whole thing is free. it's called Tolaria. the architecture is the point. there's no cloud sync to pay for. *** handles history, branching, conflict resolution, and syncing across machines. the same infrastructure you already use for code, now managing your notes. here's what that unlocks: → every vault is a *** repo. *** push syncs it. *** log shows every edit. no proprietary cloud watching your notes. → plain Markdown + YAML frontmatter. the format is yours. not theirs. → AGENTS.md support built in. Claude Code, Gemini CLI, and Codex can read your entire vault context natively, without a plugin. → built-in MCP server. connects to Claude, local LLMs, or any MCP-compatible tool directly. → command palette, keyboard-first. Tauri binary for macOS, Windows, and Linux. → zero accounts. zero vendor dependency. zero subscription. the creator runs 10,000+ notes in his personal vault with it. 13K GitHub stars. 918 forks. open source. free. brew install --cask tolaria most note apps don't say this out loud, but their business model is the sync layer. Obsidian cloud sync is $4/month. Roam is $15/month. Notion keeps your notes in a proprietary database. Tolaria removes the sync layer and replaces it with ***. in 2026, when your AI coding agent needs to read your notes for context, you want those files on your machine in a format every tool understands, not sitting in someone else's cloud.
-
Jeremy Nguyen ✍🏼 🚢 (@JeremyNguyenPhD) reported@ErenChenAI GitHub link seems to be down
-
Faisal Karim (@Le__FaiCee) reported- Claude for coding. ($20/mo) - Supabase for backend. (Free tier) - Vercel for deploying. (Free tier) - Namecheap for domain. ($12/yr) - Stripe for payments. (2.9% per transaction) - GitHub for version control. (Free) - Resend for emails. (Free tier) - Clerk for auth. (Free tier) - Cloudflare for DNS. (Free) - PostHog for analytics. (Free tier) - Sentry for error tracking. (Free tier) - Upstash for Redis. (Free tier) - Pinecone for vector DB. (Free tier)
-
Kirtesh (@AKirtesh) reported𝗧𝗼𝗽 𝟭𝟮 𝗧𝗵𝗶𝗻𝗴𝘀 𝗘𝘃𝗲𝗿𝘆 𝗗𝗲𝘃𝗲𝗹𝗼𝗽𝗲𝗿 𝗦𝗵𝗼𝘂𝗹𝗱 𝗛𝗮𝘃𝗲 𝗶𝗻 𝟮𝟬𝟮𝟲 📌 1. Cursor (AI Code Editor) 2. Claude 4 Subscription 3. Notion (Second Brain) 4. Raycast (Mac Productivity) 5. GitHub Pro 6. Supabase / Neon Postgres 7. Vercel / Railway Account 8. Figma (Design) 9. Linear (Issue Tracking) 10. Arc Browser 11. Wise Account (Payments) 12. A strong personal domain Save this. 📌 What’s missing in this list? 👇
-
foxystack (@foxy_stack) reportedThe jailbreak that caused the US government to shut down Fable 5 is now fully documented. The 120,000 character system prompt is on GitHub. Anyone can read it. #github #Fab5
-
The Glowtail/RatEmperor/Poweringsales (@Glowtail31) reported@LuuvsLuna @BrisketCaek I gotta love linux when it comes to downloading **** God that flatpak github bullshit is brilliant So brilliant and not stress inducing God I loved hot setting up and Manager for a game because of some bullshit and you spend a month trying to fix it to work again.
-
Jon Oringer (@jonoringer) reportedIt started with a message from a recruiter at a small crypto startup. She described a broken proof-of-concept they needed a lead engineer for and sent a public GitHub repo to review. Specifically, she asked to "check out the deprecated Node modules issue.
-
Data Wolf 🐺 (@0xDataWolf) reportedWeird tip: Don't use native Hermes to set up Camoufox. Give it the Camoufox repo on GitHub and get it to install it, and most importantly, GET IT TO USE DOCKER to host Camoufox. THEN hook Hermes up, and write a skill on how to use it for the next AI session. This makes it easy for Hermes to debug Camoufox issues. If you leave it running as a PID background thing, it will keep bugging out while struggling to fix it
-
Chris Schuchardt (@c_schuchardt) reported@erikzhang @kurubatermit @ngd_neo You’re the only one (besides superboyiii or Owen) with the actual permissions to remove someone from the core dev team in the GitHub repo. I was removed after my transparent 4-month school break — which I notified the entire team about in advance, with a planned return in ~90 days. This isn’t about money. It’s about getting $NEO to a proper coding and application standards. Here is the message from Discord `Neo Core Developers` server.
-
Karl ₿ 🇮🇸 (@Charles28378449) reported@aeonBTC I'm not very familiar with GitHub and don't use it much, so I took the liberty of reporting the issue here since I'm a regular user of your wallet :)
-
David Hendrickson (@TeksEdge) reported🆕 Mistral Vibe (coding agent harness) just released some big coder updates! 🪝 before_tool & after_tool hooks Shell scripts in hooks.toml so you can deny, rewrite inputs, or append context around every tool call. Enable: enable_experimental_hooks = true 📬 Message queue while it worksType ahead freely. Esc = pause queue • Ctrl+C = drop last • Enter = flush 📝 Cleaner file edit diffs Syntax-highlighted + line numbers that match your terminal theme 🧠 Smarter compaction Re-injects your original messages after context reset so it stays on-task ✅ QoL winsTool results collapse by default • Read-only commands (ls, cat, pwd) run without approval GitHub issue automation via Skills + Studio connectors (Linear too) Open-source CLI • Web Code Mode • VS Code extension
-
Gill (@gurtej__gill_) reportedThe biggest AI skill shift in 2026 isn’t prompt engineering. It’s LOOP ENGINEERING. Most people still work like this: → Prompt AI → Get output → Review manually → Fix mistakes → Prompt again The human is still doing the hard part: the feedback loop. Loop engineers think differently. Instead of writing better prompts, they design systems that: -Discover what needs to be done -Plan the work -Execute tasks -Verify results -Fix failures -Repeat until the goal is achieved A good loop has 6 building blocks: 1-Automations (triggers) 2-Worktrees (parallel workspaces) 3-Skills (reusable knowledge) 4-Connectors (GitHub, Slack, Jira, etc.) 5-Subagents (makers + checkers) Memory (what happened before) The future isn’t:“Write me a function.” It’s:“Write it, test it, fix it until it passes, then summarize the changes.” Prompt engineers optimize outputs. Loop engineers optimize outcomes. A reliable loop beats a perfect prompt every time.