Afrihost Capped ADSL Feedback (MTN) - New beginning

[caroper]

I can understand it's frustrating to see, but running ads like this is a long term planning exercise. We can't exactly yank everything

True, they are far too busy yanking our chains to yank anything else ....

 

[AfriGuy]

True, they are far too busy yanking our chains to yank anything else ....

I think with what's been discussed/ planned among the community that's the last thing we're doing.
Each to their own I guess.

 

[i.got~issues]

Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\windows\system32>tracert afrihost.com

Tracing route to afrihost.com [41.181.185.18]
over a maximum of 30 hops:

1 * * * Request timed out.
2 * * * Request timed out.
3 1795 ms 283 ms 726 ms ipc-send-tb-3a.mtnbusiness.net [41.181.53.214]
4 79 ms 98 ms 96 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * 3068 ms 18.185.181.41.in-addr.aserv.co.za [41.181.185.18]

Trace complete.

 

[AfriGuy]

Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\windows\system32>tracert afrihost.com

Tracing route to afrihost.com [41.181.185.18]
over a maximum of 30 hops:

1 * * * Request timed out.
2 * * * Request timed out.
3 1795 ms 283 ms 726 ms ipc-send-tb-3a.mtnbusiness.net [41.181.53.214]
4 79 ms 98 ms 96 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * 3068 ms 18.185.181.41.in-addr.aserv.co.za [41.181.185.18]

Trace complete.

This seems way more severe to what's been reported before - also concerning that your router isn't returning any results.
Are the same results replicated when using other accounts?

 

[i.got~issues]

This seems way more severe to what's been reported before - also concerning that your router isn't returning any results.
Are the same results replicated when using other accounts?

C:\windows\system32>tracert afrihost.com

Tracing route to afrihost.com [41.181.185.18]
over a maximum of 30 hops:

1 * * * Request timed out.
2 23 ms 23 ms 21 ms cdsl2-ctn-vl2473-ipc.ip.isnet.net [196.38.72.194]
3 22 ms 23 ms 22 ms vlan2473.cdsl2-ctn.isdsl.net [196.38.72.193]
4 22 ms 23 ms 22 ms 196.35.115.136
5 23 ms 26 ms 25 ms mi-za-cpt-p8-te0-0-0-0.ip.isnet.net [168.209.6.13]
6 23 ms 25 ms 24 ms 168.209.2.130
7 23 ms 22 ms 22 ms 41-208-29-210.mtnns.net [41.208.29.210]
8 23 ms 23 ms 24 ms 196.44.0.75
9 44 ms 43 ms 44 ms rb-cr-1.za--ct-cr-2.za.mtnns.net [196.44.31.69]
10 44 ms 43 ms 45 ms jh-cr-2.za--rb-cr-1.za-b.mtnns.net [196.44.31.171]
11 44 ms 45 ms 43 ms jh-dca-1.za--jh-cr-2.za-a.mtnns.net [41.181.180.8]
12 40 ms 40 ms 41 ms 18.185.181.41.in-addr.aserv.co.za [41.181.185.18]

Trace complete.

C:\windows\system32>

 

[giggity]

Getting poor speed speeds and horrific latency. Don't try blame it on the exchange. I am getting 8ms to it.

Web Africa 2GB Free:

Download Speed: 7215 kbps (901.9 KB/sec transfer rate)
Upload Speed: 856 kbps (107 KB/sec transfer rate)
Latency: 26 ms
Jitter: 11 ms



Afrihost:

Download Speed: 3732 kbps (466.5 KB/sec transfer rate)
Upload Speed: 726 kbps (90.8 KB/sec transfer rate)
Latency: 448 ms
Jitter: 9 ms

 

[AfriGuy]

C:\windows\system32>tracert afrihost.com

Tracing route to afrihost.com [41.181.185.18]
over a maximum of 30 hops:

