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 |
|---|---|
| Veigné, Centre | 1 |
| Paris, Île-de-France | 1 |
| Saint-Paul, Réunion | 2 |
| Mexico City, CDMX | 1 |
| León de los Aldama, GUA | 1 |
| Créteil, Île-de-France | 1 |
| Trichūr, KL | 1 |
| Brasília, DF | 1 |
| 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 |
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:
-
Charles Waters (@RelaxedPop) reportedSlashdot, YCombinator, various non-toxic Reddit subs, various Github and Hugging Face groups. Many of them are better than X. X's message feels like a staccato, somewhat random collection of posts while the others are better curated. Please note: I'm terrible at curating my X feed. It's all garbage and I'm fairly certain that there are things I can do to fix that.
-
pareidolia (@cloudsfables) reported@lex_node @armaniferrante Yes, and the main people not caring about the safety of the funds of users were the Ostium team: > No bug bounty program. > Even their GitHub link is broken. But Armani sends his love to them while advocating for even more user policing and worse UX...
-
Grey G. 🇦🇶 (@gr3yg00) reported@cpt_mayhem Yes, but not yet. I'm planning to put the 3D files and instructions on how to build on github once it's completely done. Basically it's a 24V power supply I took from a broken 3D printer in the base and power converters that drive two stacked peltier elements of 90W on a CPU fan
-
Ryan (Struggling with life NGL) (@ryanyates1990) reportedOh 💩, I did it again @github I smashed your endpoints & then you complained & put me on the naughty step Shame this is slowing down manually writing and testing some code I need for #PowerShell working groups. But gives me chance to write the blog post around all this instead
-
Will Stith (@TheStithLord) reported@gregpr07 Yeah this effectively isn’t open source… they just snapshotted their codebase and dumped it one time into a locked down but public GitHub repo. It’s obvious this is not the actual source of truth for the codebase
-
Harman (@itsharmanjot) reportedGoogle just published an open standard for how knowledge bases talk to AI agents. Most of the early tooling around it is scattered, MCP servers, converters, plugins. This is one of the first that actually publishes it as a real website. Someone turned a folder of chaotic notes into an AI-readable knowledge base with an obscure open-source tool, and there’s zero vendor lock-in anywhere in it. It’s called Kiso. A static-site generator for the AI-agent era: you write your knowledge base in the Open Knowledge Format, and Kiso turns it into a site readable by both humans and AI agents at the same time. → Takes an OKF bundle, just Markdown files with YAML frontmatter, no proprietary format, and builds a navigable static site with structured navigation → Every generated page links back to its original Markdown source, so nothing gets lost between what you wrote and what gets published → Auto-generates llms.txt and sitemap.xml on build, so the site is structured for AI crawling from the start, not added on later → Ships a check command that validates your Markdown against the OKF spec before you publish, catching structural errors early → Drops into a GitHub Action, so pushing a commit can automatically rebuild and redeploy your knowledge base to GitHub Pages or any static host The idea behind OKF, published by Google Cloud’s Data team in June 2026, is that a knowledge base shouldn’t be locked into one vendor’s catalog or SDK. It’s just Markdown files in ***, readable by any agent that supports the spec. Kiso is an independently built tool, not a Google product, that turns that idea into an actual publishing engine.
-
Kshitij Mishra | AI & Tech (@DAIEvolutionHub) reportedA NEW OPEN-SOURCE TOOL JUST MADE VIDEO DOWNLOADING RIDICULOUSLY SIMPLE. It's called ReClip. A self-hosted GitHub project that lets you download videos (or audio) from 1,000+ websites without ads, trackers, or subscriptions. Just paste a URL and you're done. It supports platforms like YouTube, TikTok, Instagram, X, and hundreds more. What you get: ↳ Download videos as MP4 or extract audio as MP3 ↳ Choose the video quality before downloading ↳ Queue multiple links with batch downloads ↳ Clean browser-based interface ↳ Lightweight self-hosted deployment ↳ No login, no limits, no hidden catches The growth has been impressive too: 📈 1,400+ GitHub stars in just 9 days 📦 239+ forks already That traction isn't surprising. For years, people have had to deal with download sites packed with ads, pop-ups, fake buttons, and privacy concerns. ReClip takes a completely different approach. You host it yourself. Your files stay on your machine. Your data stays yours. No premium paywall. No data collection. No endless upsells. Just a lightweight open-source project released under the MIT License and built to do one job well. Free. Open source. And likely to become a favorite for anyone who downloads media regularly. 👇
-
tokenbrice (@TokenBrice) reportedNot a merge. But the codex repo security scan feature that as far as I know can only be accessed on the website... It would be neat if it was more integrated with the regular CLI or codex app. Right now in CLI, the agents are not even aware of it. So I cannot ask him like, hey, check all the issues that we have in security scan (as I I can with github security flag for instance_ and tell me what is most critical or try to sort them, etc. I have to process thes manually using my hands, clicking one by one. What is it this? 1999?
-
DeFAI Scope (@defaiscope) reportedGPT-5.5 holds at zero percent reward hacking across every effort level on DeepSWE, while every other model's hacking climbs alongside its capability. That looked like clean design until the same model hit a different benchmark. ➥ DeepSWE, fix a GitHub issue: GPT-5.5 at 0%, Fable 5 past 9% ➥ SWE-Marathon, open-ended missions like rewriting a C compiler in Rust: GPT-5.5 at 26.5%, the highest of anything tested A patch has a narrow definition of done. A mission doesn't, and GPT-5.5 takes advantage of that gap more than any other model.
-
Andreas (@AndJakobsson) reportedI did set up a kind of Obsidian second brain structure for my notes with my Hermes agent directly on my VPS. Now I wonder if it is not just better to have the whole thing directly in markdown files on GitHub. I could have agents updating it directly and between projects, issues and discussions, if properly structured it will probably work really well. Is anyone else doing this?
-
Greg Mushen (@gregmushen) reported@Macrike @Brady_H @hubermanlab I would be interested in reading those papers. I know there have been recent modeling papers from Stanford and I believe he may be referring to the **** paper since he shared Figure 3 of that study if I recall correctly last year. In that paper, both permanent DST and ST resulted in better outcomes than switching for obesity and stroke. But if you compared ST and DST the differences for either were tiny. Like 0.27% for obesity and 0.02% for stroke. But if you look at the confidence intervals, they are quite wide. But there's no confidence interval for DST - ST and no p-value. So it's impossible to tell if it's significant or not. Also, that paper was recently corrected in April of this year. That is a substantial correction, and what the correction does not say is if it impacted these numbers or not. They do have everything checked into Github, so I guess if you were curious, you could find the commit that fixed it and test on the data set pre/post. This reminds me of this intra time zone study I remember reading a few years back. At first, the paper thought they saw more negative outcomes for people in the Western edge of timezones, so people glommed on to that conclusion. However, a few years later they found an error in the data set, and once they corrected that, there was no difference. This is classic modeling type stuff. It happens to everyone who tries to model anything. But even then, these are just models. They estimate what may happen and have to make assumptions to do so, such as assuming that bedtimes are fixed from 10pm-7am. Do people actually behave this way? Probably not. In fact, that would have been a really great addition to the model...a sensitivity analysis on the factors they assumed were fixed. That would make the model much more robust actually. That and time zone comparison with a p value would make the paper mucho stronger. But that's why I think Steponenaite et al 2026 is a great paper because it doesn't lean on mechanisms or models. It's purely epidemiological. And while that has its obvious downsides, if you're not seeing strong signal across 157 papers in 36 countries, that in itself is a strong signal. It mirrors what we see in this modeling paper as well. There are big advantages to sticking to a permanent time zone, but there doesn't seem to be strong evidence for one vs. the other.
-
Pyro (@0x3b33) reported> I find a bug > Open a GitHub private submission > A week passes, doesn't get checked > Send an email to the provided security email address > error "email address does not exist" > Open a discord ticket > No one checks it > Ask in chat what to do if I find a bug > No one replies > DM the project devs > No one sees it > Tag the protocol team > Bot deletes the msg and warns me (because I tagged someone) No wonder black hats are hacking so many projects
-
piyush (@piyushyrr) reportedall you need to build a million-dollar saas: - find a painful problem on reddit, x, github issues, or hacker news - validate demand with gemini/chatgpt deep research - spy on competitors with perplexity - design the ui with v0/lovable/figma - build the mvp with cursor + claude/codegen - ship on vercel/fly.io - get your first users from x, reddit, and product hunt - iterate based on user feedback - repeat until people start paying the barrier to building has never been lower. the barrier to execution has never been higher. (this is a gpt slop)
-
SquaredCube (@SquaredCubeRBX) reportedthe one thing I do not like to hear is that programming is an artform so AI is bad, and adjacently: - AI is stealing from programmers (you put the code on github yourself for free public use, usually under MIT/Apache 2.0?) - AI code is soulless slop (it can be slop, but it 99% of the times is really freaking good, just be aware of what your agent is doing) Problem solving and critical thinking are art forms, NOT writing lines of boilerplate, and most people (not all) who say this are the ones who only know how to write said boilerplate. The people who are actually passionate about making cool **** embrace AI in the right ways. A lot of the other complaints are really just abt environmental impact, etc, and a lot of them just are really overexaggerated (I live close to a datacenter, just a few miles away)
-
Yasir Ai (@AiwithYasir) reported🚨 $276 A YEAR ADOBE'S SUBSCRIPTION IS DEAD: MEET PHOTO GIMP, THE FREE KILLER! A Brazilian YouTuber has just delivered a decisive blow to Adobe’s Photoshop subscription model. It is called PhotoGIMP: a free, open-source patch (GPL-3.0) that transforms GIMP into an almost identical copy of Photoshop. Same interface, same panels, same keyboard shortcuts, and significantly more canvas space. Your hands already know exactly how to use it — no new learning curve required. Why is it going viral? > $0 instead of $276 per year > No Adobe account or login required > Everything saved locally on your PC (nothing in the cloud) > Fully compatible with Windows, macOS, and Linux > Complete uninstall by simply deleting one folder (no traces left behind) Installation is ridiculously simple: copy nine files and you’re done. It already has over 8.8k stars on GitHub and community translations. 100% free for both personal and commercial use. (Link in comments)