1.1.1.1 - High latency from BKK


#1

Hi,

1.1.1.1 is routing to Singapore from Bangkok instead of BKK

Tracing route to 1.1.1.1 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  10.1.1.1
  2     2 ms     2 ms     2 ms  10.169.17.142
  3     2 ms     1 ms     3 ms  10.169.17.149
  4     1 ms     1 ms     1 ms  171.102.247.231
  5     3 ms     3 ms     2 ms  171.102.247.230
  6    48 ms    22 ms     6 ms  171.102.250.1
  7     3 ms     3 ms     3 ms  171.102.254.227
  8     3 ms    10 ms    13 ms  210.86.143.74
  9     5 ms     3 ms     3 ms  122.144.25.148
 10    31 ms    31 ms    31 ms  113.21.245.27
 11    42 ms    48 ms    32 ms  27.111.228.132
 12    29 ms    29 ms    30 ms  1.1.1.1

Trace complete.

Tracing route to www.cloudflare.com [198.41.214.162]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.1.1.1
  2     2 ms    10 ms     2 ms  10.169.77.14
  3     2 ms     1 ms     2 ms  10.169.17.165
  4    17 ms     2 ms     2 ms  171.102.247.231
  5     2 ms     2 ms     2 ms  171.102.247.210
  6     2 ms     2 ms     3 ms  171.102.250.1
  7     4 ms     5 ms     3 ms  171.102.250.129
  8     4 ms     7 ms     7 ms  122.144.25.28
  9     2 ms     2 ms     2 ms  113.21.245.111
 10     3 ms     3 ms     3 ms  198.41.214.162

Trace complete.

Thank you


#2

Hi @triamudomatschool,

Thank you for the report. Would you mind also including a traceroute for 1.0.0.1? Want to see if it is any better and/or if our network team should investigate both at once. Thanks!

Also if you can run this it would be much appreciated:

$ dig +short CHAOS TXT id.server @1.1.1.1

$ dig +short CHAOS TXT id.server @1.0.0.1


#3

@cscharff

Tracing route to 1.0.0.1 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 10.1.1.1
2 2 ms 2 ms 2 ms 10.169.17.146
3 2 ms 1 ms 2 ms 10.169.77.9
4 2 ms 2 ms 1 ms 171.102.247.231
5 3 ms 2 ms 2 ms 171.102.247.30
6 2 ms 2 ms 2 ms 171.102.250.1
7 3 ms 3 ms 3 ms 171.102.254.227
8 3 ms 3 ms 3 ms 61.91.213.130
9 7 ms 7 ms 7 ms 113.21.242.40
10 29 ms 28 ms 28 ms 113.21.241.193
11 31 ms 31 ms 31 ms 27.111.228.132
12 29 ms 28 ms 29 ms 1.0.0.1

Trace complete.

dig +short CHAOS TXT id.server @1.1.1.1
“sin02”

dig +short CHAOS TXT id.server @1.1.1.1
“sin02”

Thanks!


#4

Thanks! I’ve passed along the info to our networking team.


#5

@ros The issue with True should be resolved. Please retry. Besides, we are checking with other Thai provider too.


#6

@Frankie.H

Thank you very much! I can confirm that the issue with TRUE ISP has been resolved.

Pinging 1.1.1.1 with 32 bytes of data:
Reply from 1.1.1.1: bytes=32 time=3ms TTL=56
Reply from 1.1.1.1: bytes=32 time=3ms TTL=56
Reply from 1.1.1.1: bytes=32 time=2ms TTL=56
Reply from 1.1.1.1: bytes=32 time=2ms TTL=56

Ping statistics for 1.1.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 3ms, Average = 2ms

Pinging 1.0.0.1 with 32 bytes of data:
Reply from 1.0.0.1: bytes=32 time=2ms TTL=56
Reply from 1.0.0.1: bytes=32 time=2ms TTL=56
Reply from 1.0.0.1: bytes=32 time=2ms TTL=56
Reply from 1.0.0.1: bytes=32 time=2ms TTL=56

Ping statistics for 1.0.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 2ms, Average = 2ms


#7

Hi @Frankie.H

Using hotel wifi, routing via AS38794 in Thailand routes to CF ‘SIN’ instead of ‘BKK’

fl=35f153
h=1.1.1.1
ip=115.31.190.6
ts=1524840660.27
visit_scheme=https
uag=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.181 Safari/537.36 OPR/52.0.2871.64
colo=SIN
spdy=h2
http=h2
loc=JP

Tracing route to 1dot1dot1dot1.cloudflare-dns.com [1.0.0.1]
over a maximum of 30 hops:

1 5 ms 2 ms 13 ms [172.16.0.1]
2 24 ms 16 ms 39 ms [192.168.254.99]
3 2 ms 2 ms 23 ms 115.31.190.1
4 47 ms 2 ms 53 ms 10.222.41.73
5 47 ms 27 ms 18 ms 10.101.41.73
6 7 ms 25 ms 37 ms 10.101.41.74
7 23 ms 13 ms 12 ms 117.121.208.117
8 40 ms 15 ms 19 ms bbconnect-net164-1.bbconnect.co.th [115.31.164.1]
9 91 ms 60 ms 100 ms 13335.sgw.equinix.com [27.111.228.132]
10 119 ms 70 ms 204 ms 1dot1dot1dot1.cloudflare-dns.com [1.0.0.1]

Trace complete.


#8

Hi @ros , unfortunately we don’t have deployment wit AS38794 in Thailand. We are trying to work something out with DTAC and AS38794 is using DTAC’s transit. So it might change in future.