Singapore - Singtel 89ms

Zero Trust 1.1.1.1
,
1

While 8.8.8.8 is 2ms, 1.1.1.1 is 89ms and intermittent packet loss.

Country: SG
ISP: SingTel
Source IP: 203.125.XXX.XXX

Tracing route to one.one.one.one [1.1.1.1]
over a maximum of 30 hops:

1 * * * Request timed out.
2 <1 ms <1 ms <1 ms 132.1.3.231
3 * * * Request timed out.
4 <1 ms <1 ms <1 ms 203.125.68.129
5 1 ms 1 ms 1 ms 118.201.77.30
6 7 ms 7 ms 7 ms 118.201.77.29
7 1 ms 1 ms 1 ms 165.21.12.86
8 89 ms 90 ms 88 ms ip-202-147-32-136.asianetcom.net [202.147.32.136]
9 * 91 ms 94 ms unknown.telstraglobal.net [210.176.138.22]
10 90 ms 89 ms 89 ms one.one.one.one [1.1.1.1]

Trace complete.

2
3

C:\Users\Admin>nslookup example.com 1.1.1.1
DNS request timed out.
timeout was 2 seconds.
Server: UnKnown
Address: 1.1.1.1

Non-authoritative answer:
DNS request timed out.
timeout was 2 seconds.
Name: example.com
Address: 93.184.216.34

C:\Users\Admin>nslookup example.com 1.0.0.1
Server: one.one.one.one
Address: 1.0.0.1

Non-authoritative answer:
Name: example.com
Addresses: 2606:2800:220:1:248:1893:25c8:1946
93.184.216.34

C:\Users\Admin>nslookup example.com 8.8.8.8
Server: google-public-dns-a.google.com
Address: 8.8.8.8

Non-authoritative answer:
Name: example.com
Addresses: 2606:2800:220:1:248:1893:25c8:1946
93.184.216.34

C:\Users\Admin>nslookup -class=chaos -type=txt id.server 1.1.1.1
Server: one.one.one.one
Address: 1.1.1.1

Non-authoritative answer:
id.server text =

    "SIN"

C:\Users\Admin>nslookup -class=chaos -type=txt id.server 1.0.0.1
Server: one.one.one.one
Address: 1.0.0.1

Non-authoritative answer:
id.server text =

    "SIN"

C:\Users\Admin>nslookup -type=txt whoami.Cloudflare.com ns3.Cloudflare.com
DNS request timed out.
timeout was 2 seconds.
Server: UnKnown
Address: 162.159.7.226

DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out

C:\Users\Admin>tracert 1.1.1.1

Tracing route to one.one.one.one [1.1.1.1]
over a maximum of 30 hops:

1 * * * Request timed out.
2 <1 ms <1 ms <1 ms 132.1.3.231
3 * * * Request timed out.
4 1 ms <1 ms <1 ms 203.125.68.129
5 1 ms 2 ms 1 ms 118.201.77.30
6 2 ms 2 ms 2 ms 118.201.77.29
7 1 ms 1 ms 1 ms 165.21.12.86
8 92 ms 89 ms 88 ms ip-202-147-32-136.asianetcom.net [202.147.32.136]
9 89 ms 89 ms * unknown.telstraglobal.net [210.176.138.22]
10 87 ms * 88 ms one.one.one.one [1.1.1.1]

Trace complete.

C:\Users\Admin>tracert 1.0.0.1

Tracing route to one.one.one.one [1.0.0.1]
over a maximum of 30 hops:

1 * * * Request timed out.
2 <1 ms <1 ms <1 ms 132.1.3.231
3 * * * Request timed out.
4 <1 ms <1 ms <1 ms 203.125.68.129
5 1 ms 1 ms 1 ms 118.201.77.30
6 8 ms 8 ms 7 ms 118.201.77.29
7 36 ms 2 ms 1 ms 165.21.12.86
8 86 ms 87 ms * ip-202-147-32-136.asianetcom.net [202.147.32.136]
9 90 ms * 95 ms unknown.telstraglobal.net [210.176.138.22]
10 87 ms 88 ms 87 ms one.one.one.one [1.0.0.1]

Trace complete.

C:\Users\Admin>nslookup -class=chaos -type=txt id.server 1.1.1.1
Server: one.one.one.one
Address: 1.1.1.1

Non-authoritative answer:
id.server text =

    "SIN"

C:\Users\Admin>nslookup -class=chaos -type=txt id.server 1.0.0.1
Server: one.one.one.one
Address: 1.0.0.1

Non-authoritative answer:
id.server text =

    "SIN"

C:\Users\Admin>nslookup -vc -class=chaos -type=txt id.server 1.1.1.1
Server: one.one.one.one
Address: 1.1.1.1

Non-authoritative answer:
id.server text =

    "SIN"

C:\Users\Admin>nslookup -vc -class=chaos -type=txt id.server 1.0.0.1
Server: one.one.one.one
Address: 1.0.0.1

Non-authoritative answer:
id.server text =

    "SIN"
4

You are going to the Singaporean data centre all right. The issue as far as I seem to be able to tell appears to be your ISP’s routing.

Your ISP is Singnet, right? They appear to be routing this particular request via some unorthodox route, notice the sudden jump to 90 milliseconds on the eighth hop.

I am afraid you’d have to contact your ISP in this regard.

5

Singtel user here, having the same issue.
High latency and packet loss on both 1.1.1.1 and 1.0.0.1
Singtel route those packet thru Malaysia, this is abnormal.
Have you reported the issue to Singtel yet?

6

Singtel won’t respond to consumer customer. Although I’m using corporate account but I am not the contact person in their system.

Yes I have verified this isn’t affecting M1.

7

I guess changing ISP might be the best option in response to their disregard to their customers.

8

It seems 1.1.1.1 is back to normal on Singtel. The tracepath is the same, likely at Malaysia has fixed the issue on their end.
Ping latency back to normal. Thank you.

9

I can attest the same.
ping is back to sub 2ms.