1 * * * Request timed out.
2 23 ms 23 ms 21 ms cdsl2-ctn-vl2473-ipc.ip.isnet.net [196.38.72.194]
3 22 ms 23 ms 22 ms vlan2473.cdsl2-ctn.isdsl.net [196.38.72.193]
4 22 ms 23 ms 22 ms 196.35.115.136
5 23 ms 26 ms 25 ms mi-za-cpt-p8-te0-0-0-0.ip.isnet.net [168.209.6.13]
6 23 ms 25 ms 24 ms 168.209.2.130
7 23 ms 22 ms 22 ms 41-208-29-210.mtnns.net [41.208.29.210]
8 23 ms 23 ms 24 ms 196.44.0.75
9 44 ms 43 ms 44 ms rb-cr-1.za--ct-cr-2.za.mtnns.net [196.44.31.69]
10 44 ms 43 ms 45 ms jh-cr-2.za--rb-cr-1.za-b.mtnns.net [196.44.31.171]
11 44 ms 45 ms 43 ms jh-dca-1.za--jh-cr-2.za-a.mtnns.net [41.181.180.8]
12 40 ms 40 ms 41 ms 18.185.181.41.in-addr.aserv.co.za [41.181.185.18]

Trace complete.

C:\windows\system32>

That's very odd. Can you try and use your account again please?
While there is latency present, it's nowhere near as bad as what you posted earlier.

 

[i.got~issues]

That's very odd. Can you try and use your account again please?
While there is latency present, it's nowhere near as bad as what you posted earlier.

Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\windows\system32>tracert www.afrihost.com

Tracing route to www.afrihost.com [41.181.185.18]
over a maximum of 30 hops:

1 * * * Request timed out.
2 32 ms 219 ms 198 ms 41.181.53.213
3 63 ms 90 ms 88 ms ipc-send-tb-3a.mtnbusiness.net [41.181.53.214]
4 68 ms 67 ms 67 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 44 ms 46 ms 50 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 87 ms 48 ms 42 ms jh-cr-1.za--tb-cr-2.za.mtnns.net [196.44.31.66]
7 861 ms 603 ms 517 ms jh-dca-1.za--jh-cr-1.za-a.mtnns.net [196.44.0.217]
8 132 ms 424 ms 156 ms 18.185.181.41.in-addr.aserv.co.za [41.181.185.18]

Trace complete.

C:\windows\system32>

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                   No response from host -  100 |   21 |    0 |    0 |    0 |    0 |    0 |
|                           41.181.53.213 -    0 |  100 |  100 |   22 |   99 | 1106 |   74 |
|          ipc-send-tb-3a.mtnbusiness.net -    3 |   93 |   91 |   21 |   69 |  829 |   23 |
|   tb-dca-2.za--qux-c.za.mtnbusiness.net -    2 |   97 |   96 |   21 |   78 |  829 |   22 |
|                     unc-cpt-1.mtnns.net -    3 |   93 |   91 |   22 |   69 |  828 |   23 |
|        jh-cr-1.za--tb-cr-2.za.mtnns.net -    0 |  100 |  100 |   41 |  114 | 1132 |   43 |
|     jh-dca-1.za--jh-cr-1.za-a.mtnns.net -    3 |   93 |   91 |   40 |   89 |  882 |   43 |
|       18.185.181.41.in-addr.aserv.co.za -    3 |   93 |   91 |   41 |   88 |  846 |   42 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

 

[Venom Rush]

That's very odd. Can you try and use your account again please?
While there is latency present, it's nowhere near as bad as what you posted earlier.

Well I for one am getting results on par if not worse. Wherever you're getting your latency reports from is definitely not a reliable source in my opinion.

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

1 1 ms <1 ms 7 ms dsldevice.lan [10.0.0.2]
2 * * * Request timed out.
3 * 1598 ms 1590 ms 41.181.53.213
4 1273 ms 1270 ms 1094 ms ipc-send-tb-3a.mtnbusiness.net [41.181.53.214]
5 919 ms 575 ms 1277 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.19
8.188]
6 * 1152 ms * compj-cpt-1.mtnns.net [196.44.18.2]
7 1091 ms 1609 ms * ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]

