Latancy problem, again!

G

Gimli_

Expert Member
Joined
Feb 8, 2005
Messages
1,011
Reaction score
346
Location
Irene, Centurion
3G has not been usable in my area since the start of the weekend, so I switched over to Edge and this is what I get.

Target Name: www.google.co.za
IP: 64.233.161.99
Date/Time: 10/16/2006 01:02:06 PM

2 359 ms 494 ms 425 ms 196-11-241-209.mtn.co.za [196.11.241.209]
3 449 ms 664 ms 597 ms 196-11-241-214.mtn.co.za [196.11.241.214]
4 442 ms 632 ms 687 ms 196-11-241-6.mtn.co.za [196.11.241.6]
5 431 ms 666 ms 877 ms rb-ad-1--mtn-rb-1-a.mtnns.net [196.44.8.210]
6 442 ms 658 ms 990 ms jp-ad-1--rb-ia-1-a.mtnns.net [196.44.8.86]
7 449 ms 644 ms 1080 ms rb-nt-1--rb-cr-2-a.mtnns.net [196.44.31.26]
8 578 ms 774 ms 1346 ms lt-ipa-1--rb-ipd-2-a.mtnns.net [196.44.31.1]
9 656 ms 804 ms 1335 ms lt-tpr-1--lt-cr-1-a.uk.mtnns.net [209.212.111.129]
10 640 ms 775 ms 1386 ms y-s-2.lon1.arbinet.net [213.232.64.76]
11 632 ms 762 ms 1354 ms ae-0-54.bbr2.London1.Level3.net [4.68.116.98]
12 685 ms 812 ms 1425 ms ae-0-0.bbr2.Washington1.Level3.net [4.68.128.210]
13 -32764 ms 783 ms 1397 ms ae-11-53.car1.Washington1.Level3.net [4.68.121.82]
14 744 ms 774 ms 1410 ms GOOGLE-INC.car1.Level3.net [4.79.228.38]
15 714 ms 746 ms 1379 ms [72.14.238.234]
16 821 ms -32764 ms 1351 ms [72.14.236.202]
17 833 ms -32764 ms 1354 ms [216.239.49.214]
18 800 ms 738 ms 1347 ms [64.233.161.99]


That is +-400 ms to the tower and +- 1000 to Google.

When is this supposed upgrade going to be done?
 
Gimli said:
3G has not been usable in my area since the start of the weekend, so I switched over to Edge and this is what I get.

Target Name: www.google.co.za
IP: 64.233.161.99
Date/Time: 10/16/2006 01:02:06 PM

2 359 ms 494 ms 425 ms 196-11-241-209.mtn.co.za [196.11.241.209]
3 449 ms 664 ms 597 ms 196-11-241-214.mtn.co.za [196.11.241.214]
4 442 ms 632 ms 687 ms 196-11-241-6.mtn.co.za [196.11.241.6]
5 431 ms 666 ms 877 ms rb-ad-1--mtn-rb-1-a.mtnns.net [196.44.8.210]
6 442 ms 658 ms 990 ms jp-ad-1--rb-ia-1-a.mtnns.net [196.44.8.86]
7 449 ms 644 ms 1080 ms rb-nt-1--rb-cr-2-a.mtnns.net [196.44.31.26]
8 578 ms 774 ms 1346 ms lt-ipa-1--rb-ipd-2-a.mtnns.net [196.44.31.1]
9 656 ms 804 ms 1335 ms lt-tpr-1--lt-cr-1-a.uk.mtnns.net [209.212.111.129]
10 640 ms 775 ms 1386 ms y-s-2.lon1.arbinet.net [213.232.64.76]
11 632 ms 762 ms 1354 ms ae-0-54.bbr2.London1.Level3.net [4.68.116.98]
12 685 ms 812 ms 1425 ms ae-0-0.bbr2.Washington1.Level3.net [4.68.128.210]
13 -32764 ms 783 ms 1397 ms ae-11-53.car1.Washington1.Level3.net [4.68.121.82]
14 744 ms 774 ms 1410 ms GOOGLE-INC.car1.Level3.net [4.79.228.38]
15 714 ms 746 ms 1379 ms [72.14.238.234]
16 821 ms -32764 ms 1351 ms [72.14.236.202]
17 833 ms -32764 ms 1354 ms [216.239.49.214]
18 800 ms 738 ms 1347 ms [64.233.161.99]


That is +-400 ms to the tower and +- 1000 to Google.

When is this supposed upgrade going to be done?
Click to expand...

