Feb 28 2021, 10:48 PM
QUOTE(go626201 @ Feb 28 2021, 10:10 PM)
Actually from my experience this should not be tm problem,because cloudflare site dc route is not done by tm, CloudFlare distribute it.
Normally peak time will always route to further dc.
But for Fastly,that 70% is TM problem,i reported to Fastly before about 1 years ago.
But Fastly team can contact TM to temporary fix it.(for weeks)
Edit:
If someone who has problem with Fastly CDN, please enter this site http://www.fastly-debug.com/
and after completed debug,the top of the site will show a long code just sent it to Fastly team,they will fix it.
Over here in East Malaysia using Cloudflare DNS (connected to JHB PoP) on Unifi Home, legal streaming sites using Akamai CDN is totally unusable at night. Infinite buffering/loading until it errors out. Pinging the domains serving the videos results in packet loss. IPv6 is enabled but Akamai CDN for the videos seem to only use IPv4.Normally peak time will always route to further dc.
But for Fastly,that 70% is TM problem,i reported to Fastly before about 1 years ago.
But Fastly team can contact TM to temporary fix it.(for weeks)
Edit:
If someone who has problem with Fastly CDN, please enter this site http://www.fastly-debug.com/
and after completed debug,the top of the site will show a long code just sent it to Fastly team,they will fix it.
CODE
Pinging a1416.w39.akamai.net [184.28.229.8] with 32 bytes of data:
Reply from 184.28.229.8: bytes=32 time=321ms TTL=55
Request timed out.
Reply from 184.28.229.8: bytes=32 time=319ms TTL=55
Reply from 184.28.229.8: bytes=32 time=320ms TTL=55
Reply from 184.28.229.8: bytes=32 time=320ms TTL=55
Reply from 184.28.229.8: bytes=32 time=320ms TTL=55
Request timed out.
Request timed out.
Request timed out.
Reply from 184.28.229.8: bytes=32 time=319ms TTL=55
Ping statistics for 184.28.229.8:
Packets: Sent = 10, Received = 6, Lost = 4 (40% loss),
Approximate round trip times in milli-seconds:
Minimum = 319ms, Maximum = 321ms, Average = 319ms
Reply from 184.28.229.8: bytes=32 time=321ms TTL=55
Request timed out.
Reply from 184.28.229.8: bytes=32 time=319ms TTL=55
Reply from 184.28.229.8: bytes=32 time=320ms TTL=55
Reply from 184.28.229.8: bytes=32 time=320ms TTL=55
Reply from 184.28.229.8: bytes=32 time=320ms TTL=55
Request timed out.
Request timed out.
Request timed out.
Reply from 184.28.229.8: bytes=32 time=319ms TTL=55
Ping statistics for 184.28.229.8:
Packets: Sent = 10, Received = 6, Lost = 4 (40% loss),
Approximate round trip times in milli-seconds:
Minimum = 319ms, Maximum = 321ms, Average = 319ms
CODE
Pinging a922.w10.akamai.net [23.46.16.143] with 32 bytes of data:
Reply from 23.46.16.143: bytes=32 time=326ms TTL=55
Reply from 23.46.16.143: bytes=32 time=323ms TTL=55
Reply from 23.46.16.143: bytes=32 time=325ms TTL=55
Request timed out.
Reply from 23.46.16.143: bytes=32 time=324ms TTL=55
Reply from 23.46.16.143: bytes=32 time=327ms TTL=55
Reply from 23.46.16.143: bytes=32 time=325ms TTL=55
Reply from 23.46.16.143: bytes=32 time=325ms TTL=55
Request timed out.
Reply from 23.46.16.143: bytes=32 time=323ms TTL=55
Ping statistics for 23.46.16.143:
Packets: Sent = 10, Received = 8, Lost = 2 (20% loss),
Approximate round trip times in milli-seconds:
Minimum = 323ms, Maximum = 327ms, Average = 324ms
Reply from 23.46.16.143: bytes=32 time=326ms TTL=55
Reply from 23.46.16.143: bytes=32 time=323ms TTL=55
Reply from 23.46.16.143: bytes=32 time=325ms TTL=55
Request timed out.
Reply from 23.46.16.143: bytes=32 time=324ms TTL=55
Reply from 23.46.16.143: bytes=32 time=327ms TTL=55
Reply from 23.46.16.143: bytes=32 time=325ms TTL=55
Reply from 23.46.16.143: bytes=32 time=325ms TTL=55
Request timed out.
Reply from 23.46.16.143: bytes=32 time=323ms TTL=55
Ping statistics for 23.46.16.143:
Packets: Sent = 10, Received = 8, Lost = 2 (20% loss),
Approximate round trip times in milli-seconds:
Minimum = 323ms, Maximum = 327ms, Average = 324ms
Addon: Looking up the IPs involved points to Singapore. So even connection to Singapore is 300ms+ with packet loss!
This post has been edited by AV_2018: Feb 28 2021, 10:50 PM
Quote
looking up the Akamai domains with TM and Google DNS does give totally different IPs compared to Cloudflare. I'm aware Cloudflare doesn't support EDNS but thought it usually doesn't matter much since Cloudflare DNS is in Malaysia so other CDNs DNS that are queried by Cloudflare will know that the query is from Malaysia.
0.0275sec
0.46
7 queries
GZIP Disabled