International Latency

brettwlewis · Jun 23, 2006

I've got a ticket logged with Sentech, but the more I speak to them the more they make me feel like its just me experiencing this problem.

I'm experiencing between 2000 and 4000ms ping times to various international sites, making some interactive sites unusable.

Is it just me, or are other myWireless users seeing this problem too?

Brett

---------------------------------------------------------

For example, this is a traceroute to 64.233.185.111 (pop.gmail.com)...

C:\>tracert 64.233.185.111

Tracing route to 64.233.185.111 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms nemo [192.168.1.254]
2 371 ms 278 ms 198 ms 66.18.87.50
3 277 ms 680 ms 442 ms 66.18.65.105
4 279 ms 175 ms 188 ms gige-0-0-102.rtr-core5-stp.infosat.net [66.18.65.106]
5 199 ms 215 ms 342 ms 66.18.87.254
6 217 ms 219 ms 224 ms 168.209.18.61
7 369 ms 272 ms 388 ms core2b-rba-gi8-0-0.rtr.isnet.net [196.26.0.9]
8 486 ms 414 ms 459 ms 168.209.0.94
9 675 ms 734 ms 495 ms 168.209.244.7
10 703 ms 579 ms 636 ms core1-0-2-0.lga.net.google.com [198.32.160.130]
11 831 ms 781 ms 696 ms 216.239.49.34
12 2559 ms 2439 ms 2357 ms 66.249.94.235
13 2459 ms 2563 ms 2732 ms 72.14.238.138
14 2565 ms 2351 ms 2068 ms 72.14.239.19
15 2441 ms 2420 ms 2521 ms 72.14.238.198
16 2566 ms 2639 ms 2794 ms 64.233.185.111

Trace complete.

TheRoDent · Jun 23, 2006

Not getting the same here:

Code:

Host                                          Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. 192.168.16.254                              0.0%    27    0.1   0.2   0.1   0.4   0.1
 2. core4-stp-gig0-0.sentech.co.za              0.0%    27    1.8  13.1   1.2 188.8  37.7
 3. stpbr01.sentech.co.za                       0.0%    27    4.6  21.9   3.8 314.5  62.1
 4. 168.209.18.61                               0.0%    27    9.5   8.3   5.9  10.3   1.1
 5. core2b-rba-gi8-0-0.rtr.isnet.net            0.0%    26   17.5 139.3   7.7 2020. 434.0
 6. 168.209.0.94                                0.0%    26  253.7 255.9 253.3 261.1   1.7
 7. 168.209.244.7                               7.7%    26  435.1 445.4 415.3 557.7  26.4
 8. core1-0-2-0.lga.net.google.com              0.0%    26  247.8 250.5 247.8 253.4   1.4
 9. 216.239.49.34                               7.7%    26  250.2 251.2 247.5 255.4   2.1
10. 66.249.94.235                               0.0%    26  254.0 256.1 251.6 277.1   4.9
11. 72.14.238.138                               0.0%    26  265.7 269.1 263.7 283.3   4.4
12. 72.14.238.155                               7.7%    26  268.2 271.2 266.0 299.8   6.8
    72.14.239.19
13. 72.14.238.194                               0.0%    26  270.6 270.9 267.1 275.9   1.9
    72.14.238.198
14. 64.233.185.111                             11.5%    26  269.1 268.4 265.9 272.4   1.7

ProAsm · Jun 23, 2006

MyWireless256

Code:

C:\>tracert 64.233.185.111
Tracing route to 64.233.185.111 over a maximum of 30 hops

  1     8 ms    <1 ms    <1 ms  192.168.0.200
  2   217 ms   111 ms   119 ms  66.18.87.50
  3   265 ms   118 ms   400 ms  66.18.65.105
  4    92 ms   158 ms   120 ms  gige-0-0-102.rtr-core5-stp.infosat.net [66.18.65.106]
  5   106 ms   120 ms   118 ms  66.18.87.254
  6   117 ms   160 ms   116 ms  168.209.18.61
  7   167 ms   119 ms   120 ms  core2b-rba-gi8-0-0.rtr.isnet.net [196.26.0.9]
  8   397 ms   379 ms   399 ms  168.209.0.94
  9   377 ms   398 ms   401 ms  168.209.244.7
 10   372 ms   360 ms   398 ms  core1-0-2-0.lga.net.google.com [198.32.160.130]
 11   403 ms   378 ms   380 ms  216.239.49.34
 12   361 ms   358 ms   440 ms  72.14.233.113
 13   377 ms   399 ms   398 ms  72.14.233.147
 14   412 ms   399 ms     *     72.14.236.26
 15   472 ms   359 ms     *     72.14.238.194
 16   476 ms   610 ms   399 ms  64.233.185.111