8 1765 ms 1812 ms 1362 ms 196.44.0.74
9 * 1909 ms 1983 ms africainx.cinx.net.za [196.223.22.47]
10 1681 ms 1799 ms 1383 ms CORE.GP-CN-HET-MEE-1.TO.GP-HV-ICT-MEE-1.DFA.P2P.
10G.za.africainx.net [41.84.13.66]
11 1325 ms 1088 ms 1548 ms 41-66-132-246-f6.HET001-CPE-1-to-GP-CN-HET-MEE-1
.africainx.net [41.66.132.246]
12 2131 ms 1696 ms 1876 ms core-access-switch1.jnb1.host-h.net [197.189.193
.1]
13 * * * Request timed out.
14 1625 ms 2057 ms 1946 ms 197.242.89.170

Trace complete.

 

[AfriGuy]

Well I for one am getting results on par if not worse. Wherever you're getting your latency reports from is definitely not a reliable source in my opinion.

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

1 1 ms <1 ms 7 ms dsldevice.lan [10.0.0.2]
2 * * * Request timed out.
3 * 1598 ms 1590 ms 41.181.53.213
4 1273 ms 1270 ms 1094 ms ipc-send-tb-3a.mtnbusiness.net [41.181.53.214]
5 919 ms 575 ms 1277 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.19
8.188]
6 * 1152 ms * compj-cpt-1.mtnns.net [196.44.18.2]
7 1091 ms 1609 ms * ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]

8 1765 ms 1812 ms 1362 ms 196.44.0.74
9 * 1909 ms 1983 ms africainx.cinx.net.za [196.223.22.47]
10 1681 ms 1799 ms 1383 ms CORE.GP-CN-HET-MEE-1.TO.GP-HV-ICT-MEE-1.DFA.P2P.
10G.za.africainx.net [41.84.13.66]
11 1325 ms 1088 ms 1548 ms 41-66-132-246-f6.HET001-CPE-1-to-GP-CN-HET-MEE-1
.africainx.net [41.66.132.246]
12 2131 ms 1696 ms 1876 ms core-access-switch1.jnb1.host-h.net [197.189.193
.1]
13 * * * Request timed out.
14 1625 ms 2057 ms 1946 ms 197.242.89.170

Trace complete.

That's concerning
I'm checking with our team now.

 

[RickNRoller]

The below results are the same across 6 different lines at different locations.

Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 206.223.136.173: bytes=32 time=161ms TTL=53
Reply from 206.223.136.173: bytes=32 time=105ms TTL=53
Request timed out.
Reply from 206.223.136.173: bytes=32 time=67ms TTL=53
Reply from 206.223.136.173: bytes=32 time=76ms TTL=53
Reply from 206.223.136.173: bytes=32 time=78ms TTL=53
Reply from 206.223.136.173: bytes=32 time=462ms TTL=53
Request timed out.
Reply from 206.223.136.173: bytes=32 time=249ms TTL=53
Request timed out.
Request timed out.
Reply from 206.223.136.173: bytes=32 time=350ms TTL=53
Request timed out.
Request timed out.
Request timed out.
Reply from 206.223.136.173: bytes=32 time=372ms TTL=53
Reply from 206.223.136.173: bytes=32 time=308ms TTL=53
Request timed out.
Request timed out.
Request timed out.
Reply from 206.223.136.173: bytes=32 time=92ms TTL=53
Request timed out.
Request timed out.
Reply from 206.223.136.173: bytes=32 time=266ms TTL=53
Reply from 206.223.136.173: bytes=32 time=84ms TTL=53
Reply from 206.223.136.173: bytes=32 time=175ms TTL=53

Ping statistics for 206.223.136.173:
Packets: Sent = 871, Received = 567, Lost = 304 (34% loss),
Approximate round trip times in milli-seconds:
Minimum = 45ms, Maximum = 824ms, Average = 214ms

------------------------------------------------------------------------------------------

Tracing route to afrihost.com [41.181.185.18]
over a maximum of 30 hops:

1 1 ms 1 ms <1 ms 192.168.4.253
2 * * * Request timed out.
3 * 55 ms 93 ms 41.181.51.181
4 * 42 ms 56 ms 41.181.51.182
5 212 ms 516 ms 236 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
6 249 ms 210 ms 90 ms unc-cpt-1.mtnns.net [196.44.18.8]
7 189 ms 329 ms 71 ms jh-cr-1.za--tb-cr-2.za.mtnns.net [196.44.31.66]
8 130 ms 138 ms * jh-dca-1.za--jh-cr-1.za-a.mtnns.net [196.44.0.217]
9 452 ms 71 ms 213 ms 18.185.181.41.in-addr.aserv.co.za [41.181.185.18]

Trace complete.

 

[AfriGuy]

Thanks for the tests guys, not sure what's happening here - I'm gathering some accounts to pass onto our team for a look into.
Monitoring is reflecting the same We're checking things out.

So far, this only looks to be affecting Capped accounts in the South.

 

[waynehooper]

I was getting terrible download speeds. Changed my DNS settings to Google and I am getting near full speed on a IOS update

 

[AfriGuy]

I was getting terrible download speeds. Changed my DNS settings to Google and I am getting near full speed on a IOS update

That's good to hear
What's your latency looking like at the moment? I'm trying to get an issue trended and investigated that seems to be affecting Capped account.

 

[giggity]

That's good to hear
What's your latency looking like at the moment? I'm trying to get an issue trended and investigated that seems to be affecting Capped account.

Just changed to Google's DNS and I'm getting the same shoddy latency as before.

 

[Ovenmit]

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

1 <1 ms <1 ms <1 ms 10.0.0.2
2 6 ms 7 ms 6 ms 105-236-240-129-esr-lo.mtnbusiness.co.za [105.236.240.129]
3 64 ms 228 ms 64 ms 41.181.201.94
4 30 ms 21 ms 61 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 142 ms 108 ms 89 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 125 ms 87 ms 45 ms jh-cr-1.za--tb-cr-2.za.mtnns.net [196.44.31.66]
7 144 ms 251 ms 46 ms jh-dca-1.za--jh-cr-1.za-a.mtnns.net [196.44.0.217]
8 39 ms 68 ms 191 ms 18.185.181.41.in-addr.aserv.co.za [41.181.185.18]

Trace complete.

=========================================

Tracing route to www.afrihost.com [41.181.185.18]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.2
2 7 ms 7 ms 21 ms 105-236-240-129-esr-lo.mtnbusiness.co.za [105.236.240.129]
3 203 ms 104 ms 64 ms 41.181.201.94
4 143 ms 57 ms 162 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 163 ms 66 ms 52 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 90 ms 47 ms 42 ms jh-cr-1.za--tb-cr-2.za.mtnns.net [196.44.31.66]
7 41 ms 67 ms 46 ms jh-dca-1.za--jh-cr-1.za-a.mtnns.net [196.44.0.217]


https://www.youtube.com/watch?v=v4s2AMKPHnE

...well.. if you can get it to load...

 

[AfriGenie]

Just changed to Google's DNS and I'm getting the same shoddy latency as before.

Thanks for checking, we should have an update in a few minutes.

 

[Venom Rush]

That's concerning
I'm checking with our team now.

That's not even the worst of it...

Tracing route to facebook.com [173.252.120.6]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms dsldevice.lan [10.0.0.2]
2 * * * Request timed out.
3 1857 ms 1137 ms 1740 ms 41.181.53.213
4 * 1141 ms 1674 ms ipc-send-tb-3a.mtnbusiness.net [41.181.53.214]
5 1346 ms 1350 ms 1626 ms tb-dca-2.za--qux-i.za.mtnbusiness.net [66.8.11.1
86]
6 1151 ms 921 ms 771 ms unc-cpt-1.mtnns.net [196.44.18.8]
7 2065 ms 1864 ms 1510 ms jh-cr-1.za--tb-cr-2.za.mtnns.net [196.44.31.66]