Sheeesh this isn't good at all, I've emailed this to our 3G engineers and will advise ASAP

MTNDD
 
Gimli said:
3G has not been usable in my area since the start of the weekend, so I switched over to Edge and this is what I get.

Target Name: www.google.co.za
IP: 64.233.161.99
Date/Time: 10/16/2006 01:02:06 PM

2 359 ms 494 ms 425 ms 196-11-241-209.mtn.co.za [196.11.241.209]
3 449 ms 664 ms 597 ms 196-11-241-214.mtn.co.za [196.11.241.214]
4 442 ms 632 ms 687 ms 196-11-241-6.mtn.co.za [196.11.241.6]
5 431 ms 666 ms 877 ms rb-ad-1--mtn-rb-1-a.mtnns.net [196.44.8.210]
6 442 ms 658 ms 990 ms jp-ad-1--rb-ia-1-a.mtnns.net [196.44.8.86]
7 449 ms 644 ms 1080 ms rb-nt-1--rb-cr-2-a.mtnns.net [196.44.31.26]
8 578 ms 774 ms 1346 ms lt-ipa-1--rb-ipd-2-a.mtnns.net [196.44.31.1]
9 656 ms 804 ms 1335 ms lt-tpr-1--lt-cr-1-a.uk.mtnns.net [209.212.111.129]
10 640 ms 775 ms 1386 ms y-s-2.lon1.arbinet.net [213.232.64.76]
11 632 ms 762 ms 1354 ms ae-0-54.bbr2.London1.Level3.net [4.68.116.98]
12 685 ms 812 ms 1425 ms ae-0-0.bbr2.Washington1.Level3.net [4.68.128.210]
13 -32764 ms 783 ms 1397 ms ae-11-53.car1.Washington1.Level3.net [4.68.121.82]
14 744 ms 774 ms 1410 ms GOOGLE-INC.car1.Level3.net [4.79.228.38]
15 714 ms 746 ms 1379 ms [72.14.238.234]
16 821 ms -32764 ms 1351 ms [72.14.236.202]
17 833 ms -32764 ms 1354 ms [216.239.49.214]
18 800 ms 738 ms 1347 ms [64.233.161.99]


That is +-400 ms to the tower and +- 1000 to Google.

When is this supposed upgrade going to be done?
Click to expand...


What does all this mean in ENGLISH!!!!!

Sean
 
MTNDD, do you have some feedback yet? I am now in a different location, PTA CBD with 5 signal and on HSDPA, how is this for latancy?

Target Name: www.google.co.za
IP: 72.14.221.99
Date/Time: 10/17/2006 10:58:11 AM

2 2393 ms 2167 ms 2202 ms 196-11-241-209.mtn.co.za [196.11.241.209]
3 4304 ms 4217 ms 4101 ms 196-11-241-214.mtn.co.za [196.11.241.214]
4 4304 ms 4217 ms 4099 ms 196-11-241-6.mtn.co.za [196.11.241.6]
5 4024 ms 4026 ms 3881 ms rb-ad-1--mtn-rb-1-a.mtnns.net [196.44.8.210]
6 4044 ms 3996 ms 3925 ms jp-ad-1--rb-ia-1-a.mtnns.net [196.44.8.86]
7 4154 ms 4176 ms 4150 ms rb-nt-1--rb-cr-2-a.mtnns.net [196.44.31.26]
8 4244 ms * 4379 ms lt-ipa-1--rb-ipd-2-a.mtnns.net [196.44.31.1]
9 4074 ms 4106 ms 4139 ms lt-tpr-1--lt-cr-1-a.uk.mtnns.net [209.212.111.129]
10 4098 ms 4126 ms 4140 ms y-s-2.lon1.arbinet.net [213.232.64.76]
11 * 4137 ms 4139 ms ae-0-55.bbr1.London1.Level3.net [4.68.116.129]
12 -32764 ms -32764 ms 4399 ms ae-1-0.bbr2.Frankfurt1.Level3.net [212.187.128.29]
13 -32764 ms -32764 ms 4139 ms ae-12-55.car2.Frankfurt1.Level3.net [4.68.118.144]
14 4023 ms 4096 ms 4128 ms [62.67.38.222]
15 4260 ms 4427 ms 4359 ms [72.14.232.207]
16 -32764 ms 4436 ms 4349 ms [72.14.232.190]
17 4014 ms 4206 ms 4169 ms [72.14.221.99]


That is 2 seconds to the tower and 4 seconds to Google. From this exact position I have had 80ms to the tower, so what is wrong on your side?
 
