Is it my ISP problem? thanks

Tracing route to servermatrix.com [69.56.222.40]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 19 ms 18 ms 23 ms atw-hhm3-2-rx.netvigator.com [203.198.32.254]
3 17 ms 17 ms 17 ms n219076078062.netvigator.com [219.76.78.62]
4 18 ms 17 ms 17 ms n219076096190.netvigator.com [219.76.96.190]
5 17 ms 17 ms 18 ms 218.102.21.205
6 17 ms 18 ms 18 ms unknown.net.reach.com [134.159.100.173]
7 18 ms 17 ms 18 ms unknown.net.reach.com [202.84.154.234]
8 18 ms 17 ms 18 ms i-15-0.hhtstcbr01.net.reach.com [202.84.154.69]

9 181 ms 180 ms 181 ms i-4-2.wil-core02.net.reach.com [202.84.143.105]

10 181 ms 181 ms 182 ms unknown.net.reach.com [202.84.251.166]
11 181 ms 181 ms 181 ms ge-6-21.car3.LosAngeles1.Level3.net [4.68.111.13
7]
12 182 ms 182 ms 213 ms ae-1-54.bbr2.LosAngeles1.Level3.net [4.68.102.97
]
13 212 ms 212 ms 213 ms ae-0-0.bbr1.Dallas1.Level3.net [64.159.1.109]
14 213 ms 214 ms 212 ms ge-1-1-55.car3.Dallas1.Level3.net [4.68.122.134]

15 431 ms 421 ms 421 ms 4.78.220.10
16 431 ms 424 ms 428 ms vl32.dsr02.dllstx3.theplanet.com [70.85.127.62]

17 422 ms 434 ms 423 ms dist-vlan22.dsr1-2.dllstx2.theplanet.com [70.85.
127.76]
18 436 ms 435 ms 428 ms car1-2-v2.dllstx2.theplanet.com [12.96.160.44]
19 422 ms 420 ms 430 ms www.servermatrix.com [69.56.222.40]

Trace complete.

Whats the return route to your server look like? Can you paste the results form 100 pings to us?

Ping to my server:

[--- 67.19.x.x ping statistics ---
100 packets transmitted, 97 received, 3% packet loss, time 99149ms
rtt min/avg/max/mdev = 398.189/414.298/427.860/6.306 ms, pipe 2

Ping 100 to SM

--- servermatrix.com ping statistics ---
100 packets transmitted, 100 received, 0% packet loss, time 99041ms
rtt min/avg/max/mdev = 398.284/426.354/440.655/7.606 ms, pipe 2



Traceroute:

Tracing route to x.x.com [67.19.x.x]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 20 ms 18 ms 17 ms atw-hhm3-2-rx.netvigator.com [203.198.32.254]
3 19 ms 19 ms 23 ms n219076109050.netvigator.com [219.76.109.50]
4 18 ms 17 ms 18 ms n219076096254.netvigator.com [219.76.96.254]
5 23 ms 18 ms 19 ms 218.102.21.210
6 19 ms 18 ms 18 ms unknown.net.reach.com [134.159.100.173]
7 18 ms 18 ms 18 ms unknown.net.reach.com [202.84.154.214]
8 18 ms 18 ms 19 ms i-4-0.hhtstcbr01.net.reach.com [202.84.154.5]
9 169 ms 168 ms 168 ms i-12-0.wil-core02.net.reach.com [202.84.143.113]

10 168 ms 168 ms 168 ms i-3-2.wil03.net.reach.com [202.84.251.170]
11 169 ms 169 ms 168 ms ge-6-21.car3.LosAngeles1.Level3.net [4.68.111.13
7]
12 168 ms 168 ms 168 ms ae-1-56.bbr2.LosAngeles1.Level3.net [4.68.102.16
1]
13 200 ms 205 ms 200 ms as-1-0.bbr2.Dallas1.Level3.net [64.159.0.245]
14 201 ms 201 ms 200 ms ge-1-2-52.car3.Dallas1.Level3.net [4.68.122.38]

15 412 ms 408 ms 411 ms 4.78.220.10
16 412 ms 416 ms 410 ms vl31.dsr01.dllstx3.theplanet.com [70.85.127.29]

17 408 ms 420 ms 408 ms dist-vlan41.dsr2-1.dllstx4.theplanet.com [70.85.
127.83]
18 418 ms 419 ms 424 ms 67.19.255.166
19 406 ms 410 ms 406 ms x.x.com [67.19.x.x]

Trace complete.

Hi Dragon,

I don't think it's your ISP. I had similar pings to yours a couple of days ago over the same route out of TP.

It appears to be a peering problem between GBLX and Reach

traceroute to 203.198.32.254 (203.198.32.254), 30 hops max, 38 byte packets

2 dist-vlan1.dsr1-1.dllstx5.theplanet.com (70.84.160.129) 0.381 ms 0.313 ms 0.374 ms
3 po51.dsr01.dllstx3.theplanet.com (70.85.127.105) 0.388 ms 0.552 ms 0.380 ms
4 ae0-0.ibr04.dllstx3.theplanet.com (70.85.127.4) 0.586 ms 0.562 ms 0.580 ms
5 ge-0-2-1.ar1.DAL2.gblx.net (64.213.176.149) 0.587 ms ge-4-3-0.ar1.DAL2.gblx.net (64.210.104.57) 0.660 ms 0.682 ms
[b] 6 reach.ar1.DAL2.gblx.net (208.51.134.238) 206.677 ms 217.593 ms 201.646 ms
7 i-2-0.wil-core02.net.reach.com (202.84.143.65) 246.357 ms 234.587 ms 243.416 ms
8 i-4-0.wwh-core01.net.reach.com (202.84.144.49) 378.135 ms 387.153 ms 388.744 ms
9 i-4-1.wwh-dist01.net.reach.com (202.84.155.6) 386.677 ms 394.392 ms 533.907 ms
10 i-1-0.wwh02.net.reach.com (202.84.155.17) 390.733 ms 381.083 ms 387.929 ms
11 unknown.net.reach.com (134.159.129.42) 391.925 ms 394.000 ms 390.566 ms
12 pcd507253.netvigator.com (218.102.39.253) 387.320 ms 378.188 ms 397.081 ms
13 n219076068211.netvigator.com (219.76.68.211) 397.142 ms 392.040 ms 383.442 ms


4.78.220.10 would be a TP router connection with Level 3. From there TP's BGP is routing back via GBLX.

I have already submitted a ticket and they reply.....

The issue appears to be caused by distance and the providers between your ISP and our network. The times increase a great deal while still inside Asia Pacific Network Information Centre (APNIC), the organization assigned the ip addresses in the first 8 hops.



what should i do now?

Slow pings and latency to the US is something that those of us in Asia just have to accept. The only real way to solve the solution would either be to :-

1) Relocate to the US or

2) Select a server slower to home

but my normal ping time should be around 200ms

dragon, I also believe that your pings should be around 200 ms

The issue appears to be caused by distance and the providers between your ISP and our network. The times increase a great deal while still inside Asia Pacific Network Information Centre (APNIC), the organization assigned the ip addresses in the first 8 hops.

IMHO that response is wrong and the problem is GBLX -> Reach peering in Dallas where the pings go from 0.580 ms to over 200 ms

5 ge-0-2-1.ar1.DAL2.gblx.net (64.213.176.149) 0.587 ms ge-4-3-0.ar1.DAL2.gblx.net (64.210.104.57) 0.660 ms 0.682 ms
6 reach.ar1.DAL2.gblx.net (208.51.134.238) 206.677 ms 217.593 ms 201.646 ms

From your ISP to Level 3 in Dallas the RTT is around 200 ms and it jumps to over 400 ms after leaving TP on the return route.

