8ta needs to see this - Proof that the latency problem is internal!

xera

xera

Expert Member
Joined
Jun 15, 2007
Messages
2,158
Everyone, just do a tracert and paste it here (open cmd)...

See the first ping? It's low! And proof that I have signal, and that the problem is on their side.
So - 8ta, don't tell me that I need to email you my physical address, IMEI number, etc. This is YOUR problem, not mine.

Test #1
Code: 
C:\>tracert mybroadband.co.za

Tracing route to mybroadband.co.za [41.203.21.137]
over a maximum of 30 hops:

  1     *        *        *     Request timed out.
[COLOR="#008000"]  2    86 ms    89 ms    89 ms  172.16.2.5
  3    68 ms    70 ms    79 ms  172.16.2.129[/COLOR]
  4   498 ms   499 ms   469 ms  wbs-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.4.1
17]
  5   478 ms   539 ms   549 ms  196.43.11.218
  6   659 ms   589 ms   509 ms  196.43.25.206
  7   578 ms   609 ms   569 ms  ge0-3.br2.cpt1.za.mtnbusiness.net [196.7.8.206]

  8   518 ms   579 ms   579 ms  vlan9.hr3.jnb6.za.mtnbusiness.net [196.30.156.13
6]
  9   559 ms   499 ms   519 ms  core-router1.jnb2.host-h.net [196.30.213.108]
 10   569 ms   589 ms   599 ms  41.72.136.53
 11   658 ms   639 ms   639 ms  mybroadband.co.za [41.203.21.137]

Trace complete.

Test #2
Code: 
C:\>tracert mybroadband.co.za

Tracing route to mybroadband.co.za [41.203.21.137]
over a maximum of 30 hops:

  1     *        *        *     Request timed out.
[COLOR="#008000"]  2    64 ms    59 ms    59 ms  172.16.2.5
  3    68 ms    59 ms    59 ms  172.16.2.129[/COLOR]
  4   808 ms   789 ms   789 ms  wbs-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.4.1
17]
  5   478 ms   459 ms   479 ms  196.43.11.218
  6   528 ms   549 ms   549 ms  196.43.25.206
  7   789 ms   749 ms   759 ms  ge0-3.br2.cpt1.za.mtnbusiness.net [196.7.8.206]

  8   589 ms   549 ms   500 ms  vlan9.hr3.jnb6.za.mtnbusiness.net [196.30.156.13
6]
  9   449 ms   509 ms   429 ms  core-router1.jnb2.host-h.net [196.30.213.108]
 10   498 ms   479 ms   490 ms  41.72.136.53
 11   749 ms   739 ms   819 ms  mybroadband.co.za [41.203.21.137]

Trace complete.
 
F

francoislr

Expert Member
Joined
Apr 17, 2008
Messages
1,190
Yeah, you should maybe Tracert to their website, not some rogue media site from the formerly free republic of SA:p
 
H

Hogrod

Expert Member
Joined
Mar 24, 2005
Messages
1,869
Great find Xera. Will run a check tonight, I can't believe that if it is the case, and how can 8ta not see this?
 
E

Effjh

Well-Known Member
Joined
Nov 11, 2011
Messages
131
Speeds will be fine again now until 6pm tonight. The constant here for the last week has been great ping and speeds up until 6pm - 12am. Wait for tonight when it goes tits up again to tracert. Also xera it is worth emailing 8ta these tracert tests that you did since their techs cant seem to figure it out for themselves.
 
J

Just call me Dave

Member
Joined
Nov 20, 2011
Messages
19
sorry for being such a noob guys..
but is there anybody who can give me a quick step by step on how to do this.

So that i can also take it up with 8ta
 
J

Just call me Dave

Member
Joined
Nov 20, 2011
Messages
19
Ok i now know how to do this.
Could anybody just give me a brief overview on
what those mean exactly to me.
How do i know that the problem is from 8ta in the 1st place
Like the OP posted??

Sorry again for my noobness :D
 
xera

xera

Expert Member
Joined
Jun 15, 2007
Messages
2,158
I want my ping of 40ms back!

francoislr said:
Yeah, you should maybe Tracert to their website, not some rogue media site from the formerly free republic of SA:p
Click to expand...

