High Ping and Latency

Xarog · Jul 10, 2012

Note :

Several people across several regions experiencing the same problem only certain times of the day indicates that once again the 8ta networks are being overburdened during peak hours.

Standing in a pink tutu on your roof trying to draw the attention of the Reception Faerie is unlikely to yield positive results, and waiting for 8ta techs to visit your premises is similarly pointless.

Effjh · Jul 10, 2012

Xarog said:
Note :

Several people across several regions experiencing the same problem only certain times of the day indicates that once again the 8ta networks are being overburdened during peak hours.

Standing in a pink tutu on your roof trying to draw the attention of the Reception Faerie is unlikely to yield positive results, and waiting for 8ta techs to visit your premises is similarly pointless.

+1

It is pretty clear that this is not an isolated issue. They oversold and continue to do so at the detriment of their network and our experiences using it. I think it is sad when customers don't even get angry any more, instead just being "moedeloos".

Ho3n3r · Jul 10, 2012

Mine is doing this tonight - not its best night:

Tracing route to www.hippo.co.za [196.35.70.58]
over a maximum of 30 hops:

1 * * * Request timed out.
2 291 ms 319 ms 399 ms 172.16.1.1
3 268 ms 309 ms 329 ms 172.16.1.129
4 368 ms 329 ms 439 ms tpr-ip-esr-6-wan.telkom-ipnet.co.za [196.25.181.169]
5 287 ms 309 ms 299 ms 196.43.11.202
6 258 ms 329 ms 319 ms 196.43.25.138
7 288 ms 319 ms 399 ms internet-solutions-gw.telkom-ipnet.co.za [196.25.46.90]
8 467 ms 469 ms 359 ms 196.26.0.61
9 338 ms 359 ms 399 ms core2a-bry-ge1-1-0.isnet.net [168.209.100.242]
10 318 ms 319 ms 309 ms csw3-bry-vl2.ip.isnet.net [168.209.217.250]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

Telkom · Jul 11, 2012

Hi there

We have the network team now monitoring this thread as well.

If you have not already done this - please use this thread to post your area (e.g. Oranjesig, Bloemfontein), time of day the test was made, as well as tracert results locally and internationally so the routing can be analyzed?

Regards,
Social Media Team

Nitrate · Jul 11, 2012

Region :Western Cape , Paarl , Du toit street 30
Time : happen every night from round about 6pm - 11/12pm
Ping/Latency jumps to 400 on local sites and 600-1000ms on international servers..

I will update this once the internet goes bonkers.

time: 9:15pm

C:\Users\Nitrate>tracert 41.185.60.73

Tracing route to 41.185.60.73 over a maximum of 30 hops

1 * * * Request timed out.
2 2474 ms 479 ms 409 ms 172.16.2.5
3 268 ms 309 ms 439 ms 172.16.2.129
4 678 ms 781 ms 828 ms 196.25.251.125
5 490 ms 667 ms 589 ms wnls-cr1-vl-101.wa.co.za [196.220.59.225]
6 458 ms 569 ms 629 ms 41.185.60.73

Trace complete.

C:\Users\Nitrate>

Teeworlds server (Wage local server) ip:41.185.60.73

This is suppose to be about 40ms- 60ms max... but the ping is 600ms -1000ms.

Please 8ta techs, HELP US , HELP YOU... some thing is seriously wrong here..

Xarog · Jul 11, 2012

8ta said:
Hi there

We have the network team now monitoring this thread as well.

If you have not already done this - please use this thread to post your area (e.g. Oranjesig, Bloemfontein), time of day the test was made, as well as tracert results locally and internationally so the routing can be analyzed?

Regards,
Social Media Team

I live in Benoni

Code:

tracert www.telkom.co.za

Tracing route to www.telkom.co.za [196.43.22.222]
over a maximum of 30 hops:

  1     *        *        *     Request timed out.
  2   293 ms   268 ms   279 ms  172.16.1.5
  3   247 ms   239 ms   229 ms  172.16.1.129
  4   236 ms   239 ms   229 ms  tpr-ip-esr-6-wan.telkom-ipnet.co.za [196.25.181.77]
  5   218 ms   228 ms   249 ms  196.43.39.162
  6   237 ms   268 ms   259 ms  rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.43.23.6]
  7   248 ms   249 ms   259 ms  nbsc-ip-bssr-1-atm-5-0-0-1.telkom-ipnet.co.za [196.43.23.30]
  8   247 ms   259 ms   277 ms  nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za [196.43.22.222]

