High latency to JHB servers

[raptorgeezus]

I've had a look around the forums for similar topics but nothing quite the same as my issue...

For the last few weeks I've had a weirdly high ping to JHB servers (usually 30ms) now a stable 180ms (I'm in CT).
However pings to CT servers are the same. I have a 10mbps line managed by axxess. Called multiple times, no joy, they've logged a fault with Telkom so long. I just wanted to ask you gurus what you thought?

In troubleshooting I've tried the following:

Tried multiple ISPs/devices and the same issue, however when I use telkom guest account I get the old 30ms ping.

I've disabled every device except the computer I run the test off, I've got NetLimiter monitoring for anything running in the background.

I've got an ASUS RT N13U with DD-WRT firmware.

Is there anything I'm missing? Is it just telkom being telkom?

Any help would be appreciated.
Cheers

 

[Tinuva]

List the ISPs you have tried, and show traceroutes to the affected servers with extra high latency. Pretty certain Axxess would need this information as well, before they can look at it for you.

 

[raptorgeezus]

This is using my default axxess unshaped account.

C:\Users\RaptorJesus>tracert 41.0.11.164

Tracing route to 41.0.11.164 over a maximum of 30 hops

1 1 ms <1 ms <1 ms DD-WRT [192.168.1.1]
2 * * * Request timed out.
3 146 ms 224 ms 295 ms 41.181.54.85
4 8 ms 7 ms 7 ms ipc-recieve-tb-2a.mtnbusiness.net [41.181.54.86]
5 8 ms 8 ms 9 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
6 8 ms 7 ms 7 ms unc-cpt-1.mtnns.net [196.44.18.8]
7 7 ms 7 ms 7 ms tb-pr-1.za--tb-cr-2.za-a.mtnns.net [196.44.18.143]
8 * * * Request timed out.
9 161 ms 161 ms 161 ms 196.43.25.205
10 175 ms 175 ms 175 ms 196.43.39.74
11 179 ms 178 ms 178 ms vodacom-gw.telkom-ipnet.co.za [196.25.253.110]
12 177 ms 174 ms 175 ms 41.0.0.33
13 174 ms 174 ms 174 ms 41.0.0.33
14 200 ms 200 ms 201 ms 41.0.11.164

Trace complete.


Any help/ideas?

 

[Johnatan56]

Looks like your exchange/line fault. Can you post line stats? Better hope the line is at fault and not the exchange.

 

[raptorgeezus]

Not exactly sure how to get line stats, is this what you are looking for:

Connection Status Connected
Us Rate (Kbps) 951
Ds Rate (Kbps) 10235
US Margin 5
DS Margin 12
Trained Modulation ADSL_2plus
LOS Errors 0
DS Line Attenuation 28
US Line Attenuation 12
Peak Cell Rate 2242 cells per sec
CRC Rx Fast 307
CRC Tx Fast 4
CRC Rx Interleaved 0
CRC Tx Interleaved 0
Path Mode Fast Path

 

[Tinuva]

No his exchange is fine. His line is fine.

What is your IP address at the time of doing the traceroute? You can get it from a website like http://www.tracemyip.org/
You can leave out the last part of the ip address, give it like: 41.181.51.x

I assume your problem is, SAIX/Vodacom is not accepting a certain prefix from MTN on their local peering links. If this assumption is correct, you will have to give the technical details to Axxess and have them escalate to MTN. Only way you will get it fixed now, or you will have to pray one day it gets fixed.