There seems to be a route issue, but whether that was deliberately done to go around some issue I dunno.
C:\>tracert 8.8.8.8
Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms router.asus.com [192.168.x.1]
2 2 ms 2 ms 1 ms fnetx-fxx-access.vqbn.com [x.x.x.x]
3 161 ms 161 ms 161 ms LosAngeles2.vqbn.com [132.147.112.81]
4 162 ms 161 ms 161 ms any2ix.coresite.com [206.72.210.41]
5 162 ms 162 ms 162 ms 209.85.250.97
6 162 ms 161 ms 162 ms google-public-dns-a.google.com [8.8.8.8]
Trace complete.
C:\>tracert google.com.sg
Tracing route to google.com.sg [74.125.200.94]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms router.asus.com [192.168.x.1]
2 2 ms 2 ms 1 ms fnetx-fxx-access.vqbn.com [x.x.x.x]
3 2 ms 1 ms 1 ms Singapore1.vqbn.com [132.147.112.65]
4 2 ms 6 ms 2 ms 203.208.190.241
5 174 ms 176 ms 174 ms 72.14.210.117
6 174 ms 174 ms 174 ms 209.85.245.95
7 174 ms 174 ms 176 ms 216.239.40.224
8 183 ms 175 ms 175 ms 64.233.174.109
9 * * * Request timed out.
10 174 ms 174 ms 174 ms sa-in-f94.1e100.net [74.125.200.94]
Trace complete.