Trace complete.

This tracert was done at 7:35 PM.

In about an hour's time the local pings will be at around 400-500ms. After about 11 PM the ping will fall back to its usual 30-50ms for the 172.16.1.5 IP.

All pings after the 1st hop are more or less consistent no matter what the time of day is. I.e. going from a local IP to Europe adds approximately 200ms and this increase does not fluctuate relative to overall network load (I am assuming that it picks up in the evenings.)

Xarog · Jul 11, 2012

15 minutes later...

Code:

tracert www.telkom.co.za

Tracing route to www.telkom.co.za [196.43.22.222]
over a maximum of 30 hops:

  1     *        *        *     Request timed out.
  2   347 ms   328 ms   358 ms  172.16.1.5
  3   335 ms   338 ms   349 ms  172.16.1.129
  4   386 ms   378 ms   358 ms  tpr-ip-esr-6-wan.telkom-ipnet.co.za [196.25.181.77]
  5   373 ms   398 ms   388 ms  196.43.39.162
  6   374 ms   358 ms   369 ms  rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.43.23.6]
  7   416 ms   388 ms   398 ms  nbsc-ip-bssr-1-atm-5-0-0-1.telkom-ipnet.co.za [196.43.23.30]
  8   415 ms   418 ms   408 ms  nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za [196.43.22.222]

Trace complete.

FreddyB · Jul 11, 2012

same here, unable to make use of 8ta for last week

Tracing route to www.telkom.co.za [196.43.22.222]
over a maximum of 30 hops:

1 * * * Request timed out.
2 505 ms 339 ms 418 ms 172.16.2.5
3 415 ms 279 ms 308 ms 172.16.2.129
4 685 ms 889 ms 649 ms wbs-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.4.117]
5 626 ms 768 ms 779 ms 196.43.39.162
6 607 ms 609 ms 569 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.43.23.6]
7 626 ms 618 ms 829 ms nbsc-ip-bssr-2-atm-5-0-0-1.telkom-ipnet.co.za [196.43.23.34]
8 545 ms 619 ms 569 ms nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za [196.43.22.222]

Trace complete.

My device + Signal

Speedtest

Steam TF2 Servers latency

moribond · Jul 11, 2012

Time: 21H14
Date: 11 July 2012

Speedtest:

Tracert: www.telkom.co.za
Tracing route to www.telkom.co.za [196.43.22.222]
over a maximum of 30 hops:

1 * * * Request timed out.
2 574 ms 360 ms 419 ms 172.16.2.1
3 448 ms 479 ms 349 ms 172.16.2.129
4 827 ms 999 ms 839 ms 196.25.251.125
5 567 ms 759 ms 659 ms 196.43.39.162
6 637 ms 739 ms 859 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.43.23.6]
7 267 ms 249 ms 279 ms nbsc-ip-bssr-1-atm-5-0-0-1.telkom-ipnet.co.za [196.43.23.30]
8 258 ms 259 ms 269 ms nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za [196.43.22.222]
Trace complete.

Network: 8ta
RSSI: >= -51 dBm
Device: E1820

My Location (approx) :
Lat: 25°51'6.22"S
Long: 28°14'41.94"E

8ta Tower Location (exact):
Lat: 25°50'59.49"S
Long: 28°14'49.93"E

Distance from the tower: < 500 meters [line of sight]

And:
If I swap out the SIM to cell c which uses the same tower, then I get whoosh;
but on 8ta is more like whooping cough....

Effjh · Jul 11, 2012

Time: 21:38

Tracert: www.telkom.co.za

Tracing route to telkom.co.za [196.43.22.222]
over a maximum of 30 hops:

1 4 ms 22 ms 1 ms 10.0.0.2
2 * * * Request timed out.
3 741 ms 613 ms 716 ms 172.16.2.5
4 * 502 ms 699 ms 172.16.2.129
5 1131 ms 1330 ms 920 ms wbs-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.4.1
17]
6 1148 ms 2655 ms 518 ms 196.43.39.162
7 404 ms 511 ms 409 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.4
3.23.6]
8 431 ms 409 ms 404 ms nbsc-ip-bssr-1-atm-5-0-0-1.telkom-ipnet.co.za [1
96.43.23.30]
9 2515 ms 511 ms 424 ms nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za [196.43
.22.222]

Trace complete.

RSSI: >= -68 dBm
Device: E1820

Location: Richwood Tower, Cape Town

Effjh · Jul 11, 2012

International, same as above location:

Tracert: www.yahoo.co.uk

Tracing route to yahoo.co.uk [77.238.178.122]
over a maximum of 30 hops:

1 3 ms 1 ms 1 ms 10.0.0.2
2 * * * Request timed out.
3 584 ms 825 ms 710 ms 172.16.2.5
4 523 ms 818 ms 614 ms 172.16.2.129
5 1250 ms 1023 ms 1228 ms wbs-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.4.1
17]
6 1330 ms 1228 ms 1235 ms lon-ip-dir-telecity-pos-1-1-0.telkom-ipnet.co.za
[196.43.9.50]
7 1329 ms 1433 ms 1330 ms 13-126-245-83.packetexchange.net [83.245.126.13]

8 1128 ms 1326 ms 1228 ms UNKNOWN-66-196-65-X.yahoo.com [66.196.65.17]
9 1329 ms 1330 ms 1125 ms ae-2.msr2.ird.yahoo.com [66.196.67.237]
10 1227 ms 1125 ms 1228 ms te-8-4.bas-b2.ird.yahoo.com [87.248.101.109]
11 1329 ms 2149 ms 1842 ms w2.rc.vip.ird.yahoo.com [77.238.178.122]

Trace complete.

Xarog · Jul 11, 2012

11PM and the network is almost back to normal again :

Code:

tracert www.telkom.co.za

Tracing route to www.telkom.co.za [196.43.22.222]
over a maximum of 30 hops:

  1     *        *        *     Request timed out.
  2    95 ms    99 ms    68 ms  172.16.1.5
  3    43 ms    69 ms    39 ms  172.16.1.129
  4    43 ms    39 ms    40 ms  tpr-ip-esr-6-wan.telkom-ipnet.co.za [196.25.181.77]
  5    38 ms    39 ms    49 ms  196.43.39.162
  6    56 ms    59 ms    69 ms  rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.43.23.6]
  7    87 ms    69 ms    79 ms  nbsc-ip-bssr-1-atm-5-0-0-1.telkom-ipnet.co.za [196.43.23.30]
  8    46 ms    49 ms    49 ms  nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za [196.43.22.222]

Trace complete.

Note how the ping is still spiking slightly to about 90ms.

FreddyB · Jul 11, 2012

Xarog said:
11PM and the network is almost back to normal again :

Note how the ping is still spiking slightly to about 90ms.

Not around here, its better than at 9pm but still pretty much useless at 11pm

Tracing route to www.telkom.co.za [196.43.22.222]
over a maximum of 30 hops:

1 * * * Request timed out.
2 30 ms 28 ms 27 ms 172.16.2.5
3 25 ms 22 ms 25 ms 172.16.2.129
4 466 ms 498 ms 479 ms wbs-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.4.117]
5 465 ms 399 ms 538 ms 196.43.39.162
6 405 ms 449 ms 529 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.43.23.6]
7 594 ms 678 ms 558 ms nbsc-ip-bssr-1-atm-5-0-0-1.telkom-ipnet.co.za [196.43.23.30]
8 534 ms * 670 ms nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za [196.43.22.222]

Trace complete.

Here is the 12AM results, so on midnight

Tracing route to www.telkom.co.za [196.43.22.222]
over a maximum of 30 hops:

1 * * * Request timed out.
2 47 ms 39 ms 41 ms 172.16.2.5
3 85 ms 97 ms 173 ms 172.16.2.129
4 98 ms 135 ms 107 ms 196.25.251.125
5 50 ms 75 ms 113 ms 196.43.39.162
6 52 ms 71 ms 69 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.43.23.6]
7 52 ms 64 ms 61 ms nbsc-ip-bssr-1-atm-5-0-0-1.telkom-ipnet.co.za [196.43.23.30]
8 53 ms 52 ms * nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za [196.43.22.222]
9 52 ms 66 ms 70 ms nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za [196.43.22.222]

Trace complete.

Lurking · Jul 12, 2012

I also have it. Smooth during the day but horrible at night now.

Can we get an update on this 8ta?

Nitrate · Jul 12, 2012

Region :Western Cape , Paarl , Du toit street 30
Time : happen every night from round about 6pm - 11/12pm
Ping/Latency jumps to 400 on local sites and 600-1000ms on international servers..

I will update this once the internet goes bonkers.

time: 9:15pm

C:\Users\Nitrate>tracert 41.185.60.73

Tracing route to 41.185.60.73 over a maximum of 30 hops

1 * * * Request timed out.
2 2474 ms 479 ms 409 ms 172.16.2.5
3 268 ms 309 ms 439 ms 172.16.2.129
4 678 ms 781 ms 828 ms 196.25.251.125
5 490 ms 667 ms 589 ms wnls-cr1-vl-101.wa.co.za [196.220.59.225]
6 458 ms 569 ms 629 ms 41.185.60.73

Trace complete.

C:\Users\Nitrate>

Teeworlds server (Wage local server) ip:41.185.60.73

This is suppose to be about 40ms- 60ms max... but the ping is 600ms -1000ms.

Please 8ta techs, HELP US , HELP YOU... some thing is seriously wrong here..

More info , using a e173 7.2mb DL , 3.2UP. RSSI = -75 and 93% signal strength..

marmeduke · Jul 12, 2012

East rand Guateng 8:42 pm

Tracing route to w2.rc.vip.ird.yahoo.com [77.238.178.122]
over a maximum of 30 hops:

1 * * * Request timed out.
2 556 ms 859 ms 479 ms 172.16.1.1
3 593 ms 508 ms 509 ms 172.16.1.129
4 761 ms 738 ms 748 ms tpr-ip-esr-6-wan.telkom-ipnet.co.za [196.25.181.77]
5 996 ms 989 ms 969 ms 196.43.18.234
6 928 ms 1059 ms 999 ms 13-126-245-83.packetexchange.net [83.245.126.13]

7 1097 ms 1018 ms 909 ms so-0-0-0.pat1.irz.yahoo.com [66.196.65.33]
8 977 ms 1079 ms 968 ms ae-1.msr1.ird.yahoo.com [66.196.67.231]
9 907 ms 958 ms 989 ms te-7-4.bas-b1.ird.yahoo.com [87.248.101.103]
10 948 ms 959 ms 989 ms w2.rc.vip.ird.yahoo.com [77.238.178.122]

Trace complete.

Mossiee · Jul 12, 2012

Same problem here..

When I play Counter-strike Source during the day I get pings of 30ms - 50ms.. then 6PM comes and everything is screwed. Sometimes I can't even browse the internet past 6PM.. It's pretty frustrating. Used to work fine until about 3 weeks ago.

I have the exact same signal strength throughout the day, but it's still insanely laggy past 6. I have also tried using the sim in another device, but still the same problem.

8ta seriously have to fix this.. paying them money for something that's useless most of the day

Effjh · Jul 12, 2012

Like clockwork. The only consistent part of this network so far. Same time every night:

Tracing route to telkom.co.za [196.43.22.222]
over a maximum of 30 hops:

1 1 ms * 2 ms 10.0.0.2
2 * * * Request timed out.
3 505 ms 818 ms 819 ms 172.16.2.5
4 635 ms * 595 ms 172.16.2.129
5 738 ms 928 ms 1025 ms wbs-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.4.1
17]
6 848 ms 1244 ms 921 ms 196.43.39.162
7 1158 ms 1228 ms 1229 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.4
3.23.6]
8 696 ms 1168 ms 1000 ms nbsc-ip-bssr-2-atm-5-0-0-1.telkom-ipnet.co.za [1
96.43.23.34]
9 1049 ms 1021 ms 961 ms telkom.co.za [196.43.22.222]

