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 |
|---|---|
| Paris, Île-de-France | 6 |
| Ahmedabad, GJ | 1 |
| Delme, ACAL | 1 |
| Lyaud, Auvergne-Rhône-Alpes | 1 |
| Catania, Sicily | 1 |
| Inverness, Scotland | 1 |
| Quito, Pichincha | 2 |
| Junín, Manabí | 1 |
| Guadalajara, JAL | 1 |
| São Paulo, SP | 1 |
| Ipauçu, SP | 1 |
| Vigo, Galicia | 1 |
| Tel Aviv, Tel Aviv | 1 |
| Éragny, Île-de-France | 1 |
| Saltillo, COA | 2 |
| Montlhéry, Île-de-France | 1 |
| Aulnay-sous-Bois, Île-de-France | 1 |
| Granada, Andalusia | 1 |
| Vernon, Normandy | 1 |
| Township of Evan, KS | 1 |
| Madrid, Madrid | 1 |
| Bogotá, Bogota D.C. | 1 |
| Lyon, Auvergne-Rhône-Alpes | 1 |
| Lima, Lima | 1 |
| Aix-en-Provence, Provence-Alpes-Côte d'Azur | 1 |
| Trento, Trentino-Alto Adige | 1 |
| Le Chambon-Feugerolles, Auvergne-Rhône-Alpes | 1 |
| Antananarivo, Analamanga | 1 |
| Lure, Bourgogne-Franche-Comté | 1 |
| Ashkelon, Southern District | 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:
-
Ravi Prasad (@ravikp7) reportedBig NO to Github hosted CI runners for personal projects now. I have setup a self-hosted github CI runner on a spare laptop running ubuntu server. Been running it for 10 days and I did some calculations, for my usage if I run it on Github runners, it'd cost me around 200$ vs < INR 100 on electricity (local setup) monthly.
-
siggy bilstein (@sbilstein) reportedfyi if you sync a GitHub repository to Cursor Origin and GitHub is down for whatever reason, you can still clone and fetch from that repo. we’re also releasing something pretty soon that will let you push to that repo so you can keep grinding 💪
-
mrgadget (@mrgadgetstudio) reported@EzekielCrrypt I still deploy code to github, what's problem?
-
Åsa-Nietzsche (@AsaNietsche) reported@peterb0yd @burkeholland @github It's every ******* model. I'm getting whiplash from all of this everything changing forever society being turned upside down every two weeks.
-
Yuvraj Singh (@Yuvraj_Singh317) reportedStarted building Etio: a GitHub Action that bisects a failing CI run to the exact breaking commit, diffs it, and asks an LLM to explain why it broke, then comments the diagnosis on your PR. No Docker, no server- runs on your own Actions minutes. Open source, WIP.
-
Blue Collar Executive (@A_Sober_Drunk) reportedon the third try at the same problem, I told Grok to "stop and go search stack overflow or github or something"... five seconds later... Literally the exact issue, problem solved. That's how new global rules are born.
-
Ash Lonare (@ashlonare) reportedWhat actually happened when I put my side project on GitHub and waited for users I built a side project. A self-hosted backend tool. Open source, free for anyone to run. I did the thing every founder tells themselves they will do. Put it out there. Get feedback. Iterate. I expected feature requests. Maybe a bug report about my ugly dashboard. Maybe just silence. What I actually got, within a few weeks, was three security researchers filing detailed vulnerability reports. Real ones. With working proof of concept. One showed they could run arbitrary SQL against any project on the platform. No login needed. Not theoretical. A working exploit, sitting in my issue tracker, with my name on the repo. My first reaction was not gratitude. It was embarrassment. It stings to see "here is exactly how broken your thing is," posted in public, with a timestamp. I sat with it for a day. Then it clicked. Those people were not trying to embarrass me. Nobody spends an hour writing a clean writeup and a suggested fix for something they do not think is worth fixing. They cared. That is the whole thing right there. They cared enough to actually try to break it. Nobody had signed up. Nobody had left a star and a "nice tool" comment. But three strangers had taken my work seriously enough to attack it. That is a rarer thing than a star. So here is the villain in this story, if you want to call it that. It is not the bug. It is the story I tell myself when I see a hard truth about my own work. The instinct to read scrutiny as an attack instead of as attention. I fixed everything the same day. I replied to every report and explained exactly what changed and why. I closed each one out with a thank you that I actually meant by the end. That thread is now the best proof I have that someone other than me has used this thing for real. Better than any testimonial I could write myself. If you are early and the silence feels loud, here is what I would tell you. Do not wait for praise as your sign that people are paying attention. Scrutiny is attention. It is just wearing a different coat. #opensource #saas #vibecoders
-
Joshua Okolo (@joshuaokolo_) reportedwe made @sgl_project and @vllm_project scheduler config changeable on a live server. no restart, weights never leave the GPU. - 15ms to change a concurrency cap, queue limit, prefill size, or schedule policy, measured on H100, RTX PRO 6000, B200 - 2s (SGLang) / 8–10s (vLLM) to resize the KV pool with weights resident (formerly a 1–7 min redeploy) - zero dropped requests across every run, both engines github below
-
阮添福-ThiênPhúc (@vietroadie) reportedFeature request for @TradingView @TrendSpider @Schwab (ThinkOrSwim) engineering teams: Please add GitHub-native CI/CD for custom indicators. Connect a repo → validate on push → deploy approved scripts to my workspace → full version history + rollback. 1/ The Problem I maintain the same level set across ThinkScript, Pine, and JS. One level change = 3 manual copy/pastes into 3 browser editors.Result: drift between platforms, stale timestamps, and levels that silently disagree mid-session. No audit trail of what changed or when. 2/ Core ask — repo connection • OAuth GitHub App install, scoped to selected repos • Map a file path → a specific study slot (e.g. ES Levels/ES_LEVELS.pine → "ES Levels") • Branch selection (deploy from main, preview from a branch) • Config in-repo, e.g. .tradingview.yml / .trendspider.yml 3/ Core ask — validation • On push/PR: compile + lint the script server-side • Return errors as GitHub check runs with file + line numbers • Block merge on compile failure • Optional: run a backtest or smoke-render and post results as a PR comment 4/ Core ask — deploy • Auto-deploy on merge, or manual "promote" button • Atomic: study updates or fails cleanly, never half-applied • Deploy to draft/private first, publish separately • Preserve user-set inputs across deploys where param names are unchanged 5/ Core ask — versioning & safety • Every deploy tagged with commit SHA, author, timestamp • Version list in the UI with diff view • One-click rollback to any prior commit • Dry-run mode • Deploy log / webhook on success + failure 6/ Minimum viable alternative If full CI/CD is too big, just ship a documented REST API: GET/PUT /studies/{id}/sourcewith token auth + rate limits. We'll build the GitHub Action ourselves. That single endpoint unblocks the entire workflow. 7/ Why it matters Scripts are code. Code belongs in version control with review, CI, and rollback. This is table stakes in every other dev ecosystem — and it directly reduces the risk of a bad indicator edit going live during market hours. Who else needs this? 🙋
-
NitroStack (@nitrostackai) reportedThe missing primitive might be capability contracts. A Skill shouldn’t say “call Jira.” It should say “I need issue.write.” Then MCP can bind that capability to Jira, Linear, GitHub… whatever exists. That’s basically dependency injection for agents.
-
Avinash (@Avinash25818689) reportedPeople who want to start contributing to open source: - Pick an Org based on your interest - Fork the repository - Clone it - Do the local setup - Read README and contributing .md - Pick an issue - Create a new branch - Fix the issue - Write tests (if necessary) - Test it - Add, Commit & Push the code - Go to GitHub & raise that PR That's pretty much it. Start small and learn as you go.
-
AI Scientist (@AIScientist_X) reportedNEWS: X LANDS FIRST PUBLIC ALGORITHM PR > X OPEN SOURCE SAID SEP 1 THAT AFTER 2 PLUS WEEKS OF DAILY UPDATES IT INTEGRATED A FIRST PUBLIC CONTRIBUTION AND THAT THE CHANGE IS NOW LIVE ON X. > IT SAID THE SMALL UPDATE IS BASED ON GITHUB PULL REQUEST 55. X CLOSED THAT PR AS COMPLETED AFTER LANDING ITS OWN FIX. SOURCE: X OPEN SOURCE
-
Ben (@benatcortexai) reported@github this is the kind of tiny primitive that makes agent workflows less brittle. attaching the repro artifact directly to the issue beats handing an agent a local path nobody else can open.
-
Conor Bronsdon (@ConorBronsdon) reported.@SlackHQ is building for multiplayer AI: tag a coding agent into a Slack conversation and it spins up a coding channel: everyone in that convo gets a live dev environment, diffs post as artifacts, and the channel winds down when the task is done. With the launch of Slack Code, Claudeforce, their MCP and more, Slack is putting Agents in the channels where teams already work, not simply in a private chat with one person. Their position is that the whole team should be able to watch, steer, and review what the agent does. Slack Chief Product Officer Jaime DeLanghe joined me on @chain_ofthought to explain how Slack is building a team AI environment, what happens mechanically when a code channel is created, why Anthropic pushes so much of its code through Slack, how the channel permission model became the agent context model, and what has to change in engineering culture when the whole team is steering one agent. I think Slack is the platform best positioned to become the context harness where enterprise agents run: agents that see what the team discusses, permissions that already exist, and a cultural opportunity hiding inside every multiplayer coding session. Chapters: (0:00) Slack as an IDE and a GitHub for your team (0:29) Who is Jaime DeLanghe (1:21) The reaction to the Slack Code launch (5:30) Why coding agents belong in a context-rich environment (6:08) Engineers now manage agents, not copy-paste code (7:24) The permission model: agents get the channel's context (11:44) What happens when a code channel is created (15:00) Why Anthropic pushes so much code through Slack (19:14) Steering one agent with many people: culture decides (24:54) Slackbot, skills, and MCPs: agents go where the work is (30:53) The solo terminal vs. agents in social spaces (33:53) Org charts and ownership when agents join the team (39:33) Learning loops and shared agent memory (42:39) Citations, recency, and accidental knowledge management (46:50) Context bloat and multi-pass search for agents (50:01) How Jaime uses Slackbot as CPO (52:38) Slack Code is V1 of multiplayer AI
-
Russ Wonsley (@RussWonsley) reportedMy @bot tells me that the official GitHub login for bot is still broken. Has this been addressed already, or did I miss it?