Twitter.com quietly drops Cloudflare for Fastly

Buried in a day of roughly 14,224 DNS changes across 20+ million tracked domains, one entry stands out simply because of whose name is on it.

Twitter.com leaves Cloudflare's network

twitter.com flipped its hosting from Cloudflare (AS13335) to Fastly (AS54113), with the hosting classification changing from "Cloudflare (cdn)" to "Fastly (cdn)". Both are CDNs, so this isn't a "site went down" moment — it's a routing/edge-provider swap, the kind of move that usually happens behind a load balancer without anyone outside the network team noticing. Whether it's a permanent shift or a partial rebalancing, we'll only know from tomorrow's data.

Three unrelated domains, one ASN move

www.milyaar.net, www.healthdecoded.co, and www.321go.club all made the identical jump from AS30058 to AS16276 within a couple of hours of each other. Same source network, same destination, same day — that's the fingerprint of a hosting reseller or platform migrating a batch of customer sites to new infrastructure, rather than three site owners independently deciding to switch providers at once.

Elsewhere, amershams.com and its www subdomain moved from AS22612 onto Cloudflare (AS13335), swapping Namecheap-hosting nameservers for Cloudflare's drew.ns.cloudflare.com / tessa.ns.cloudflare.com, and its mail from jellyfish.systems boxes over to mx1.krystal.uk / mx2.krystal.uk — a clean full-stack migration: DNS, hosting, and mail all changing together.

A cluster of domains going dark on security records

A handful of sites quietly pulled their CAA records (which restrict who's allowed to issue TLS certs for them) alongside other teardown signals — often a sign of a domain being parked, sold, or wound down rather than an active security downgrade:

• www.electricians.pro dropped its letsencrypt.org CAA entry and its mail record, while the bare domain also lost its parking nameservers (ns1.parkingcrew.net) and a locked-down SPF (-all).
• 07711.com and its www host both dropped the same letsencrypt.org CAA issue record, their nameservers (ns1.ibspark.com, ns2.ibspark.com), and an SPF -all record.
• www.solshaker.org similarly removed its CAA and SPF -all records.
• shreeambicaalloys.com lost its CNAME, mail record, and its ns1.9888788888.com / ns2.9888788888.com nameservers in one sweep.

None of these show a new CAA record replacing the old one — the config is just being stripped, which usually means "domain being decommissioned" rather than "cert provider switch." Worth a glance if any of these are on your watchlist.