- Joined
- May 24, 2012
- Messages
- 17,239
Latency has come down so far, I wonder what was up.
We'll need to test and monitor further. Could have been an area issue on Telkom
Latency has come down so far, I wonder what was up.
Local Tracert
Tracing route to news24.co.za [41.86.110.143]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms H0M3nE11 [192.168.0.1]
2 18 ms 18 ms 13 ms ipc-recieve-tb-1a.mtnbusiness.net [41.181.53.150]
3 15 ms 18 ms * tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
4 19 ms 15 ms 14 ms unc-cpt-1.mtnns.net [196.44.18.8]
5 19 ms 18 ms 19 ms 196.44.31.106
6 13 ms 16 ms 19 ms nl-ha-2.za--rb-cr-1.za-a.mtnns.net [196.44.0.121]
7 19 ms 19 ms 19 ms 196-28-178-141.adsl.mweb.co.za [196.28.178.141]
8 18 ms 21 ms 17 ms tengig-0-0-0-1-cpt-p-1.mweb.co.za [197.84.7.1]
9 64 ms 21 ms 19 ms vl-12-cpt-hscore-2.mweb.co.za [197.84.5.254]
10 24 ms 19 ms 19 ms vp-02-14.bb.ctn.c27.za.net [196.28.178.70]
11 23 ms 19 ms 19 ms gig5-2-cpt-opt-65-1.optinet.net [196.41.133.166]
12 22 ms 18 ms 19 ms OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6]
13 20 ms 19 ms 19 ms 197-84-208-146.cpt.mweb.co.za [197.84.208.146]
14 19 ms 19 ms 19 ms 41-86-110-143.mweb.co.za [41.86.110.143]
Trace complete.
International Tracert
Tracing route to thinkbroadband.com [80.249.99.130]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms H0M3nE11 [192.168.0.1]
2 17 ms 19 ms 19 ms 41.181.221.254
3 20 ms 18 ms 11 ms tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.184.28]
4 17 ms 19 ms 19 ms unc-cpt-1.mtnns.net [196.44.18.8]
5 16 ms 19 ms 16 ms 196.44.31.106
6 240 ms 187 ms 159 ms am-cr-1.am--lt-cr-1.uk-a.mtnns.net [196.44.31.221]
7 176 ms 159 ms 159 ms ls-pr-1.uk--ls-cr-1.uk-a.mtn.net [209.212.111.83]
8 164 ms 159 ms 155 ms linx-gw1.thn.ncuk.net [195.66.224.240]
9 162 ms 169 ms 159 ms te2-1-9.star10g.bdr-rt3.thdo.ncuk.net [80.249.97.17]
10 160 ms 158 ms 156 ms te1-1-1-31.core-rs2.thdo.ncuk.net [80.249.97.85]
11 157 ms 163 ms 164 ms www.thinkbroadband.com [80.249.99.130]
Trace complete.
International Speedtest
Downloaded 10.0 megabytes in 1:54 seconds. (89.44 KB/s)
Local Speedtest
Downloaded 8000.0 kilobytes in 38 seconds. (209.26 KB/s)
Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert)
Pinging 41.181.53.214 with 32 bytes of data:
Reply from 41.181.53.214: bytes=32 time=21ms TTL=60
Reply from 41.181.53.214: bytes=32 time=37ms TTL=60
Reply from 41.181.53.214: bytes=32 time=17ms TTL=60
Reply from 41.181.53.214: bytes=32 time=44ms TTL=60
Reply from 41.181.53.214: bytes=32 time=15ms TTL=60
Reply from 41.181.53.214: bytes=32 time=13ms TTL=60
Reply from 41.181.53.214: bytes=32 time=20ms TTL=60
Reply from 41.181.53.214: bytes=32 time=18ms TTL=60
Reply from 41.181.53.214: bytes=32 time=17ms TTL=60
Reply from 41.181.53.214: bytes=32 time=29ms TTL=60
Reply from 41.181.53.214: bytes=32 time=15ms TTL=60
Reply from 41.181.53.214: bytes=32 time=33ms TTL=60
Reply from 41.181.53.214: bytes=32 time=21ms TTL=60
Reply from 41.181.53.214: bytes=32 time=19ms TTL=60
Reply from 41.181.53.214: bytes=32 time=18ms TTL=60
Reply from 41.181.53.214: bytes=32 time=17ms TTL=60
Reply from 41.181.53.214: bytes=32 time=16ms TTL=60
Reply from 41.181.53.214: bytes=32 time=14ms TTL=60
Reply from 41.181.53.214: bytes=32 time=21ms TTL=60
Reply from 41.181.53.214: bytes=32 time=31ms TTL=60
Reply from 41.181.53.214: bytes=32 time=20ms TTL=60
Reply from 41.181.53.214: bytes=32 time=18ms TTL=60
Reply from 41.181.53.214: bytes=32 time=17ms TTL=60
Reply from 41.181.53.214: bytes=32 time=16ms TTL=60
Reply from 41.181.53.214: bytes=32 time=14ms TTL=60
Reply from 41.181.53.214: bytes=32 time=23ms TTL=60
Reply from 41.181.53.214: bytes=32 time=14ms TTL=60
Reply from 41.181.53.214: bytes=32 time=20ms TTL=60
Reply from 41.181.53.214: bytes=32 time=18ms TTL=60
Reply from 41.181.53.214: bytes=32 time=27ms TTL=60
Ping statistics for 41.181.53.214:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 13ms, Maximum = 44ms, Average = 20ms
2014/06/05 22:04:43.72
Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert)
Pinging 105.236.13.129 with 32 bytes of data:
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=9ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=9ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=13ms TTL=254
Reply from 105.236.13.129: bytes=32 time=161ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=7ms TTL=254
Reply from 105.236.13.129: bytes=32 time=9ms TTL=254
Reply from 105.236.13.129: bytes=32 time=7ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=11ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Ping statistics for 105.236.13.129:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 7ms, Maximum = 161ms, Average = 13ms
2014/06/05 22:21:44.82
Local Tracert
Tracing route to news24.co.za [41.86.110.143]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms home.gateway.pace.net [192.168.1.254]
2 7 ms 6 ms 7 ms 105-236-13-129-esr-lo.mtnbusiness.co.za [105.236.13.129]
3 8 ms 8 ms 8 ms 41.181.221.254
4 8 ms 7 ms 8 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 8 ms 9 ms 8 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 9 ms 8 ms 9 ms 196.44.31.106
7 9 ms 9 ms 9 ms nl-ha-2.za--rb-cr-1.za-a.mtnns.net [196.44.0.121]
8 9 ms 9 ms 9 ms 196-28-178-141.adsl.mweb.co.za [196.28.178.141]
9 11 ms 10 ms 12 ms tengig-0-0-0-1-cpt-p-1.mweb.co.za [197.84.7.1]
10 10 ms 9 ms 9 ms vl-11-cpt-hscore-1.mweb.co.za [197.84.5.238]
11 10 ms 10 ms 10 ms 196.28.178.66
12 10 ms 10 ms 9 ms gig5-1-cpt-opt-65-1.optinet.net [196.41.133.234]
13 11 ms 10 ms 9 ms OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6]
14 10 ms 10 ms 10 ms 197-84-208-146.cpt.mweb.co.za [197.84.208.146]
15 9 ms 10 ms 10 ms 41-86-110-143.mweb.co.za [41.86.110.143]
Trace complete.
International Tracert
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 7 ms 7 ms 7 ms 105-236-13-129-esr-lo.mtnbusiness.co.za [105.236.13.129]
3 8 ms 7 ms 8 ms 41.181.201.94
4 52 ms 7 ms 7 ms tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.184.28]
5 13 ms 13 ms 13 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 9 ms 9 ms 8 ms 196.44.31.106
7 151 ms 152 ms 152 ms am-cr-1.am--lt-cr-1.uk-a.mtnns.net [196.44.31.221]
8 152 ms 151 ms 151 ms ls-pr-1.uk--ls-cr-1.uk-a.mtn.net [209.212.111.83]
9 152 ms 152 ms 151 ms linx-gw1.thn.ncuk.net [195.66.224.240]
10 152 ms 152 ms 152 ms te2-1-9.star10g.bdr-rt3.thdo.ncuk.net [80.249.97.17]
11 153 ms 152 ms 152 ms te1-1-1-31.core-rs2.thdo.ncuk.net [80.249.97.85]
12 152 ms 152 ms 152 ms www.thinkbroadband.com [80.249.99.130]
Trace complete.
International Speedtest
Downloaded 20.0 megabytes in 19 seconds. (1037.28 KB/s)
Local Speedtest
Downloaded 15.6 megabytes in 17 seconds. (937.21 KB/s)
Test End Timestamp
2014/06/05 22:24:34.79
Zertop's "Is it my Line" Results
Basic Report:
Your average ping was 20ms
Your maximum ping was 44ms
Looking at your average ping, your line seems to be running perfectly![]()
Looking at your maximum ping, however, it seems as though there could be a slight intermittant issue on the line. If required, please post the results to a forum post.
Detailed Report
Code:Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert) Pinging 41.181.53.214 with 32 bytes of data: Reply from 41.181.53.214: bytes=32 time=21ms TTL=60 Reply from 41.181.53.214: bytes=32 time=37ms TTL=60 Reply from 41.181.53.214: bytes=32 time=17ms TTL=60 Reply from 41.181.53.214: bytes=32 time=44ms TTL=60 Reply from 41.181.53.214: bytes=32 time=15ms TTL=60 Reply from 41.181.53.214: bytes=32 time=13ms TTL=60 Reply from 41.181.53.214: bytes=32 time=20ms TTL=60 Reply from 41.181.53.214: bytes=32 time=18ms TTL=60 Reply from 41.181.53.214: bytes=32 time=17ms TTL=60 Reply from 41.181.53.214: bytes=32 time=29ms TTL=60 Reply from 41.181.53.214: bytes=32 time=15ms TTL=60 Reply from 41.181.53.214: bytes=32 time=33ms TTL=60 Reply from 41.181.53.214: bytes=32 time=21ms TTL=60 Reply from 41.181.53.214: bytes=32 time=19ms TTL=60 Reply from 41.181.53.214: bytes=32 time=18ms TTL=60 Reply from 41.181.53.214: bytes=32 time=17ms TTL=60 Reply from 41.181.53.214: bytes=32 time=16ms TTL=60 Reply from 41.181.53.214: bytes=32 time=14ms TTL=60 Reply from 41.181.53.214: bytes=32 time=21ms TTL=60 Reply from 41.181.53.214: bytes=32 time=31ms TTL=60 Reply from 41.181.53.214: bytes=32 time=20ms TTL=60 Reply from 41.181.53.214: bytes=32 time=18ms TTL=60 Reply from 41.181.53.214: bytes=32 time=17ms TTL=60 Reply from 41.181.53.214: bytes=32 time=16ms TTL=60 Reply from 41.181.53.214: bytes=32 time=14ms TTL=60 Reply from 41.181.53.214: bytes=32 time=23ms TTL=60 Reply from 41.181.53.214: bytes=32 time=14ms TTL=60 Reply from 41.181.53.214: bytes=32 time=20ms TTL=60 Reply from 41.181.53.214: bytes=32 time=18ms TTL=60 Reply from 41.181.53.214: bytes=32 time=27ms TTL=60 Ping statistics for 41.181.53.214: Packets: Sent = 30, Received = 30, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 13ms, Maximum = 44ms, Average = 20ms 2014/06/05 22:04:43.72
I dunno if I would jump to a line issue - pings look OK. Looks like slow throughput, but otherwise latency is fine. I'm guessing this started to ease off after about 10 last night?
Hi AfriMan
It sometimes becomes usable around between 11pm and midnight... but I cannot say really as I switch to a backup account as soon as the AH becomes dial-up internationally. While I get fluctuating latency and sub 800kbs on the Afrihost account, I get normal latency and a consistent 2.6Mbs on the backup 2Mbs account all night. Also, on my Afrihost account, speedtests to JHB have better results than Cape Town ones. Cape Town is just as useless as international during the evening.
This performance degradation has happened every night on on my Afrihost Business account, and only this account, since Monday.
Sounds consistent more or less with peak demand on the network that I saw last - seems to follow the same trend as most night.
Not sure about the JHB CPT thing - your routing looks correct on the trace you posted, so it could just be the speed of the servers themselves serving the tests.
It is not just limited to the speedtest servers ... it is international browsing, and actually anything to do with internets... this all becomes useless.
I go to the speedtest as a last resort before switching accounts.
Switch accounts, all works at full speed all night.
Switch to Afrihost account, back to 384k to 1Mbs fluctuating interwebz.
These are the exact symptoms experienced by me before the bottom fell out of the IPC earlier this year.
It is not just limited to the speedtest servers ... it is international browsing, and actually anything to do with internets... this all becomes useless.
I go to the speedtest as a last resort before switching accounts.
Switch accounts, all works at full speed all night.
Switch to Afrihost account, back to 384k to 1Mbs fluctuating interwebz.
These are the exact symptoms experienced by me before the bottom fell out of the IPC earlier this year.
I'm pretty sure that you're right here, cos the symptoms are the same and the times correspond to the demand trends on the South IPC. I was just offering a possible explanation on the Cape Town/Joburg speedtest issue.
I am on the normal Afrihost uncapped account (4Mbps) and, today, I am working at home (too cold to venture out) and have noticed that my shaping is 50% on download and 25% on P2P. What are you "business" uncapped guys shaping figures? I am wondering if I should upgrade to the business package in the future.
afrihost
![]()
webafrica
![]()
So something is horribly wrong with my line today. Sent a support ticket around 5am. They responded to say they stabablized my line. This has resulted in me not disconnecting every few minutes, but has done nothing to restore my 8Mb/s business connection. It is several hours since I replied giving them feedback and complaining about these speed test results. Still no word.
Officially there is no shaping;
View attachment 123581
But sometimes... it sure just feels like there is...
Looks like a line/exchange issue possibly (or maybe even a router problem) as those pings are through the roof. What does a tracert look like (or use Zertop's tool)?
Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert)
Pinging 105.236.8.129 with 32 bytes of data:
Reply from 105.236.8.129: bytes=32 time=82ms TTL=254
Reply from 105.236.8.129: bytes=32 time=105ms TTL=254
Reply from 105.236.8.129: bytes=32 time=61ms TTL=254
Reply from 105.236.8.129: bytes=32 time=66ms TTL=254
Reply from 105.236.8.129: bytes=32 time=35ms TTL=254
Reply from 105.236.8.129: bytes=32 time=37ms TTL=254
Reply from 105.236.8.129: bytes=32 time=62ms TTL=254
Reply from 105.236.8.129: bytes=32 time=48ms TTL=254
Reply from 105.236.8.129: bytes=32 time=43ms TTL=254
Reply from 105.236.8.129: bytes=32 time=70ms TTL=254
Reply from 105.236.8.129: bytes=32 time=51ms TTL=254
Reply from 105.236.8.129: bytes=32 time=38ms TTL=254
Reply from 105.236.8.129: bytes=32 time=53ms TTL=254
Reply from 105.236.8.129: bytes=32 time=52ms TTL=254
Request timed out.
Request timed out.
Reply from 105.236.8.129: bytes=32 time=68ms TTL=254
Reply from 105.236.8.129: bytes=32 time=78ms TTL=254
Reply from 105.236.8.129: bytes=32 time=34ms TTL=254
Reply from 105.236.8.129: bytes=32 time=61ms TTL=254
Reply from 105.236.8.129: bytes=32 time=36ms TTL=254
Reply from 105.236.8.129: bytes=32 time=37ms TTL=254
Reply from 105.236.8.129: bytes=32 time=40ms TTL=254
Reply from 105.236.8.129: bytes=32 time=76ms TTL=254
Reply from 105.236.8.129: bytes=32 time=46ms TTL=254
Reply from 105.236.8.129: bytes=32 time=86ms TTL=254
Reply from 105.236.8.129: bytes=32 time=46ms TTL=254
Reply from 105.236.8.129: bytes=32 time=112ms TTL=254
Reply from 105.236.8.129: bytes=32 time=58ms TTL=254
Reply from 105.236.8.129: bytes=32 time=56ms TTL=254
Ping statistics for 105.236.8.129:
Packets: Sent = 30, Received = 28, Lost = 2 (6% loss),
Approximate round trip times in milli-seconds:
Minimum = 34ms, Maximum = 112ms, Average = 58ms
2014/06/06 10:50:01.83
Local Tracert
Tracing route to news24.co.za [41.86.110.143]
over a maximum of 30 hops:
1 <1 ms 1 ms 2 ms 192.168.1.254
2 9 ms 23 ms 25 ms 105-236-8-129-esr-lo.mtnbusiness.co.za [105.236.8.129]
3 34 ms 32 ms 62 ms ipc-send-tb-3a.mtnbusiness.net [41.181.53.214]
4 45 ms 29 ms 62 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 42 ms 20 ms 40 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 45 ms 29 ms 28 ms 196.44.31.106
7 57 ms 44 ms 28 ms nl-ha-2.za--rb-cr-1.za-a.mtnns.net [196.44.0.121]
8 43 ms 38 ms 52 ms 196-28-178-141.adsl.mweb.co.za [196.28.178.141]
9 52 ms 54 ms 36 ms tengig-0-0-0-1-cpt-p-1.mweb.co.za [197.84.7.1]
10 110 ms 47 ms 29 ms vl-11-cpt-hscore-1.mweb.co.za [197.84.5.238]
11 95 ms 57 ms 80 ms 196.28.178.66
12 55 ms 50 ms 37 ms gig5-1-cpt-opt-65-1.optinet.net [196.41.133.234]
13 48 ms * * OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6]
14 35 ms 59 ms * 197-84-208-146.cpt.mweb.co.za [197.84.208.146]
15 36 ms 34 ms 28 ms 41-86-110-143.mweb.co.za [41.86.110.143]
Trace complete.
International Tracert
Tracing route to thinkbroadband.com [80.249.99.130]
over a maximum of 30 hops:
1 1 ms <1 ms 1 ms 192.168.1.254
2 12 ms 9 ms 8 ms 105-236-8-129-esr-lo.mtnbusiness.co.za [105.236.8.129]
3 * * 42 ms 41.181.201.94
4 * 93 ms 41 ms tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.184.28]
5 * * 59 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 34 ms 27 ms 43 ms 196.44.31.106
7 204 ms 177 ms * am-cr-1.am--lt-cr-1.uk-a.mtnns.net [196.44.31.221]
8 * 212 ms 202 ms ls-pr-1.uk--ls-cr-1.uk-a.mtn.net [209.212.111.83]
9 * * * Request timed out.
10 179 ms 180 ms 165 ms te2-1-9.star10g.bdr-rt3.thdo.ncuk.net [80.249.97.17]
11 * 191 ms 168 ms te1-1-1-31.core-rs2.thdo.ncuk.net [80.249.97.85]
12 189 ms 202 ms 170 ms www.thinkbroadband.com [80.249.99.130]
Trace complete.
International Speedtest
Downloaded 20.0 megabytes in 46 seconds. (438.56 KB/s)
Local Speedtest
Downloaded 15.6 megabytes in 51 seconds. (312.31 KB/s)
Test End Timestamp
2014/06/06 10:57:48.56
Aaah... indeed.
So it is a wait and struggle then until another upgrade or the balance of the previous is installed.
/sigh