Trace complete.

ADSL512

Code:

C:\>tracert 64.233.185.111
Tracing route to 64.233.185.111 over a maximum of 30 hops

  1     8 ms     1 ms     1 ms  server.mshome.net [192.168.0.100]
  2     2 ms     1 ms     1 ms  10.0.0.1
  3    13 ms    11 ms    11 ms  dsl-145-0-01.telkomadsl.co.za [165.145.0.1]
  4    12 ms    13 ms    12 ms  ndn-ip-er-1-fe-3-0-0-1.telkom-ipnet.co.za [196.43.10.130]
  5    13 ms    13 ms    12 ms  ndn-ip-esr-1-fe-1-0-1-2.telkom-ipnet.co.za [196.43.10.73]
  6   346 ms   344 ms   346 ms  ny-ip-dir-globalc-pos-5-0.telkom-ipnet.co.za [196.43.9.137]
  7   453 ms   452 ms   452 ms  g0-2.na01.b001105-24.jfk02.atlas.cogentco.com [38.112.18.41]
  8   452 ms   453 ms   451 ms  g10-2-104.core01.jfk02.atlas.cogentco.com [38.112.38.169]
  9   452 ms   448 ms   454 ms  p15-0.core01.jfk05.atlas.cogentco.com [154.54.2.126]
 10   479 ms   480 ms     *     core1-0-0-8.lga.net.google.com [198.32.118.39]
 11   455 ms   469 ms   479 ms  66.249.94.235
 12   485 ms   475 ms   468 ms  72.14.238.138
 13   467 ms   474 ms   468 ms  72.14.238.155
 14   471 ms   471 ms   472 ms  72.14.238.198
 15   471 ms   468 ms   480 ms  72.14.236.16
 16   472 ms   469 ms   471 ms  64.233.185.111

Trace complete.

newb5000 · Jun 23, 2006

Jeeez! TheRoDent, ProAsm - those latencies are awesome!

Here's mine:

Code:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2   248 ms   273 ms   219 ms  66.18.87.50
  3   251 ms   317 ms   299 ms  66.18.65.105
  4   190 ms     *      206 ms  gige-0-0-102.rtr-core5-stp.infosat.net [66.18.65
.106]
  5   180 ms   355 ms   205 ms  66.18.87.254
  6   165 ms   377 ms   148 ms  168.209.18.61
  7   324 ms   173 ms   219 ms  core2b-rba-gi8-0-0.rtr.isnet.net [196.26.0.9]
  8   399 ms   688 ms   479 ms  168.209.0.94
  9   413 ms   635 ms   465 ms  168.209.244.7
 10   576 ms   428 ms   477 ms  core1-0-2-0.lga.net.google.com [198.32.160.130]

 11  1509 ms   462 ms   736 ms  216.239.49.34
 12  1212 ms  1438 ms  1339 ms  66.249.94.235
 13  2230 ms  1942 ms  1508 ms  72.14.238.138
 14  1729 ms  1646 ms  1590 ms  72.14.239.19
 15  1715 ms  1557 ms  1548 ms  72.14.238.198
 16  1696 ms  1629 ms  1644 ms  64.233.185.111

brettwlewis · Jun 27, 2006

Okay, so I upped my MTU from 1460 to 1496 on my Linux Smoothwall firewall / router and my latencies are far better.