8 1811 ms 2172 ms 2040 ms ls-cr-2.uk--jh-cr-1.za.mtnns.net [196.44.31.114]

9 1867 ms 1961 ms 2064 ms am-cr-1.nl--ls-cr-2.uk-a.mtnns.net [196.44.31.18
3]
10 1618 ms 1756 ms 1978 ms am-tpr-1.nl--am-cr-1.nl-a.mtn.net [209.212.111.1
41]
11 1864 ms 994 ms 1598 ms br01.ams1.tfbnw.net [80.249.209.115]
12 2121 ms 1973 ms 2215 ms ae1.bb01.ams2.tfbnw.net [31.13.29.86]
13 2208 ms 2190 ms 1576 ms ae3.bb02.bos2.tfbnw.net [204.15.23.61]
14 1871 ms 2610 ms 1939 ms be26.bb01.lga1.tfbnw.net [31.13.28.1]
15 * 1785 ms 1672 ms be29.bb02.dca1.tfbnw.net [74.119.78.164]
16 2461 ms 2151 ms * ae33.bb04.frc3.tfbnw.net [204.15.23.215]
17 2833 ms 726 ms 1592 ms ae32.dr06.frc3.tfbnw.net [31.13.29.237]
18 * * * Request timed out.
19 * * * Request timed out.
20 737 ms 713 ms 1675 ms edge-star-shv-12-frc3.facebook.com [173.252.120.
6]

Trace complete.

 

[waynehooper]

Was trying to download a 34mb IOS update and completion time was 12 minutes. After the dns change I got near full speed

Latency is 55ms on the Rosebank Telkom test and 60ms on the Mweb Jhb test

That's good to hear
What's your latency looking like at the moment? I'm trying to get an issue trended and investigated that seems to be affecting Capped account.

 

[AfriGenie]

That's not even the worst of it...

Tracing route to facebook.com [173.252.120.6]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms dsldevice.lan [10.0.0.2]
2 * * * Request timed out.
3 1857 ms 1137 ms 1740 ms 41.181.53.213
4 * 1141 ms 1674 ms ipc-send-tb-3a.mtnbusiness.net [41.181.53.214]
5 1346 ms 1350 ms 1626 ms tb-dca-2.za--qux-i.za.mtnbusiness.net [66.8.11.1
86]
6 1151 ms 921 ms 771 ms unc-cpt-1.mtnns.net [196.44.18.8]
7 2065 ms 1864 ms 1510 ms jh-cr-1.za--tb-cr-2.za.mtnns.net [196.44.31.66]

8 1811 ms 2172 ms 2040 ms ls-cr-2.uk--jh-cr-1.za.mtnns.net [196.44.31.114]

9 1867 ms 1961 ms 2064 ms am-cr-1.nl--ls-cr-2.uk-a.mtnns.net [196.44.31.18
3]
10 1618 ms 1756 ms 1978 ms am-tpr-1.nl--am-cr-1.nl-a.mtn.net [209.212.111.1
41]
11 1864 ms 994 ms 1598 ms br01.ams1.tfbnw.net [80.249.209.115]
12 2121 ms 1973 ms 2215 ms ae1.bb01.ams2.tfbnw.net [31.13.29.86]
13 2208 ms 2190 ms 1576 ms ae3.bb02.bos2.tfbnw.net [204.15.23.61]
14 1871 ms 2610 ms 1939 ms be26.bb01.lga1.tfbnw.net [31.13.28.1]
15 * 1785 ms 1672 ms be29.bb02.dca1.tfbnw.net [74.119.78.164]
16 2461 ms 2151 ms * ae33.bb04.frc3.tfbnw.net [204.15.23.215]
17 2833 ms 726 ms 1592 ms ae32.dr06.frc3.tfbnw.net [31.13.29.237]
18 * * * Request timed out.
19 * * * Request timed out.
20 737 ms 713 ms 1675 ms edge-star-shv-12-frc3.facebook.com [173.252.120.
6]

Trace complete.

Oh wow... We're definitely seeing something strange happening in the South, and to a lesser degree in the East, this is a priority.