Telkom says nothing is wrong, but...

M

Mr Anderson

Well-Known Member
Joined
Oct 29, 2005
Messages
272
Reaction score
0
I phoned Telkom and reported that there is a huge latency issue at the moment even with SAIX users like myself. The said there's nothing wrong on their side but look at this...

Tracert to saix.net:

Tracing route to saix.net [196.25.1.200]
over a maximum of 30 hops:

1 * * * Request timed out.
2 22 ms 21 ms 19 ms dsl-146-64-01.telkomadsl.co.za [165.146.64.1]
3 126 ms 132 ms 143 ms rrba-ip-er-1-fe-3-0-0-1.telkom-ipnet.co.za [196.
43.10.145]
4 372 ms 389 ms 392 ms wblv-ip-essr-1-atm-2-0-0-2.telkom-ipnet.co.za [1
96.43.11.30]
5 374 ms 389 ms 384 ms saix.net [196.25.1.200]

Trace complete.

Check the Pings out...

Pinging saix.net [196.25.1.200] with 32 bytes of data:

Reply from 196.25.1.200: bytes=32 time=425ms TTL=249
Reply from 196.25.1.200: bytes=32 time=293ms TTL=249
Reply from 196.25.1.200: bytes=32 time=370ms TTL=249
Reply from 196.25.1.200: bytes=32 time=356ms TTL=249

Ping statistics for 196.25.1.200:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 293ms, Maximum = 425ms, Average = 361ms


As you can clearly see in the tracert there is a problem and it start within the Telkom IP Network. The funny thing is, they don't have a CLUE - as always.
 
Log a call make sure they come out run the tracert infront of them and say "WTF it was 20ms last night!!??".
 
Dont report this to Telkom, report it to your ISP.

Something is up though, I am getting packet loss and **** ping times, even on an IS account.
 
Last edited:
WebAfrica threw this at telkom...once again I'm getting the run-around.
 
This is a message I sent to my ISP, they asked me to give ping results from different regions to ftp.is.co.za anyways it should give the just of the problem, I did quite a few tests. There are also IS to IS problems
============================================================
Hi There

It has come to my attention over the past few days that the pings and
speeds between IS and SAIX users is absolutely shocking, I do not know
whether this is a IS problem (I think it is though from my testing), a
SAIX problem or a Telkom cause. This problem does not apply to all
addresses on the IS networks range, I managed to find about 2
addresses out of 15 that did not give me a problem, I conducted the
same tests within my town and to people in johannesburg and cape town
(I live in Kwa-Zulu Natal) and gotten the same results, thus I have
ruled out it being a regional error, direct transfers between pc's (be
it via http or ftp) the speeds are also drastically different (2KB/s
with IS vs 30KB/s with saix to a IS user). I have also ruled out time
of day as these results to not differ with results done at 1AM, these
were taken round about 9pm

I know its a lot of pings to look at but please bear with me.

It all started with a VPN to a friend of mine, here are the ping results...

This was with a capped account pinging the friend with a VPN's result,
I increased the wait time to 5000ms for the ping.
-------------------------------------------------------
Pinging 196.209.105.177 with 32 bytes of data:

Reply from 196.209.105.177: bytes=32 time=2103ms TTL=58
Reply from 196.209.105.177: bytes=32 time=2675ms TTL=58
Request timed out.
Reply from 196.209.105.177: bytes=32 time=4510ms TTL=58
-------------------------------------------------------
I also have a saix account, and this is the result, last months pings
showed in the 70-100ms result under the same conditions though.

-------------------------------------------------------
Pinging 196.209.105.177 with 32 bytes of data:

Reply from 196.209.105.177: bytes=32 time=795ms TTL=52
Reply from 196.209.105.177: bytes=32 time=508ms TTL=52
Reply from 196.209.105.177: bytes=32 time=509ms TTL=52
Reply from 196.209.105.177: bytes=32 time=508ms TTL=52
-------------------------------------------------------

Now if I switch to uncapped the result changes.

IS (uncapped)
--------------------------------------------------------
Pinging 196.209.105.177 with 32 bytes of data:

Reply from 196.209.105.177: bytes=32 time=60ms TTL=58
Reply from 196.209.105.177: bytes=32 time=59ms TTL=58
Reply from 196.209.105.177: bytes=32 time=60ms TTL=58
Reply from 196.209.105.177: bytes=32 time=60ms TTL=58
--------------------------------------------------------

Now granted thats a peer connection, so I tested to a actual machine
hosted by IS, no problems with capped or uncapped, same results.

IS
----------------------------------------------------------
Pinging 196.36.190.110 with 32 bytes of data:

Reply from 196.36.190.110: bytes=32 time=51ms TTL=53
Reply from 196.36.190.110: bytes=32 time=50ms TTL=53
Reply from 196.36.190.110: bytes=32 time=50ms TTL=53
Reply from 196.36.190.110: bytes=32 time=49ms TTL=53
----------------------------------------------------------
SAIX
----------------------------------------------------------

Pinging 196.36.190.110 with 32 bytes of data:

Reply from 196.36.190.110: bytes=32 time=50ms TTL=54
Reply from 196.36.190.110: bytes=32 time=48ms TTL=54
Reply from 196.36.190.110: bytes=32 time=47ms TTL=54
Reply from 196.36.190.110: bytes=32 time=66ms TTL=54
----------------------------------------------------------

Note the lack of a problem at all.
-------------------
-------------------

There are a lot of users wondering what is causing this and I was
wondering if you could explain the result to me so that I can convey
it to all the people I know who are affected, (which are about 80% of
the people that have IS accounts that I know)

I dont think IS can give the excuse of a user being capped having less
rights as it is within their own network and they agreed to give their
users up to 30 gigs total traffic. I could understand if it was from
IS to SAIX as that crosses networks.
 
Well as of about 16:30 things started to look up again...the pings dropped by about 50% and were sitting at 100ms....about 10 minutes later...they were sitting at 50ms....so somewhere something went wrong, somebody finally noticed and started to fix it. Stoopid freaking ADSL...

I'm not going to blame Telkom, I'm not going to blame WebAfrica...I'm now blaming the whole freaking package as a whole...ADSL Sucks!
 
Mr Anderson said:
Well as of about 16:30 things started to look up again...the pings dropped by about 50% and were sitting at 100ms....about 10 minutes later...they were sitting at 50ms....so somewhere something went wrong, somebody finally noticed and started to fix it.
Click to expand...

HAH!
My side is still slow slow slow ...
 
It has been happening tome now the whole week. During the day latency of between 250ms to 450ms up until 5pm. After that almost instantly the ping plummet to 60ms. My thinking is they are giving preference to the business accounts and somehow routing the home traffic through slow pathes to ensure businesses are not moaning about slow response.
 
so by all the complaining I guess I should move to vodacoms new HSDPA wireless service?

is it worth it? than to get ADSL 512 again?
 
Aspersie...

Latency on HSDPA is still 500ms+...don't fall for the martketing schemes. If you're a gamer then HSDPA is NOT for you, despite what they try and rub off on you.
 
Well, at the moment, If you're a gamer, adsl isn't an option either. :(
 
what new 1mb line?

1024k lines from telkom are 1mb lines, btw. I can only think that the line you're talking about is 100mb or 1gb.

Either way, some clarification would be appreciated. :)
 
Xarog said:
Well, at the moment, If you're a gamer, adsl isn't an option either. :(
Click to expand...

LOL! you're right. Should have said that myself.

How the HECK am I supposed to earn my expert sniper badge in BF2 with lag?!?!? it can't be done I tell you!!
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X