From a GBLX router in Phoenix we can do traces that bypass Dallas and the RTT's are around 164 msec to Netvigator. This tends to confirm that it's a peering problem in Dallas.
.
route-server.phx1>traceroute 203.198.32.254

Type escape sequence to abort.
Tracing the route to atw-hhm3-2-rx.netvigator.com (203.198.32.254)

1 ge4-1-0-226-1000M.ar4.PHX1.gblx.net (67.17.64.89) 0 msec 0 msec 0 msec
2 so1-0-0-2488M.ar1.LAX2.gblx.net (67.17.67.169) 12 msec 12 msec 12 msec
3 208.50.13.238 32 msec 32 msec 36 msec
4 i-11-2.wil-core02.net.reach.com (202.84.251.185) [AS 4637] 32 msec 36 msec 36 msec
5 i-4-0.wwh-core01.net.reach.com (202.84.144.49) [AS 4637] 172 msec 176 msec 176 msec
6 i-4-1.wwh-dist01.net.reach.com (202.84.155.6) [AS 4637] 176 msec 172 msec 176 msec
7 i-1-0.wwh02.net.reach.com (202.84.155.17) [AS 4637] 172 msec 176 msec 176 msec
8 unknown.net.reach.com (134.159.129.42) [AS 4637] 160 msec 164 msec 164 msec
9 pcd507253.netvigator.com (218.102.39.253) [AS 4760] 164 msec 164 msec 164 msec
10 n219076068211.netvigator.com (219.76.68.211) [AS 4760] 164 msec 160 msec 160 msec
11 * * *

Doodle, thanks

Looks like several of my customers are currently experiencing the same problem as you so I'm going to submit a ticket as well.

Reach peering in Dallas has been rather flaky for well over two years now.

I usually get a ping of about 170 from Tokyo, but recently it has been sometimes hitting around 380!

I think it was getting caught up at an Alternet hop?

Well once Cogent depeered with Level(3), then brought it back (and now talks of doing it again in November) I'll bet routing tables across the Internet are getting hosed.

Not a thing ThePlanet can do except monitor it so just cope with the fact its going to be slow, or like eddy2099 said. "Relocate to the US, or find a provider in your own country."

I did have this problem last week (GBLX/REACH connect router). It's better now. In fact, better then it's been in a long time:

Pinging matrixau.net [70.84.217.98] with 32 bytes of data:

Reply from 70.84.217.98: bytes=32 time=190ms TTL=46
Reply from 70.84.217.98: bytes=32 time=190ms TTL=46
Reply from 70.84.217.98: bytes=32 time=190ms TTL=46
Reply from 70.84.217.98: bytes=32 time=190ms TTL=46
Reply from 70.84.217.98: bytes=32 time=190ms TTL=46
Reply from 70.84.217.98: bytes=32 time=189ms TTL=46
Reply from 70.84.217.98: bytes=32 time=190ms TTL=46
Reply from 70.84.217.98: bytes=32 time=190ms TTL=46
Reply from 70.84.217.98: bytes=32 time=190ms TTL=46
Reply from 70.84.217.98: bytes=32 time=190ms TTL=46

Ping statistics for 70.84.217.98:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 189ms, Maximum = 190ms, Average = 189ms

From Sydney, Australia. .

Here's the differance. (Specifically hop 6 on each of these traceroutes).

