Hummercellc
Expert Member
- Joined
- Jan 6, 2008
- Messages
- 3,451
Anyone else seeing high local latency?
Currently seeing 400ms :wtf:
Currently seeing 400ms :wtf:
Latency is very high in the Cape.... May be a Telkom issue, as the only ISP account that doesn't seem to be affected as much is my MWEB account.
Out of ALL the accounts I have (Telkom, MWEB, Axxess, Afrihost, WebAfrica), my AH accounts are the worst - 60ms to 150ms to Cape Town server (previously 11ms) and JHB 180ms to 240ms (previously 28ms).
Even my Axxess account (MTN with same routing as AH) has lower latency 40ms (CPT) and 60ms (JHB).
This cannot be exchange congestion, as ALL traces are normal, and this happens at any time in the day/night randomly. I then suffer lots of time-outs, periods of no throughput, high page load times, and sometimes certain sites are not available at all.
Anyone else seeing high local latency?
Currently seeing 400ms :wtf:
I understand your point.
But there is a definite difference in the performance of my line since 11 Febraury - from Google play store downloads/updates, playstation and xbox updates, browsing, http downloads and p2p have all been affected. And it is usually always between about 6 pm and 10 pm at night and over the week end.
i.e. my line is most definitely not performing as it did before 11 February - speed tests were around 3,3 mbps any time of day, well seeded ( single) p2p downloads would be running at about 320 kB/s no problem ( sometimes even up to 400 kB/s), Google play store would update at about 400 kB/s, connection speed tests on playstation and xbox would show as 3,2 mbps ( mostly), you get picture.
Based on my own previous experience before 11 February, there is something seriously wrong.
Bought a new router ( to have one spare) which i used test - same story.
Tried new cables, New pots filter, with and without pots filter, wireless and cable.
So hopefully, if the Telkom fault is causing all this, it can be sorted out asap.
Where are you seeing the increased latency?
Could you post a traceroute possibly?
Latency is very high in the Cape.... May be a Telkom issue, as the only ISP account that doesn't seem to be affected as much is my MWEB account.
Out of ALL the accounts I have (Telkom, MWEB, Axxess, Afrihost, WebAfrica), my AH accounts are the worst - 60ms to 150ms to Cape Town server (previously 11ms) and JHB 180ms to 240ms (previously 28ms).
Even my Axxess account (MTN with same routing as AH) has lower latency 40ms (CPT) and 60ms (JHB).
This cannot be exchange congestion, as ALL traces are normal, and this happens at any time in the day/night randomly. I then suffer lots of time-outs, periods of no throughput, high page load times, and sometimes certain sites are not available at all.
Traceroute output:
1 * * *
2 41.181.221.213 (41.181.221.213) 369.723 ms 334.583 ms 434.377 ms
3 41.181.221.214 (41.181.221.214) 293.836 ms 337.598 ms 338.600 ms
4 rb-dca-2.za--qux-b.za.mtnbusiness.net (41.181.165.118) 293.102 ms 366.924 ms 298.797 ms
5 rb-cr-1.za--rb-dca-2.mtnns.net (196.44.31.122) 334.915 ms 332.369 ms 360.235 ms
6 jh-dca-2.za--jh-cr-1.za-a.mtnns.net (196.44.0.221) 338.250 ms 338.750 ms 338.780 ms
7 196.31.220.12 (196.31.220.12) 283.575 ms 290.300 ms 287.001 ms
8 196.31.220.25 (196.31.220.25) 298.577 ms 306.242 ms 303.427 ms
9 196.31.63.206 (196.31.63.206) 305.741 ms 315.034 ms 314.156 ms
10 vl9-ah-ha-2.za.mtnbusiness.net (196.30.42.133) 315.826 ms 309.712 ms 317.343 ms
11 cms-gm.afrihost.com (197.242.144.102) 324.229 ms 333.972 ms 338.424 ms
Mweb and Telkom account are fine, so it's not my exchange.
Would you mind testing your connection using those account details that I sent to you last night. Something is definitely not right.
Better than my accounts, but not great...
Tracing route to afrihost.com [197.242.144.102]
over a maximum of 30 hops:
1 * * * Request timed out.
2 258 ms 305 ms 233 ms 41.181.221.213
3 207 ms 202 ms 207 ms 41.181.221.214
4 191 ms 205 ms 195 ms rb-dca-2.za--qux-b.za.mtnbusiness.net [41.181.165.118]
5 209 ms 208 ms 204 ms rb-dca-2.za--rb-cr-1.mtnns.net [196.44.31.122]
6 207 ms 199 ms 204 ms jh-dca-2.za--jh-cr-1.za-a.mtnns.net [196.44.0.221]
7 224 ms 194 ms 192 ms 196.30.1.53
8 230 ms 219 ms 226 ms 196.31.220.25
9 230 ms 216 ms 215 ms 196.31.63.206
10 198 ms 197 ms 201 ms vl9-ah-ha-2.za.mtnbusiness.net [196.30.42.133]
11 213 ms 213 ms 213 ms cms-gm.afrihost.com [197.242.144.102]
IS Account
Tracing route to webafrica.co.za [41.185.61.34]
over a maximum of 30 hops:
1 * * * Request timed out.
2 14 ms 14 ms 14 ms 196.38.74.246
3 18 ms 19 ms 18 ms cdsl1-umh-gi0-0-0-3102.ip.isnet.net [196.38.74.245]
4 18 ms 18 ms 18 ms 196.26.210.200
5 25 ms 25 ms 23 ms 196.38.74.176
6 45 ms 43 ms 43 ms cdsl1-ctn-cdsl1-rba.ip.isnet.net [196.38.72.159]
7 44 ms 43 ms 43 ms wa-is.isdsl.net [196.38.72.84]
8 43 ms 43 ms 42 ms wnls-hr2-vl-140.wa.co.za [41.185.1.1]
9 43 ms 43ms 42ms ms wnls-whmcs-web03.wadns.net [41.185.61.34]
Trace complete.
When I last checked demand in the East, we were performing within range but the tests you're showing here seem consistent with when the network is under strain. I'll have to get confirmation if that is the case, at this point I don't have any info pointing to that. I'll check our graphs and see what they say![]()
I have a feeling I am not routing through the Durban IPC, I am going via Joburg or Cape Town, for some unknown reason.
I PM'ed AfriGenie Last night about this....
We definitely have an IPC in Durban, but the routing shows JH for some networking components in the signal chain, totally normal. The routing that is, the results you're seeing are definitely not normal, I've asked our network engineers to confirm what could be happening here![]()
:wtf:
That's definitely a strange one!
When next you notice the jump in latency, can you please run a traceroute to Afrihost.com and Google.com, I realize you said that the traceroutes appear normal, but we'll need to see those traceroutes to get an idea what is causing the latency.
Have you run any speedtests when the latency skyrockets?
C:\Users\cortexenslaver>tracert afrihost.com
Tracing route to afrihost.com [197.242.144.102]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms home.gateway.pace.net [192.168.1.254]
2 14 ms 9 ms 11 ms 105-236-13-129-esr-lo.mtnbusiness.co.za [105.236
.13.129]
3 8 ms 10 ms 8 ms ipc-recieve-tb-2a.mtnbusiness.net [41.181.54.86]
4 8 ms 8 ms 11 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.19
8.188]
5 17 ms 8 ms 9 ms compj-cpt-1.mtnns.net [196.44.18.2]
6 17 ms 9 ms 9 ms ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]
7 30 ms 29 ms 33 ms rb-cr-1.za--ct-cr-2.za.mtnns.net [196.44.31.69]
8 42 ms 30 ms 27 ms 196.44.31.97
9 66 ms 67 ms 52 ms 196.30.1.53
10 29 ms 38 ms 40 ms 196.31.220.25
11 33 ms 28 ms 28 ms 196.31.63.206
12 30 ms 29 ms 27 ms vl9-ah-ha-2.za.mtnbusiness.net [196.30.42.133]
13 27 ms 27 ms 27 ms cms-gm.afrihost.com [197.242.144.102]
Trace complete.
C:\Users\cortexenslaver>tracert webafrica.co.za
Tracing route to webafrica.co.za [41.185.61.34]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms home.gateway.pace.net [192.168.1.254]
2 16 ms 8 ms 14 ms 105-236-13-129-esr-lo.mtnbusiness.co.za [105.236
.13.129]
3 12 ms 15 ms 21 ms ipc-recieve-tb-2a.mtnbusiness.net [41.181.54.86]
4 48 ms 84 ms 23 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.19
8.188]
5 45 ms 44 ms 48 ms compj-cpt-1.mtnns.net [196.44.18.2]
6 63 ms 68 ms 63 ms ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]
7 12 ms 8 ms 13 ms 196.44.0.74
8 29 ms 9 ms 15 ms 41-208-29-209.mtnns.net [41.208.29.209]
9 14 ms 10 ms 10 ms css2-ctn-gi0-2.ip.isnet.net [168.209.6.15]
10 12 ms 11 ms 11 ms mi-za-cpt-br1-gi0-3-108.ip.isnet.net [168.209.28
.42]
11 10 ms 25 ms 30 ms 197.96.154.190
12 19 ms 22 ms 26 ms 197.96.154.191
13 26 ms 12 ms 13 ms wnls-whmcs-web02.wadns.net [41.185.61.34]
Trace complete.
C:\Users\cortexenslaver>tracert thinkbroadband.com
Tracing route to thinkbroadband.com [80.249.99.130]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms home.gateway.pace.net [192.168.1.254]
2 14 ms 11 ms 8 ms 105-236-13-129-esr-lo.mtnbusiness.co.za [105.236
.13.129]
3 9 ms 7 ms 8 ms ipc-send-tb-3a.mtnbusiness.net [41.181.53.214]
4 8 ms 11 ms 12 ms tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.18
4.28]
5 33 ms 11 ms 8 ms compj-cpt-1.mtnns.net [196.44.18.2]
6 167 ms 155 ms 154 ms ls-cr-2--tb-cr-1.uk-b.mtnns.net [196.44.31.113]
7 152 ms 177 ms 161 ms ls-pr-1.uk--ls-cr-2.uk-a.mtn.net [209.212.111.20
1]
8 166 ms 155 ms 206 ms linx-gw1.thn.ncuk.net [195.66.224.240]
9 152 ms 151 ms 152 ms te2-1-9.star10g.bdr-rt3.thdo.ncuk.net [80.249.97
.17]
10 153 ms 163 ms 153 ms te1-1-1-31.core-rs2.thdo.ncuk.net [80.249.97.85]
11 186 ms 218 ms 172 ms www.thinkbroadband.com [80.249.99.130]
Trace complete.
Looking at your correspondence with AfriGuy, and the fault history for your ADSL line, I'm pretty convinced there is a line issue causing your woes!
We'll keep pushing Telkom hard to get a Tech out there as quickly as possible!
dankeschön![]()
Speed has taken a serious nose-dive on AH... especially on local sites.
Here are some speed tests (10MB AH Business Uncapped).
http://speedtest.ookla.com/result/2837598888.png
http://speedtest.ookla.com/result/2837599232.png
http://speedtest.ookla.com/result/2837599462.png
same problem we have any time of the day and it is getting worse since january
well ah why dont you tell us exactly where the problem is instead of blaming exchanges
after all you are the company who gets paid to do the job properly
Sigh...I just scared myself with how bad the Afrihost connectivity actually is at this stage. Over the last 2 or 3 weeks I've noticed a marked degradation in the service I've been getting in terms of latency and streaming.
So out of frustration this morning I purchased a few gigs from another ISP on a different backbone.
Yeah, there isn't much more to say than that.