Haha.. Point is that 8ta themselves should be able to grab a dongle in the problem area, do the tracert to whatever websites they want, and find and fix the problem.
All this thread is doing, is showing that:
  1. I have a dongle that supports HSPA. (Therefore, my IMEI number(s) are not required)
  2. I have signal, and the light blue light is on. (Therefore, my location is not a problem)
  3. First few hops of the tracert are fine. (Therefore, the problem is not the technology on my side: it is not my hardware, software, firewall, or antivirus.)

I am aware that 8ta must ask those questions, in order to troubleshoot. But, in this case there are numerous users who have reported shocking speeds and latencies recently... Yet, when they first got their dongles, their speeds and latencies were fine!
So 8ta please. Stop calling us all noobs, and look at the tracert's instead:

@The_Librarian:

www.pingtest.net
Code: 
C:\>tracert www.pingtest.net

Tracing route to www.pingtest.net [74.209.160.10]
over a maximum of 30 hops:

  1     *        *        *     Request timed out.
[COLOR="#008000"]  2    62 ms    70 ms    80 ms  172.16.2.5
  3    69 ms    79 ms    69 ms  172.16.2.129
  4    68 ms    60 ms    59 ms  wbs-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.251.125][/COLOR]
  5   268 ms   229 ms   229 ms  lon-ip-dir-telecity-pos-7-0-2.telkom-ipnet.co.za [196.43.9.150]
  6   539 ms   509 ms   599 ms  ge9-16.br02.ldn01.pccwbtn.net [63.218.13.13]
  7   399 ms   399 ms   389 ms  netriver.ge2-16.br01.sea01.pccwbtn.net [63.216.14.162]
  8   389 ms   409 ms   409 ms  static-74-209-160-10.lynnwood.netriver.net [74.209.160.10]

Trace complete.

www.speedtest.net:
Code: 
C:\>tracert www.speedtest.net

Tracing route to www.speedtest.net [74.209.160.12]
over a maximum of 30 hops:

  1     *        *        *     Request timed out.
[COLOR="#008000"]  2   100 ms    59 ms    60 ms  172.16.2.5
  3    61 ms    57 ms    80 ms  172.16.2.129
  4    68 ms    59 ms    59 ms  wbs-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.4.117][/COLOR]
  5   238 ms   239 ms   229 ms  196.43.18.102
  6   428 ms   409 ms   389 ms  ge9-16.br02.ldn01.pccwbtn.net [63.218.13.13]
  7   379 ms   379 ms   379 ms  netriver.ge2-16.br01.sea01.pccwbtn.net [63.216.14.162]
  8   369 ms   369 ms   369 ms  static-74-209-160-12.lynnwood.netriver.net [74.209.160.12]

Trace complete.

www.telkom.co.za
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    57 ms    61 ms    59 ms  172.16.2.1
  3    76 ms    79 ms    70 ms  172.16.2.129
  4    69 ms    59 ms    69 ms  wbs-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.251.125]
  5    88 ms   109 ms    80 ms  196.43.39.166
  6    90 ms    89 ms    79 ms  rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.43.23.6]
  7    88 ms    89 ms   129 ms  nbsc-ip-bssr-1-atm-5-0-0-1.telkom-ipnet.co.za [196.43.23.30]
  8   118 ms    89 ms   109 ms  nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za [196.43.22.222]

Trace complete.

www.8ta.co.za
Code: 
C:\>tracert www.8ta.co.za

Tracing route to www.8ta.co.za [165.143.158.47]
over a maximum of 30 hops:

  1     *        *        *     Request timed out.
  2    86 ms    69 ms    60 ms  172.16.2.1
  3    59 ms    60 ms    60 ms  172.16.2.129
  4    68 ms    69 ms    59 ms  wbs-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.4.117]
  5    98 ms   109 ms    99 ms  196.43.51.78
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8     *     telkom-sa-tienet-gw.telkom-ipnet.co.za [196.25.54.62]  reports: Destination net unreachable.

Trace complete.

Those of you who don't know how to copy out of cmd:

Use the context menu.
Right click, select Mark.... drag mouse up and down to mark.
Finally press Enter to copy.
:)
 
K

K-BeAnZ

