Eugene Yan, an applied machine-learning engineer and writer, says he moved his site back from Netlify to GitHub Pages after recurring DNS-server issues. He reports that those failures affected more than availability: they led to email delivery problems and security concerns. Netlify's free tier also limited monthly build minutes, another practical constraint for a frequently updated technical blog.
The post is best read as an infrastructure lesson rather than an ML result. For researchers who publish models and notes, the choice of static-hosting provider can introduce operational risk. Yan's response was to simplify the stack by returning to GitHub Pages.
Because this is a single first-person source, there are no differing accounts to compare. The decision reflects one author's experience, not a benchmark of hosting services. Readers with similar priorities—reliability, email integrity, and no surprise build limits—may find the rationale useful.