8.ta, Your network is PATHETIC!

Effjh said:
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
Click to expand...

:twisted: Holy cow! Do you live ON the actual tower?
 
Hi all!

Thank you for all the tracerts and feedback. We are currently experiencing a higher than normal customer data usage which will affect throughput during busy hours. Network optimization is in progress which will address the issue. A resolve is expected by next week Wednesday (18/07/2012).

Apologies for the inconvenience

Regards,
Social Media Team
 
Last edited:
Below are three traces with different results:
First one ideal, second shows delay on 8ta network, third one complete unacceptable - 1.5s somewhere between 8ta and Telkom.
Location Gauteng Knoppieslaaghte (near Diepsloot). Cell ID 22222, signal -77dBm.
We have open reference, yesterday received call from Veronica informing that in 3 weeks threre will be new tower on this location. I asked for Cell ID, received my current Cell ID as an ID for new tower. Not sure that new tower is going to help with these unstable pings.

Code: 
C:\>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   165 ms    50 ms    39 ms  172.16.1.5
  3    44 ms    39 ms    39 ms  172.16.1.129
  4    42 ms    39 ms    49 ms  tpr-ip-esr-6-wan.telkom-ipnet.co.za [196.25.181.
77]
  5    41 ms    49 ms    69 ms  196.43.39.162
  6    39 ms    40 ms    39 ms  rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.4
3.23.6]
  7    38 ms    39 ms    39 ms  nbsc-ip-bssr-2-atm-5-0-0-1.telkom-ipnet.co.za [1
96.43.23.34]
  8    47 ms    48 ms     *     nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za [196.43
.22.222]
  9    48 ms    49 ms    39 ms  nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za [196.43
.22.222]

Trace complete.

C:\>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   359 ms   309 ms   349 ms  172.16.1.5
  3   277 ms   339 ms   379 ms  172.16.1.129
  4   275 ms   349 ms   319 ms  tpr-ip-esr-6-wan.telkom-ipnet.co.za [196.25.181.
77]
  5   303 ms   358 ms   329 ms  196.43.39.162
  6   300 ms   360 ms   369 ms  rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.4
3.23.6]
  7   768 ms   399 ms   319 ms  nbsc-ip-bssr-2-atm-5-0-0-1.telkom-ipnet.co.za [1
96.43.23.34]
  8     *      290 ms   339 ms  nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za [196.43
.22.222]

Trace complete.

C:\>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   320 ms   359 ms   349 ms  172.16.1.5
  3   308 ms   369 ms   359 ms  172.16.1.129
  4   356 ms   337 ms  1439 ms  tpr-ip-esr-6-wan.telkom-ipnet.co.za [196.25.181.
77]
  5   347 ms   370 ms   388 ms  196.43.39.162
  6   351 ms   339 ms   359 ms  rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.4
3.23.6]
  7   278 ms   369 ms   379 ms  nbsc-ip-bssr-2-atm-5-0-0-1.telkom-ipnet.co.za [1
96.43.23.34]
  8   297 ms   369 ms   389 ms  nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za [196.43
.22.222]

Trace complete.
 
Mine is also up the pipe again. Was hoping to watch this weekend's rugby but 8ta disappointing me once again... Should learn not to get my hopes up with these guys.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X