Member
Joined
Feb 17, 2009
Messages
16
xera said:
Haha.. Point is that 8ta themselves should be able to grab a dongle in the problem area, do the tracert to whatever websites they want, and find and fix the problem.
All this thread is doing, is showing that:
  1. I have a dongle that supports HSPA. (Therefore, my IMEI number(s) are not required)
  2. I have signal, and the light blue light is on. (Therefore, my location is not a problem)
  3. First few hops of the tracert are fine. (Therefore, the problem is not the technology on my side: it is not my hardware, software, firewall, or antivirus.)

I am aware that 8ta must ask those questions, in order to troubleshoot. But, in this case there are numerous users who have reported shocking speeds and latencies recently... Yet, when they first got their dongles, their speeds and latencies were fine!
So 8ta please. Stop calling us all noobs, and look at the tracert's instead:

@The_Librarian:

www.pingtest.net
Code: 
C:\>tracert www.pingtest.net

Tracing route to www.pingtest.net [74.209.160.10]
over a maximum of 30 hops:

  1     *        *        *     Request timed out.
[COLOR="#008000"]  2    62 ms    70 ms    80 ms  172.16.2.5
  3    69 ms    79 ms    69 ms  172.16.2.129
  4    68 ms    60 ms    59 ms  wbs-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.251.125][/COLOR]
  5   268 ms   229 ms   229 ms  lon-ip-dir-telecity-pos-7-0-2.telkom-ipnet.co.za [196.43.9.150]
  6   539 ms   509 ms   599 ms  ge9-16.br02.ldn01.pccwbtn.net [63.218.13.13]
  7   399 ms   399 ms   389 ms  netriver.ge2-16.br01.sea01.pccwbtn.net [63.216.14.162]
  8   389 ms   409 ms   409 ms  static-74-209-160-10.lynnwood.netriver.net [74.209.160.10]

Trace complete.

www.speedtest.net:
Code: 
C:\>tracert www.speedtest.net

Tracing route to www.speedtest.net [74.209.160.12]
over a maximum of 30 hops:

  1     *        *        *     Request timed out.
[COLOR="#008000"]  2   100 ms    59 ms    60 ms  172.16.2.5
  3    61 ms    57 ms    80 ms  172.16.2.129
  4    68 ms    59 ms    59 ms  wbs-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.4.117][/COLOR]
  5   238 ms   239 ms   229 ms  196.43.18.102
  6   428 ms   409 ms   389 ms  ge9-16.br02.ldn01.pccwbtn.net [63.218.13.13]
  7   379 ms   379 ms   379 ms  netriver.ge2-16.br01.sea01.pccwbtn.net [63.216.14.162]
  8   369 ms   369 ms   369 ms  static-74-209-160-12.lynnwood.netriver.net [74.209.160.12]

Trace complete.

www.telkom.co.za
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    57 ms    61 ms    59 ms  172.16.2.1
  3    76 ms    79 ms    70 ms  172.16.2.129
  4    69 ms    59 ms    69 ms  wbs-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.251.125]
  5    88 ms   109 ms    80 ms  196.43.39.166
  6    90 ms    89 ms    79 ms  rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.43.23.6]
  7    88 ms    89 ms   129 ms  nbsc-ip-bssr-1-atm-5-0-0-1.telkom-ipnet.co.za [196.43.23.30]
  8   118 ms    89 ms   109 ms  nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za [196.43.22.222]

Trace complete.

www.8ta.co.za
Code: 
C:\>tracert www.8ta.co.za

Tracing route to www.8ta.co.za [165.143.158.47]
over a maximum of 30 hops:

  1     *        *        *     Request timed out.
  2    86 ms    69 ms    60 ms  172.16.2.1
  3    59 ms    60 ms    60 ms  172.16.2.129
  4    68 ms    69 ms    59 ms  wbs-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.4.117]
  5    98 ms   109 ms    99 ms  196.43.51.78
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8     *     telkom-sa-tienet-gw.telkom-ipnet.co.za [196.25.54.62]  reports: Destination net unreachable.

Trace complete.

Those of you who don't know how to copy out of cmd:

Use the context menu.
Right click, select Mark.... drag mouse up and down to mark.
Finally press Enter to copy.
:)
Click to expand...
They over sold,now they dont have enough capacity damn pricks !!!
 
H

Hogrod

Expert Member
Joined
Mar 24, 2005
Messages
1,869
Here's mine. Back to dialup

Tracing route to www.8ta.co.za [165.143.158.47]
over a maximum of 30 hops:

1 * * * Request timed out.
2 36 ms 39 ms 29 ms 172.16.2.1
3 35 ms 39 ms 39 ms 172.16.2.129
4 916 ms 869 ms 849 ms wbs-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.4.117]
5 807 ms 878 ms 889 ms 196.43.51.78
6 * telkom-sa-tienet-gw.telkom-ipnet.co.za [196.25.54.62] reports: Destination net unreachable.
 
B

b1tbyte

New Member
Joined
Oct 9, 2011
Messages
5
Ditto. This is becoming too frequent.

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

1 3 ms 3 ms 3 ms 192.168.0.1
2 * * * Request timed out.
3 77 ms 49 ms 49 ms 172.16.2.5
4 100 ms 49 ms 49 ms 172.16.2.129
5 750 ms 779 ms 810 ms wbs-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.251.125]
6 1158 ms 1099 ms 1029 ms 196.43.11.218
7 934 ms 969 ms 899 ms 196.43.25.206
8 854 ms 919 ms 879 ms 197-84-4-22.cpt.mweb.co.za [197.84.4.22]
9 848 ms 789 ms 819 ms vlan11.cpt-hscore-1.mweb.co.za [196.28.178.99]
10 727 ms 679 ms 739 ms 196-28-178-34.adsl.mweb.co.za [196.28.178.34]
11 1017 ms 1010 ms 978 ms www.mweb.co.za [196.2.63.110]
Trace complete.


The problem is definitely at the wbs-ip-hsll-1-wan.telkom-ipnet.co.za (196.25.251.125) hop

I wonder what could be happening here? Perhaps 8ta runs its "cap" from saix for the day and gets throttled?

Only joking..!

Whatever the reason: 8ta please sort this out!
 
J

Just call me Dave

Member
Joined
Nov 20, 2011
Messages
19
So these are my results.
I spoke to someone today from 8ta.
Amod, he was extremely helpful.
When i asked about the inconsistent latencies.
He checked with the floor manager if they were aware of
any on going problems. Currently they don't see a problem
and i was told that it could be traffic etc etc....
which to be honest i think is a total load of hogwash...
I mean come on... how does your ping (ingame) go from
between 35 to 100 suddenly rise to a ridiculously high ping of up to
6000!!!!! I cant and refuse to believe that is all caused by traffic.
How do i get 1 month of excellent service with the exception of a day during the
week go to (i am now on my 4th night of this *****) complete rubbish.

I explained to him that i would understand that if it was perhaps
a tower or some rubbish that broke down it would be completely understandable if
it broke and they were making an effort to fix it because that would mean that there
would be light at the end of the tunnel in the near future....
It doesnt seam that there is....

anyways here are my results..

70123948.jpg
[/URL] Uploaded with ImageShack.us[/IMG]
 
Xarog

Xarog

Honorary Master
Joined
Feb 13, 2006
Messages
19,039
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    58 ms    59 ms    59 ms  172.16.2.5
  3    67 ms    59 ms    59 ms  172.16.2.129
  4   905 ms   917 ms   857 ms  wbs-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.4.117]
  5   899 ms   867 ms   867 ms  196.43.39.162
  6  1013 ms   997 ms  1027 ms  rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.43.23.6]
  7   757 ms   788 ms   814 ms  nbsc-ip-bssr-1-atm-5-0-0-1.telkom-ipnet.co.za [196.43.23.30]
  8   870 ms   907 ms   917 ms  nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za [196.43.22.222]

Trace complete.

Code: 
C:\>tracert www.8ta.co.za