Before:
traceroute to 60.225.xxx.xx (60.225.xxx.xx), 30 hops max, 38 byte packets
1 97.70-84-217.reverse.theplanet.com (70.84.217.97) 0.837 ms 0.935 ms 0.824
ms
2 dist-vlan2.dsr1-1.dllstx5.theplanet.com (70.84.160.161) 0.372 ms 0.659 ms
0.401 ms
3 po51.dsr01.dllstx3.theplanet.com (70.85.127.105) 147.028 ms 37.643 ms 211
.729 ms
4 ae1-0.ibr04.dllstx3.theplanet.com (70.85.127.36) 0.588 ms 0.944 ms 0.557
ms
5 ip-208.49.147.157.gblx.net (208.49.147.157) 0.734 ms * ge-4-3-0.ar1.DAL2.gb
lx.net (64.210.104.57) 0.825 ms
6 reach.ar1.DAL2.gblx.net (208.51.134.238) 194.026 ms 204.033 ms 202.444 ms
7 i-2-0.wil-core02.net.reach.com (202.84.143.65) 228.931 ms 237.578 ms 225.
668 ms
8 i-0-0.syd-core02.net.reach.com (202.84.144.102) 371.663 ms 380.445 ms 382
.239 ms
9 i-5-0.syd-core04.net.reach.com (202.84.144.250) 377.634 ms 375.261 ms 379
.148 ms
10 10GigabitEthernet5-0.oxf-core1.Sydney.telstra.net (203.50.13.33) 391.025 ms
371.847 ms *
11 10GigabitEthernet13-0.chw-core2.Sydney.telstra.net (203.50.6.1) 377.338 ms
379.733 ms 389.639 ms
12 Port-Channel200.chw30.Sydney.telstra.net (203.50.20.168) 379.885 ms * 391.409 ms
13 bpbnr002.lnk.telstra.net (139.130.0.30) 373.776 ms 383.170 ms *
14 CPE-61-9-195-5.nsw.bigpond.net.au (61.9.195.5) 373.313 ms 392.678 ms 369.413 ms
15 61.9.207.235 (61.9.207.235) 380.589 ms 389.694 ms *
16 *

After:
traceroute to 60.225.xxx.xx (60.225.xxx.xx), 30 hops max, 38 byte packets
1 97.70-84-217.reverse.theplanet.com (70.84.217.97) 1.274 ms 0.993 ms 1.058
ms
2 dist-vlan2.dsr1-1.dllstx5.theplanet.com (70.84.160.161) 0.363 ms 0.384 ms *
3 po51.dsr01.dllstx3.theplanet.com (70.85.127.105) 0.618 ms 0.540 ms 0.463 ms
4 ae1-0.ibr03.dllstx3.theplanet.com (70.85.127.35) 0.741 ms 0.634 ms *
5 67.99.43.233 (67.99.43.233) 6.014 ms 1.157 ms 1.120 ms
6 216.140.5.46 (216.140.5.46) 1.535 ms V20.rp0.dlls.broadwing.net (216.140.4.210) 1.567 ms *
7 gi0-2.dal-core01.net.reach.com (206.223.118.11) 1.748 ms 1.473 ms 1.448 ms
8 i-0-0.dal-core01.net.reach.com (202.84.142.81) 1.349 ms 1.509 ms 1.453 ms
9 i-2-0.wil-core02.net.reach.com (202.84.143.65) 33.228 ms 33.252 ms 32.969 ms
10 i-0-0.syd-core02.net.reach.com (202.84.144.102) 181.827 ms 181.370 ms 181.355 ms
11 i-5-0.syd-core04.net.reach.com (202.84.144.250) 181.844 ms 182.333 ms 182.206 ms
12 10GigabitEthernet5-0.oxf-core1.Sydney.telstra.net (203.50.13.33) 182.006 ms 182.346 ms 182.006 ms
13 10GigabitEthernet13-0.chw-core2.Sydney.telstra.net (203.50.6.1) 182.593 ms 182.182 ms 182.424 ms
14 Port-Channel200.chw30.Sydney.telstra.net (203.50.20.168) 231.013 ms 182.363 ms 182.468 ms
15 bpbnr002.lnk.telstra.net (139.130.0.30) 182.411 ms 182.450 ms 182.370 ms
16 CPE-61-9-195-5.nsw.bigpond.net.au (61.9.195.5) 182.480 ms 182.376 ms 182.237 ms
17 61.9.207.235 (61.9.207.235) 183.366 ms 183.241 ms 183.959 ms
18 *


Much better! .