High Ping and Latency

[sajunky]

pings use to be 199-250 . only local is more stable but that too jumps to 240-350 pings because the 8ta dashboard shows its jumping between HSPA and WCDMA the whole time !! and its not the modem !

Unstable pings is typical for 8ta.
WCDMA comes always when idle (not exchanging data), this is normal. Does it switch to WCDMA during downloading files as well?

[Dean56898]

Unstable pings is typical for 8ta.
WCDMA comes always when idle (not exchanging data), this is normal. Does it switch to WCDMA during downloading files as well?

Yess Like it

Broadband is Becoming a HARD Knock Life for Us

spendiet

WE GET KICKED

damn this dude wins a 10 Gb DSL Account for FREE by telling A Joke About South African Broadband

and the joke Telkom

[Draconia2]

Unstable pings is typical for 8ta.
WCDMA comes always when idle (not exchanging data), this is normal. Does it switch to WCDMA during downloading files as well?

EDIT: no it doesn't do that anymore but still constant timeouts on the diablo 3 EU server.

only time it doesn't do that is when i play cod4 , constant ping of 100-109.

gonna give 8ta a call now for an update. its been a few days

====

spoke to soon, it just started doing that while im playing with my hardcore character on a public game which would force it download / upload data ..... this is starting to P%^$%& me off, 8ta techy told me WCDMA is when it handshakes with the tower and its the towers name (erm whaat the F?? no its not??) .... meaning im not sure he knew what it meant but forwarded my request to the "SOP" department and will receive a call on Monday


seems the link is broken once telkom connects internationally ???



Tracing route to 213-155-155-233.customer.teliacarrier.com [213.155.155.233]
over a maximum of 30 hops:

1 * * * Request timed out.
2 67 ms 80 ms 48 ms 172.16.3.5
3 49 ms 69 ms 39 ms 172.16.3.129
4 97 ms 89 ms 89 ms ndn-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.7.7
3]
5 279 ms 278 ms 270 ms lon-ip-dir-stacker-pos-4-0-0-5.telkom-ipnet.co.z
a [196.43.9.102]
DEAL BREAKER BELOW
6 410 ms 419 ms 459 ms ffm-b10-link.telia.net [195.12.255.217]
7 391 ms 389 ms 409 ms ffm-bb1-link.telia.net [80.91.247.184]
8 488 ms 429 ms 419 ms hbg-bb1-link.telia.net [213.155.135.227]
9 437 ms 519 ms 489 ms adm-bb1-link.telia.net [80.91.253.140]
10 452 ms 429 ms 409 ms adm-b5-link.telia.net [213.155.132.159]
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.

[Nitrate]

Dear 8ta rep ,

this is becoming unacceptable , its been more than 1 week and I have yet to hear or receive any phone call from 8ta... I am getting the worst speed and ping latency in the evenings. last night was no expection as i was hitting 900 -1000ms ping .. this is really not the way to do business. If there is an issue (which obviously there is ) I expect some kind of support from 8ta... NOT JUST A MSG FROM YOU SAYING THE ISSUE HAS BEEN ESCALATED....

how can the network go from ok to very bad in such a short time . please get me some sort of help or atleast an answer/explination.. SHOW ME YOU CARE ATLEAST...

I compliment 8ta when they do something good and also expect me to 8!tch about it when stuff goes wrong as this is the only way you guys can fix issues.

[Draconia2]

Dear 8ta rep ,

this is becoming unacceptable , its been more than 1 week and I have yet to hear or receive any phone call from 8ta... I am getting the worst speed and ping latency in the evenings. last night was no expection as i was hitting 900 -1000ms ping .. this is really not the way to do business. If there is an issue (which obviously there is ) I expect some kind of support from 8ta... NOT JUST A MSG FROM YOU SAYING THE ISSUE HAS BEEN ESCALATED....

how can the network go from ok to very bad in such a short time . please get me some sort of help or atleast an answer/explination.. SHOW ME YOU CARE ATLEAST...

I compliment 8ta when they do something good and also expect me to 8!tch about it when stuff goes wrong as this is the only way you guys can fix issues.

its been the same for me as well.... sigh, right before i typed this message all my sites went down, its like its getting worse ?? i couldnt get onto mybb until i restarted everything. its not the modem, nor is it my pc.

[Xarog]

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]

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]

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 Mobile]

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]

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]

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

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]

15 minutes later...

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]

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]

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]

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