Tracing route to www.8ta.co.za [165.143.158.47]
over a maximum of 30 hops:

  1     *        *        *     Request timed out.
  2    54 ms    59 ms    59 ms  172.16.2.5
  3    54 ms    79 ms    59 ms  172.16.2.129
  4   933 ms   896 ms   927 ms  wbs-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.4.117]
  5  1072 ms  1106 ms  1027 ms  nbsc-ip-er-1-pos-8-0-0.telkom-ipnet.co.za [196.43.25.146]
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8  telkom-sa-tienet-gw.telkom-ipnet.co.za [196.25.54.62]  reports: Destination
 net unreachable.

Trace complete.
 
Deezil

Deezil

Senior Member
Joined
Mar 9, 2008
Messages
790
5:30 in the morning from Pierre van Ryneveld area ... will do another tonight during peak traffic

Code: 
C:\>tracert 8ta.co.za

Tracing route to 8ta.co.za [165.143.158.47]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3    94 ms    89 ms    78 ms  172.16.1.5
  4   108 ms    89 ms    79 ms  172.16.1.129
  5   106 ms    89 ms    79 ms  tpr-ip-esr-6-wan.telkom-ipnet.co.za [196.25.181.77]
  6    96 ms    99 ms    99 ms  nbsc-ip-er-1-pos-8-0-0.telkom-ipnet.co.za [196.43.25.146]
  7  telkom-sa-tienet-gw.telkom-ipnet.co.za [196.25.54.62]  reports: Destination net unreachable.

Trace complete.

Code: 
C:\>tracert speedtest.net

Tracing route to speedtest.net [74.209.160.12]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3    76 ms    89 ms    79 ms  172.16.1.1
  4    87 ms    89 ms    79 ms  172.16.1.129
  5    68 ms    89 ms    79 ms  tpr-ip-esr-6-wan.telkom-ipnet.co.za [196.25.181.169]
  6   226 ms   239 ms   239 ms  hkg-ip-dir-hongkong-pos-5-0.telkom-ipnet.co.za [196.43.18.18]
  7   225 ms   239 ms   239 ms  ge13-42.br01.hkg04.pccwbtn.net [63.218.2.201]
  8   348 ms   379 ms   379 ms  netriver.ge2-16.br01.sea01.pccwbtn.net [63.216.14.162]
  9   375 ms   380 ms   389 ms  static-74-209-160-12.lynnwood.netriver.net [74.209.160.12]

Trace complete.
 
Last edited:
M

mysticMystic

Active Member
Joined
Jan 2, 2007
Messages
38
Mybroadband investigate perhaps?

Maybe the mybroadband team can investigate this and write an article on this problem?

Hopefully the journalist will be able to get a response from 8ta that will at least shake them into investigating.

I've given up trying to communicate with them.
 
ISP cash cow

ISP cash cow

Executive Member
Joined
Feb 10, 2011
Messages
6,369
I could have told you this from the start.

The only way 8-ta (telkom) would be able to get business is by lowering the price to a ridiculous amount. there service is crap and the amount of complaints and lack of answers is just typical of Telkom tactics.

IMO no matter the specials or deals 8-ta offer.. stay away from them. Let them sink along with their retarded parent company!
 
H

Hogrod

Expert Member
Joined
Mar 24, 2005
Messages
1,869
mysticMystic said:
Maybe the mybroadband team can investigate this and write an article on this problem?

Hopefully the journalist will be able to get a response from 8ta that will at least shake them into investigating.

I've given up trying to communicate with them.
Click to expand...

I sent a PM to RPM yesterday asking for some help if possible. It's the lack of feedback from 8ta that's frustrating. Not a care in the world.
 
shinji

shinji

Well-Known Member
Joined
Sep 18, 2008
Messages
483
Glad to see someone else also picked up on this issue.

How can pings be 45ms yet leave us with download speeds of 0.03mbps?

Will have to wait a week to see if things improve... :mad:
 
C

CraigViking

Well-Known Member
Joined
Oct 16, 2008
Messages
125
ISP cash cow said:
I could have told you this from the start.

The only way 8-ta (telkom) would be able to get business is by lowering the price to a ridiculous amount. there service is crap and the amount of complaints and lack of answers is just typical of Telkom tactics.

IMO no matter the specials or deals 8-ta offer.. stay away from them. Let them sink along with their retarded parent company!
Click to expand...

What a stupid post......if they sink WE ALL SINK no matter who you with they all related to telkom somehow.......
 
You must log in or register to reply here.
Top