Let's see if it holds...

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| nemo - 0 | 39 | 39 | 0 | 0 | 16 | 0 |
| 66.18.87.50 - 0 | 39 | 38 | 125 | 276 | 1047 | 531 |
| 66.18.65.105 - 0 | 39 | 38 | 141 | 289 | 969 | 453 |
| gige-0-0-102.rtr-core5-stp.infosat.net - 0 | 38 | 38 | 109 | 331 | 891 | 390 |
| 66.18.87.254 - 0 | 38 | 38 | 125 | 341 | 829 | 312 |
| 168.209.18.61 - 3 | 38 | 37 | 125 | 328 | 766 | 250 |
| core2b-rba-gi8-0-0.rtr.isnet.net - 0 | 38 | 38 | 109 | 306 | 797 | 187 |
| 168.209.0.94 - 0 | 38 | 38 | 375 | 552 | 922 | 594 |
| 168.209.244.7 - 14 | 38 | 33 | 515 | 718 | 1218 | 562 |
| core1-0-2-0.lga.net.google.com - 14 | 38 | 33 | 531 | 739 | 1156 | 859 |
| 216.239.49.34 - 14 | 38 | 33 | 531 | 718 | 1046 | 828 |
| 66.249.94.235 - 6 | 38 | 36 | 516 | 738 | 1406 | 609 |
| 72.14.238.138 - 14 | 38 | 32 | 546 | 817 | 1437 | 1437 |
| 72.14.239.19 - 11 | 38 | 33 | 547 | 799 | 1328 | 1328 |
| 72.14.238.194 - 9 | 38 | 34 | 516 | 790 | 1266 | 1250 |
| 64.233.185.109 - 9 | 38 | 34 | 531 | 737 | 1188 | 1172 |
|________________________________________________|______|______|______|______|______|______|
WinMTR - 0.8. Copyleft @2000-2002 Vasile Laurentiu Stanimir ( [email protected] )

Luke7777 · Jun 28, 2006

Tonight is NOT nice:

Code:

Tracing route to gmail-pop.l.google.com [64.233.185.111]
over a maximum of 30 hops:

  1     4 ms     1 ms     1 ms  192.168.1.1
  2   990 ms   262 ms   317 ms  66.18.87.50
  3   400 ms   618 ms   736 ms  66.18.65.105
  4   812 ms   240 ms   288 ms  gige-0-0-102.rtr-core5-stp.infosat.net [66.18.65.106]
  5   717 ms   541 ms   517 ms  66.18.87.254
  6   256 ms   640 ms   388 ms  168.209.18.61
  7   358 ms  1201 ms  1000 ms  core1b-rba-gi0-1.rtr.isnet.net [196.26.0.10]
  8  2119 ms  2297 ms  1278 ms  168.209.160.89
  9  2762 ms   495 ms   559 ms  168.209.224.65
 10   460 ms   703 ms   479 ms  195.66.224.125
 11     *     3146 ms  2435 ms  72.14.236.216
 12   859 ms     *      620 ms  66.249.94.235
 13   558 ms  1299 ms   579 ms  72.14.238.138
 14  1066 ms   660 ms  1171 ms  72.14.239.19
 15   567 ms   660 ms   690 ms  72.14.238.198
 16   680 ms   737 ms   802 ms  64.233.185.111

Trace complete.

C:\Documents and Settings\Deon>tracert pop.gmail.com

Tracing route to gmail-pop.l.google.com [64.233.185.109]
over a maximum of 30 hops:

  1     5 ms     1 ms     1 ms  192.168.1.1
  2  1509 ms  1075 ms   423 ms  66.18.87.50
  3  1976 ms  1083 ms   216 ms  66.18.65.105
  4   278 ms  2158 ms   251 ms  gige-0-0-102.rtr-core5-stp.infosat.net [66.18.65
.106]
  5   160 ms   331 ms   358 ms  66.18.87.254
  6   558 ms   478 ms   560 ms  168.209.18.61
  7   390 ms   181 ms   461 ms  core2b-rba-gi8-0-0.rtr.isnet.net [196.26.0.9]
  8  1081 ms  1240 ms   719 ms  168.209.0.94
  9  1883 ms  1056 ms   488 ms  168.209.244.7
 10   430 ms   428 ms   619 ms  core1-0-2-0.lga.net.google.com [198.32.160.130]

 11   835 ms     *      670 ms  216.239.49.34
 12   800 ms   650 ms  1823 ms  66.249.94.235
 13   579 ms   620 ms   750 ms  72.14.238.138
 14  1305 ms   852 ms  2462 ms  72.14.239.19
 15     *      452 ms   599 ms  72.14.238.198
 16   660 ms  1255 ms   633 ms  64.233.185.109

Trace complete.

C:\Documents and Settings\Deon>tracert pop.gmail.com