Last edited:
Gimli said:
MTNDD, do you have some feedback yet? I am now in a different location, PTA CBD with 5 signal and on HSDPA, how is this for latancy?

Target Name: www.google.co.za
IP: 72.14.221.99
Date/Time: 10/17/2006 10:58:11 AM

2 2393 ms 2167 ms 2202 ms 196-11-241-209.mtn.co.za [196.11.241.209]
3 4304 ms 4217 ms 4101 ms 196-11-241-214.mtn.co.za [196.11.241.214]
4 4304 ms 4217 ms 4099 ms 196-11-241-6.mtn.co.za [196.11.241.6]
5 4024 ms 4026 ms 3881 ms rb-ad-1--mtn-rb-1-a.mtnns.net [196.44.8.210]
6 4044 ms 3996 ms 3925 ms jp-ad-1--rb-ia-1-a.mtnns.net [196.44.8.86]
7 4154 ms 4176 ms 4150 ms rb-nt-1--rb-cr-2-a.mtnns.net [196.44.31.26]
8 4244 ms * 4379 ms lt-ipa-1--rb-ipd-2-a.mtnns.net [196.44.31.1]
9 4074 ms 4106 ms 4139 ms lt-tpr-1--lt-cr-1-a.uk.mtnns.net [209.212.111.129]
10 4098 ms 4126 ms 4140 ms y-s-2.lon1.arbinet.net [213.232.64.76]
11 * 4137 ms 4139 ms ae-0-55.bbr1.London1.Level3.net [4.68.116.129]
12 -32764 ms -32764 ms 4399 ms ae-1-0.bbr2.Frankfurt1.Level3.net [212.187.128.29]
13 -32764 ms -32764 ms 4139 ms ae-12-55.car2.Frankfurt1.Level3.net [4.68.118.144]
14 4023 ms 4096 ms 4128 ms [62.67.38.222]
15 4260 ms 4427 ms 4359 ms [72.14.232.207]
16 -32764 ms 4436 ms 4349 ms [72.14.232.190]
17 4014 ms 4206 ms 4169 ms [72.14.221.99]


That is 2 seconds to the tower and 4 seconds to Google. From this exact position I have had 80ms to the tower, so what is wrong on your side?
Click to expand...


No Dude there is deff something wrong......
 
Gimli said:
MTNDD, do you have some feedback yet? I am now in a different location, PTA CBD with 5 signal and on HSDPA, how is this for latancy?

Target Name: www.google.co.za
IP: 72.14.221.99
Date/Time: 10/17/2006 10:58:11 AM

2 2393 ms 2167 ms 2202 ms 196-11-241-209.mtn.co.za [196.11.241.209]
3 4304 ms 4217 ms 4101 ms 196-11-241-214.mtn.co.za [196.11.241.214]
4 4304 ms 4217 ms 4099 ms 196-11-241-6.mtn.co.za [196.11.241.6]
5 4024 ms 4026 ms 3881 ms rb-ad-1--mtn-rb-1-a.mtnns.net [196.44.8.210]
6 4044 ms 3996 ms 3925 ms jp-ad-1--rb-ia-1-a.mtnns.net [196.44.8.86]
7 4154 ms 4176 ms 4150 ms rb-nt-1--rb-cr-2-a.mtnns.net [196.44.31.26]
8 4244 ms * 4379 ms lt-ipa-1--rb-ipd-2-a.mtnns.net [196.44.31.1]
9 4074 ms 4106 ms 4139 ms lt-tpr-1--lt-cr-1-a.uk.mtnns.net [209.212.111.129]
10 4098 ms 4126 ms 4140 ms y-s-2.lon1.arbinet.net [213.232.64.76]
11 * 4137 ms 4139 ms ae-0-55.bbr1.London1.Level3.net [4.68.116.129]
12 -32764 ms -32764 ms 4399 ms ae-1-0.bbr2.Frankfurt1.Level3.net [212.187.128.29]
13 -32764 ms -32764 ms 4139 ms ae-12-55.car2.Frankfurt1.Level3.net [4.68.118.144]
14 4023 ms 4096 ms 4128 ms [62.67.38.222]
15 4260 ms 4427 ms 4359 ms [72.14.232.207]
16 -32764 ms 4436 ms 4349 ms [72.14.232.190]
17 4014 ms 4206 ms 4169 ms [72.14.221.99]


That is 2 seconds to the tower and 4 seconds to Google. From this exact position I have had 80ms to the tower, so what is wrong on your side?
Click to expand...

I just got a reply saying that they are aware of the problems and are working on it

MTNDD
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X