Trace complete.

Effjh · Jul 12, 2012

International:

Tracing route to yahoo.co.uk [77.238.178.122]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 10.0.0.2
2 * * * Request timed out.
3 547 ms 901 ms 716 ms 172.16.2.5
4 686 ms 850 ms 838 ms 172.16.2.129
5 1057 ms 921 ms 920 ms 196.25.251.125
6 1135 ms 1125 ms 1228 ms lon-ip-dir-telecity-pos-1-1-0.telkom-ipnet.co.za
[196.43.9.50]
7 1160 ms 1228 ms 1126 ms 13-126-245-83.packetexchange.net [83.245.126.13]

8 2250 ms 1331 ms 828 ms UNKNOWN-66-196-65-X.yahoo.com [66.196.65.17]
9 633 ms 511 ms 511 ms ae-2.msr2.ird.yahoo.com [66.196.67.237]
10 1036 ms 409 ms 409 ms te-8-4.bas-b2.ird.yahoo.com [87.248.101.109]
11 543 ms 511 ms 511 ms yahoo.co.uk [77.238.178.122]

Trace complete.

Ho3n3r · Jul 13, 2012

Ho3n3r said:
Mine is doing this tonight - not its best night:

Tracing route to www.hippo.co.za [196.35.70.58]
over a maximum of 30 hops:

1 * * * Request timed out.
2 291 ms 319 ms 399 ms 172.16.1.1
3 268 ms 309 ms 329 ms 172.16.1.129
4 368 ms 329 ms 439 ms tpr-ip-esr-6-wan.telkom-ipnet.co.za [196.25.181.169]
5 287 ms 309 ms 299 ms 196.43.11.202
6 258 ms 329 ms 319 ms 196.43.25.138
7 288 ms 319 ms 399 ms internet-solutions-gw.telkom-ipnet.co.za [196.25.46.90]
8 467 ms 469 ms 359 ms 196.26.0.61
9 338 ms 359 ms 399 ms core2a-bry-ge1-1-0.isnet.net [168.209.100.242]
10 318 ms 319 ms 309 ms csw3-bry-vl2.ip.isnet.net [168.209.217.250]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

Just for reference, here is Vodacom - maybe it gives 8ta some help, I dunno. All other conditions are the same as above:

Tracing route to www.hippo.co.za [196.35.70.58]
over a maximum of 30 hops:

1 54 ms 49 ms 49 ms 10.17.7.12
2 48 ms 59 ms 49 ms 10.242.249.2
3 48 ms 49 ms 49 ms 10.113.228.1
4 48 ms 59 ms 50 ms 41.192.248.18
5 49 ms 49 ms 49 ms vc-196-207-44-134.3g.vodacom.co.za [196.207.44.1
34]
6 48 ms 69 ms 49 ms 41.0.4.1
7 57 ms 59 ms 59 ms 41.0.0.5
8 58 ms 59 ms 60 ms 196.25.253.109
9 59 ms 49 ms 59 ms rrba-ip-lir-1-gig-3-0-0.telkom-ipnet.co.za [196.
43.11.134]
10 59 ms 48 ms 69 ms 196.43.25.138
11 58 ms 59 ms 59 ms internet-solutions-gw.telkom-ipnet.co.za [196.25
.46.90]
12 58 ms 59 ms 59 ms core1a-pkl-te-1-2.ip.isnet.net [168.209.1.139]
13 68 ms 59 ms 59 ms core1a-bry-te0-0-0-1.ip.isnet.net [168.209.100.7
8]
14 68 ms 59 ms 59 ms csw3-bry-vl2.ip.isnet.net [168.209.217.250]
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

Join the MyBroadband community

Get started

High Ping and Latency

Honorary Master

Well-Known Member

Honorary Master

Expert Member

Well-Known Member

Honorary Master

Honorary Master

Well-Known Member

Active Member

Well-Known Member

Well-Known Member

Honorary Master

Well-Known Member

Active Member

Well-Known Member

New Member

New Member

Well-Known Member

Well-Known Member

Honorary Master