Tracing route to gmail-pop.l.google.com [64.233.185.109]
over a maximum of 30 hops:

  1     4 ms     1 ms     1 ms  192.168.1.1
  2  1029 ms   767 ms   238 ms  66.18.87.50
  3   850 ms   814 ms  3639 ms  66.18.65.105
  4   775 ms   814 ms   208 ms  gige-0-0-102.rtr-core5-stp.infosat.net [66.18.65
.106]
  5  1506 ms   436 ms  2003 ms  66.18.87.254
  6   175 ms   372 ms   243 ms  168.209.18.61
  7   159 ms   569 ms   919 ms  core2b-rba-gi8-0-0.rtr.isnet.net [196.26.0.9]
  8     *      782 ms   429 ms  168.209.0.94
  9   895 ms  1298 ms   773 ms  168.209.244.7
 10   564 ms  1741 ms  3023 ms  core1-0-2-0.lga.net.google.com [198.32.160.130]

 11  1738 ms     *        *     216.239.49.34
 12   646 ms  1340 ms  1179 ms  66.249.94.235
 13   625 ms  2994 ms     *     72.14.238.138
 14   772 ms   765 ms   899 ms  72.14.238.155
 15   634 ms   970 ms   500 ms  72.14.238.194
 16   649 ms   688 ms   843 ms  64.233.185.109

Trace complete.

Chaz · Jun 29, 2006

C:\Documents and Settings\Chaz>tracert 64.223.185.111

Tracing route to pool-64-223-185-111.man.east.verizon.net [64.223.185.111]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 28 ms 23 ms 24 ms lo100.dlk-ar1.net.digiweb.ie [83.147.147.1]
3 41 ms 31 ms 31 ms gi-0-2-45.dub-deg-br1.net.digiweb.ie [83.147.163
.38]
4 37 ms 47 ms 48 ms 816.ge5-0.mpr1.lhr1.uk.above.net [213.161.79.65]

5 50 ms 47 ms 39 ms so-5-3-0.cr1.lhr3.uk.above.net [208.184.231.178]

6 59 ms 39 ms 48 ms 64.125.27.229.available.above.net [64.125.27.229
]
7 141 ms 126 ms 139 ms so-4-0-0.cr1.dca2.us.above.net [64.125.27.57]
8 148 ms 129 ms 126 ms so-6-0-0.mpr1.iad1.us.above.net [64.125.28.126]

9 150 ms 153 ms 151 ms so-3-0-0.mpr2.iad2.us.above.net [64.125.28.214]

10 117 ms 120 ms 151 ms so-3-0-0.mpr2.iad10.us.above.net [64.125.30.121]

11 132 ms 124 ms 130 ms so-0-0-0.mpr1.iad10.us.above.net [64.125.30.113]

12 139 ms 126 ms 126 ms so-4-1-0-0.PEER-RTR1.ASH.verizon-gni.net [130.81
.15.41]
13 135 ms 134 ms 151 ms so-7-3-0-0.BB-RTR1.RES.verizon-gni.net [130.81.1
0.89]
14 130 ms 152 ms 138 ms so-7-2-0-0.BB-RTR1.NY325.verizon-gni.net [130.81
.8.254]
15 138 ms 128 ms 151 ms so-7-2-0-0.BB-RTR1.NY5030.verizon-gni.net [130.8
1.7.90]
16 148 ms 151 ms 151 ms 130.81.20.119
17 151 ms 156 ms 152 ms A4-0-0-1711.DSL-RTR1.MAN.verizon-gni.net [130.81
.10.70]
18 188 ms 176 ms 176 ms pool-64-223-185-111.man.east.verizon.net [64.223
.185.111]

Chaz · Jun 29, 2006

Sorry, coulnt resist. From my pesky home wireless connection.

brettwlewis · Jun 29, 2006

Me changing my MTU setting and better latency may just have been co-incidental.

My ping times have gone through the roof again, since sometime during the day yesterday.

Anyone else battling today?

And if anyone can offer any insight into this issue, please make a post. I'm pulling my hair out!!!

C:\>tracert pop.gmail.com

