Cloudflare network has low ping, but not WARP

Hello,

I’ve been having some weird issues relating to WARP and peering. I’m from Iraq and our Internet infrastructure and peering agreements is a very hot mess to say the least. EarthLink (AS50710) and Asiacell (AS51684) Both peer to Cloudflare fine and even reach the BGW datacenter, however the WARP service ends up exiting the country and in the process I end up with really high latency. I basically end up connecting to IST (Istanbul, Turkey) and the peering between Iraq and Turkey is also horrendous, I get better ping times to Central EU!

So what’s the problem? Is WARP simply not available in BGW? Is it an issue on Cloudflare’s side or is it an ISP problem? I’ve tried contacting the ISP multiple times up to no avail. It’s either no response or I get the usual “Turn the router off and on again”. Assistance would be great, thank you. I’m gonna attach necessary diagnostic info below

Trace without WARP

fl=359f2
h=www.cloudflare.com
ip=82.199.217.37
ts=1658900509.639
visit_scheme=https
uag=Mozilla/5.0 (X11; Linux x86_64; rv:103.0) Gecko/20100101 Firefox/103.0
colo=BGW
http=http/2
loc=IQ
tls=TLSv1.3
sni=plaintext
warp=off
gateway=off

Trace with WARP

fl=336f74
h=www.cloudflare.com
ip=104.28.215.122
ts=1658900556.97
visit_scheme=https
uag=Mozilla/5.0 (X11; Linux x86_64; rv:103.0) Gecko/20100101 Firefox/103.0
colo=IST
http=http/2
loc=IQ
tls=TLSv1.3
sni=plaintext
warp=plus
gateway=off

ICMP ping to cloudflare.com without WARP

--- cloudflare.com ping statistics ---
100 packets transmitted, 100 received, 0% packet loss, time 9957ms
rtt min/avg/max/mdev = 1.878/2.418/6.119/0.520 ms

ICMP ping to cloudflare.com with WARP

--- cloudflare.com ping statistics ---
100 packets transmitted, 100 received, 0% packet loss, time 9961ms
rtt min/avg/max/mdev = 107.031/114.439/125.009/3.217 ms, pipe 2

traceroute to cloudflare.com without WARP

traceroute to cloudflare.com (104.16.133.229), 30 hops max, 60 byte packets
 1  _gateway (192.168.1.1)  0.261 ms  0.254 ms  0.297 ms
 2  10.10.10.1 (10.10.10.1)  1.806 ms  1.850 ms  1.846 ms
 3  192.168.151.133 (192.168.151.133)  2.362 ms  2.407 ms  2.404 ms
 4  192.168.251.142 (192.168.251.142)  2.343 ms  2.340 ms  1.838 ms
 5  192.168.150.1 (192.168.150.1)  2.388 ms  2.335 ms  2.379 ms
 6  10.1.52.69 (10.1.52.69)  2.578 ms  2.346 ms 10.1.52.101 (10.1.52.101)  2.295 ms
 7  10.1.53.134 (10.1.53.134)  2.514 ms 10.1.53.130 (10.1.53.130)  2.432 ms  2.359 ms
 8  10.1.3.92 (10.1.3.92)  2.395 ms  2.480 ms 10.1.3.83 (10.1.3.83)  2.335 ms
 9  10.1.4.202 (10.1.4.202)  3.163 ms 10.1.4.198 (10.1.4.198)  3.156 ms 10.1.4.202 (10.1.4.202)  3.589 ms
10  37.238.254.22 (37.238.254.22)  2.339 ms  2.418 ms  2.270 ms
11  104.16.133.229 (104.16.133.229)  2.261 ms  2.407 ms  2.483 ms

traceroute to engage.cloudflareclient.com without WARP

traceroute to engage.cloudflareclient.com (162.159.192.1), 30 hops max, 60 byte packets
 1  _gateway (192.168.1.1)  0.220 ms  0.368 ms  0.363 ms
 2  10.10.10.1 (10.10.10.1)  1.091 ms  1.133 ms  1.080 ms
 3  192.168.151.133 (192.168.151.133)  1.589 ms  1.584 ms  1.626 ms
 4  192.168.251.142 (192.168.251.142)  1.551 ms  1.593 ms  1.860 ms
 5  192.168.150.1 (192.168.150.1)  2.036 ms 192.168.150.65 (192.168.150.65)  2.028 ms 192.168.150.1 (192.168.150.1)  2.257 ms
 6  10.1.52.49 (10.1.52.49)  2.252 ms  2.069 ms 10.1.52.81 (10.1.52.81)  2.114 ms
 7  10.1.53.13 (10.1.53.13)  3.710 ms 10.1.53.21 (10.1.53.21)  2.360 ms  2.814 ms
 8  10.1.26.62 (10.1.26.62)  2.951 ms  3.152 ms  2.924 ms
 9  * * *
10  37.236.249.50 (37.236.249.50)  6.648 ms  6.640 ms  6.682 ms
11  37.236.240.18 (37.236.240.18)  8.864 ms 37.236.240.26 (37.236.240.26)  6.622 ms  6.618 ms
12  167.160.20.244 (167.160.20.244)  73.864 ms 178.86.50.8 (178.86.50.8)  84.647 ms  84.774 ms
13  * * sfia-b3-link.ip.twelve99.net (213.248.73.76)  75.178 ms
14  linx-lon1.as13335.net (195.66.225.179)  91.278 ms cloudflare-svc079338-ic369087.ip.twelve99-cust.net (62.115.162.27)  81.300 ms  81.292 ms
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

Note: All diagnostic info were pulled from EarthLink however Asiacell yields the same except 1.1.1.1 which returns 12ms instead of EarthLink’s 95ms. I’m happy to supply more info if needed.

Note 2: I’m pretty certain EarthLink blocks WARP however this is irrelevant to the problem since Asiacell experiences the same latency issue

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.