Cloudflare DNS is not resolving facebook and instagram to the nearest datacenter for clients in HK.
1.1.1.1 is routing Facebook/Instagram to Singapore instead of the Hong Kong local server.
It’s causing significant performance degrade for browsing FB/IG especially at peak hours.
ping www.instagram.com
PING z-p42-instagram.c10r.instagram.com (157.240.235.174) 56(84) bytes of data.
64 bytes from instagram-p42-shv-04-sin6.fbcdn.net (157.240.235.174): icmp_seq=1 ttl=52 time=34.2 ms
64 bytes from instagram-p42-shv-04-sin6.fbcdn.net (157.240.235.174): icmp_seq=2 ttl=52 time=33.7 ms
64 bytes from instagram-p42-shv-04-sin6.fbcdn.net (157.240.235.174): icmp_seq=3 ttl=52 time=33.6 ms
ping www.facebook.com
PING star-mini.c10r.facebook.com (157.240.235.35) 56(84) bytes of data.
64 bytes from edge-star-mini-shv-04-sin6.facebook.com (157.240.235.35): icmp_seq=1 ttl=52 time=35.0 ms
64 bytes from edge-star-mini-shv-04-sin6.facebook.com (157.240.235.35): icmp_seq=2 ttl=52 time=33.5 ms
64 bytes from edge-star-mini-shv-04-sin6.facebook.com (157.240.235.35): icmp_seq=3 ttl=52 time=33.7 ms
Using Google DNS 8.8.8.8 as comparison:
Resolved to local breakout
ping www.facebook.com
PING star-mini.c10r.facebook.com (31.13.77.35) 56(84) bytes of data.
64 bytes from edge-star-mini-shv-01-hkt1.facebook.com (31.13.77.35): icmp_seq=1 ttl=56 time=1.29 ms
64 bytes from edge-star-mini-shv-01-hkt1.facebook.com (31.13.77.35): icmp_seq=2 ttl=56 time=1.15 ms
64 bytes from edge-star-mini-shv-01-hkt1.facebook.com (31.13.77.35): icmp_seq=3 ttl=56 time=1.31 ms
ping www.instagram.com
PING z-p42-instagram.c10r.instagram.com (31.13.77.174) 56(84) bytes of data.
64 bytes from instagram-p42-shv-01-hkt1.fbcdn.net (31.13.77.174): icmp_seq=1 ttl=56 time=1.13 ms
64 bytes from instagram-p42-shv-01-hkt1.fbcdn.net (31.13.77.174): icmp_seq=2 ttl=56 time=1.24 ms
64 bytes from instagram-p42-shv-01-hkt1.fbcdn.net (31.13.77.174): icmp_seq=3 ttl=56 time=1.08 ms