Possible PCCW network problems?

Possible PCCW network problems?
Links: home · search · speed test · login · more ·

Links: Reply New Topic
Forums » International » Southeast Asian Broadband » Possible PCCW network problems?

sam123 @ 25th Apr 11:56AM:
Possible PCCW network problems?

Hi

Would any network gurus care to opine on the following pathping and dslreports.com line quality testing results on a Netvigator service?

******************************
C:\Documents and Settings\user3>pathping -n yahoo.com

Tracing route to yahoo.com [68.180.206.184]
over a maximum of 30 hops:
0 119.237.149.156
1 116.48.72.254
2 219.76.118.18
3 218.102.21.222
4 63.218.2.13
5 63.218.179.34
6 216.115.107.59
7 209.131.32.17
8 68.180.206.184

Computing statistics for 200 seconds...

Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 119.237.149.156
0/ 100 = 0% |
1 26ms 0/ 100 = 0% 0/ 100 = 0% 116.48.72.254
0/ 100 = 0% |
2 --- 100/ 100 =100% 100/ 100 =100% 219.76.118.18
0/ 100 = 0% |
3 31ms 1/ 100 = 1% 1/ 100 = 1% 218.102.21.222
0/ 100 = 0% |
4 36ms 0/ 100 = 0% 0/ 100 = 0% 63.218.2.13
0/ 100 = 0% |
5 174ms 0/ 100 = 0% 0/ 100 = 0% 63.218.179.34
0/ 100 = 0% |
6 189ms 0/ 100 = 0% 0/ 100 = 0% 216.115.107.59
0/ 100 = 0% |
7 187ms 0/ 100 = 0% 0/ 100 = 0% 209.131.32.17
0/ 100 = 0% |
8 171ms 0/ 100 = 0% 0/ 100 = 0% 68.180.206.184

Trace complete.

******************************
C:\Documents and Settings\user3>pathping -n google.com

Tracing route to google.com [74.125.67.100]
over a maximum of 30 hops:
0 119.237.149.156
1 116.48.72.254
2 219.76.118.18
3 218.102.21.222
4 219.76.106.2
5 218.189.106.50
6 64.233.175.209
7 209.85.249.236
8 209.85.248.131
9 72.14.233.117
10 209.85.240.225
11 209.85.240.225
12 72.14.239.90
13 209.85.254.249
14 209.85.255.194
15 * * *
Computing statistics for 375 seconds...

Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 119.237.149.156
0/ 100 = 0% |
1 26ms 0/ 100 = 0% 0/ 100 = 0% 116.48.72.254
0/ 100 = 0% |
2 --- 100/ 100 =100% 100/ 100 =100% 219.76.118.18
0/ 100 = 0% |
3 27ms 4/ 100 = 4% 4/ 100 = 4% 218.102.21.222
0/ 100 = 0% |
4 28ms 0/ 100 = 0% 0/ 100 = 0% 219.76.106.2
0/ 100 = 0% |
5 28ms 0/ 100 = 0% 0/ 100 = 0% 218.189.106.50
0/ 100 = 0% |
6 34ms 14/ 100 = 14% 14/ 100 = 14% 64.233.175.209
0/ 100 = 0% |
7 79ms 0/ 100 = 0% 0/ 100 = 0% 209.85.249.236
0/ 100 = 0% |
8 175ms 10/ 100 = 10% 10/ 100 = 10% 209.85.248.131
0/ 100 = 0% |
9 224ms 8/ 100 = 8% 8/ 100 = 8% 72.14.233.117
0/ 100 = 0% |
10 219ms 10/ 100 = 10% 10/ 100 = 10% 209.85.240.225
0/ 100 = 0% |
11 219ms 18/ 100 = 18% 18/ 100 = 18% 209.85.240.225
0/ 100 = 0% |
12 235ms 0/ 100 = 0% 0/ 100 = 0% 72.14.239.90
74/ 100 = 74% |
13 245ms 76/ 100 = 76% 2/ 100 = 2% 209.85.254.249
0/ 100 = 0% |
14 234ms 74/ 100 = 74% 0/ 100 = 0% 209.85.255.194
26/ 100 = 26% |
15 --- 100/ 100 =100% 0/ 100 = 0% 0.0.0.0

Trace complete.

******************************
dslreports.com line quality testing result:
»/linequality/nil/2514310

******************************

(1) Does it appear that there's a packet loss/latency problem somewhere within the PCCW network?
(2) Is it likely that the problem is unrelated to the local DSL loop?

Thanks in advance.

Sam
reply