Tracing route to gmail-pop.l.google.com [64.233.185.111]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms nemo [192.168.1.254]
2 632 ms 207 ms 319 ms 66.18.87.50
3 254 ms 239 ms 243 ms 66.18.65.105
4 187 ms 153 ms 180 ms gige-0-0-102.rtr-core5-stp.infosat.net [66.18.65
.106]
5 225 ms 199 ms 293 ms 66.18.87.254
6 192 ms 181 ms 361 ms 168.209.18.61
7 106 ms 219 ms 219 ms core2b-rba-gi8-0-0.rtr.isnet.net [196.26.0.9]
8 338 ms 459 ms 379 ms 168.209.0.94
9 422 ms 591 ms 399 ms 168.209.244.7
10 473 ms 449 ms 432 ms core1-0-2-0.lga.net.google.com [198.32.160.130]

11 427 ms * * 216.239.49.34
12 3020 ms 3076 ms 3039 ms 66.249.94.235
13 2860 ms 3361 ms 2931 ms 72.14.238.138
14 3339 ms 2941 ms 2918 ms 72.14.239.19
15 2876 ms 3029 ms 3021 ms 72.14.238.194
16 2978 ms 3019 ms 3138 ms 64.233.185.111

Trace complete.

asilva · Jun 29, 2006

Problems again?

Yes, i seem to be having a problem as well, i did some simple pings to google, and, although the latency to google is fair, there are alot of timeouts, so, i broke down the ip numbers and started to ping each and everyone of them to see where the timeouts started, and im said to say, it's the next hop from the international link. This might or might not indicate a problem with the international link itself, i wonder what kind of maintenance was done a few days ago. Anyway, it's almost impossible to stream right now. Oh, i almost forgot, i usualy play world of warcraft on US servers and my latency was actualy good (considering), about 980ms, since a few days ago, it jumped to 5 seconds...so, it's almost impossible to play (just as an example). I think the timeouts have a saying there. By the way, you cannot "see" the timeouts with traceroute but doing simple pings, even when the latency is good, you can see them ocurring frenquently, say, about once every 4 good pings. I know timeouts do ocur, more so during peak hours, but this is ridiculous.
I hope sentech fix this, AGAIN.
cheers,
AS

ShadowSA · Jul 3, 2006

I'm getting a lot of dropped packets too. On 256. Just for the record.

asilva · Jul 3, 2006

Yeah,
it seems back to the same ol'problems...

JayM · Jul 5, 2006

asilva said:
Yes, i seem to be having a problem as well, i did some simple pings to google, and, although the latency to google is fair, there are alot of timeouts, so, i broke down the ip numbers and started to ping each and everyone of them to see where the timeouts started, and im said to say, it's the next hop from the international link. This might or might not indicate a problem with the international link itself, i wonder what kind of maintenance was done a few days ago. Anyway, it's almost impossible to stream right now. Oh, i almost forgot, i usualy play world of warcraft on US servers and my latency was actualy good (considering), about 980ms, since a few days ago, it jumped to 5 seconds...so, it's almost impossible to play (just as an example). I think the timeouts have a saying there. By the way, you cannot "see" the timeouts with traceroute but doing simple pings, even when the latency is good, you can see them ocurring frenquently, say, about once every 4 good pings. I know timeouts do ocur, more so during peak hours, but this is ridiculous.
I hope sentech fix this, AGAIN.
cheers,
AS

Try "pathping <ip>" ... much easier.

brettwlewis · Aug 5, 2006

There's been an end to my sad saga - I hope I don't bring a tear to too many of you out there.

I'm cancelling my MyWireless128 and going for ADSL 384.

I'm sure I'll have some (different) pain going that route - they say a change is as good as a holiday - but I'm done with Sentech and their "support" guys.

To cut a long story short:-
- my ticket has been open for close on 2 months,
- it took close to 4 weeks for "second level" to do anything,
- they finally sent someone to do some on-site tests (tho' I never saw them),
- they say the latency I'm seeing is common to most 128 and some 512 clients - 256 seems better for some in explicable reason,
- they are looking for a solution,
- they say they are installing some new kit this month and improvements may arise.

But I'm not hanging around to see what happens...

Join the MyBroadband community

Get started

International Latency

brettwlewis

Well-Known Member

TheRoDent

Cool Ideas Rep

ProAsm

Expert Member

newb5000

Well-Known Member

brettwlewis

Well-Known Member

Luke7777

Executive Member

Chaz

Active Member

Chaz

Active Member

brettwlewis

Well-Known Member

asilva

Active Member

ShadowSA

Well-Known Member

asilva

Active Member

JayM

Expert Member

brettwlewis

Well-Known Member