GitLab

Why GitLab.com is changing its CDN provider to Cloudflare March 28

Jan 16, 2020David Smith
Why GitLab.com is changing its CDN provider to Cloudflare March 28
SummaryAI, from the source post

GitLab.com is changing its CDN provider from Fastly to Cloudflare to improve availability, security, and performance. This involves integrating Cloudflare's WAF, Spectrum, and Argo. The change requires handling both HTTP and SSH traffic (ports 22 and 443) and necessitates firewall reconfiguration for users whitelisting GitLab.com IPs. Custom runner images or private runners with DNS or SSL certificate caching may also be affected.

More from the Performance Optimization trail