Afrihost Uncapped ADSL Feedback

Status
Not open for further replies.
Peter_A
I suspect you might get a lot of flak! :-) Not the same guys bitching and saying it is alright. The other problem is that we are comparing what we have with what we had! If it was the same or better then all would be well and we can sleep well. BUT all is not well compared with what we had!
 
Pete_A said:
You guys on the forum are weird. Last night there is some high latency. Everyone is complaining on the forums that they are immediately cancelling their service, leaving bad reviews, setting reminders to not vote isp of the year at certain dates, twittering their hate. Today its ok, and everyone is like "Im holding out for a few months to see how the service it since its new." Fickle eh? I mentioned in another thread, it is normal in this country for the providers to have high latency from time to time. They are not on international level yet. Things do seem to be improving even since as little as 3 years ago.
Click to expand...

I think you missed the point. In summary: Users had the best latency we've had in a while. Afrihost moved to MTN, and now the latency is rubbish at best, and is not set to improve anytime this year. Essentially Afrihost downgraded all Cape Town users, and we must just live with it.
 
Sinbad said:
Do me a favour and run a traceroute to your IP from telia's looking glass in amsterdam?

http://looking-glass.telia.net/
Click to expand...

CPT 2Mbps with nntp running


TeliaSonera Looking Glass - traceroute inet 105.236.8.65 as-number-lookup

Router: Hong Kong
Command: traceroute inet 105.236.8.65 as-number-lookup


traceroute to 105.236.8.65 (105.236.8.65), 30 hops max, 40 byte packets
1 las-bb1-link.telia.net (213.155.134.194) 163.061 ms las-bb1-link.telia.net (213.155.130.36) 167.425 ms las-bb1-link.telia.net (213.155.132.215) 231.940 ms
2 xe-4-2-0.edge1.LosAngeles9.Level3.net (4.68.110.221) 151.794 ms 180.024 ms 154.754 ms
3 vlan60.csw1.LosAngeles1.Level3.net (4.69.144.62) [AS 3356] 161.741 ms vlan80.csw3.LosAngeles1.Level3.net (4.69.144.190) [AS 3356] 201.678 ms vlan90.csw4.LosAngeles1.Level3.net (4.69.144.254) [AS 3356] 171.531 ms
MPLS Label=1258 CoS=0 TTL=1 S=1
4 ae-83-83.ebr3.LosAngeles1.Level3.net (4.69.137.41) [AS 3356] 166.284 ms ae-73-73.ebr3.LosAngeles1.Level3.net (4.69.137.37) [AS 3356] 177.355 ms ae-83-83.ebr3.LosAngeles1.Level3.net (4.69.137.41) [AS 3356] 177.089 ms
MPLS Label=1208 CoS=0 TTL=1 S=1
5 ae-3-3.ebr1.SanJose1.Level3.net (4.69.132.9) [AS 3356] 151.931 ms 162.948 ms 153.452 ms
MPLS Label=1434 CoS=0 TTL=1 S=1
6 ae-2-2.ebr2.NewYork1.Level3.net (4.69.135.186) [AS 3356] 235.783 ms 235.727 ms 232.749 ms
MPLS Label=1453 CoS=0 TTL=1 S=1
7 ae-82-82.csw3.NewYork1.Level3.net (4.69.148.42) [AS 3356] 232.993 ms 237.758 ms ae-72-72.csw2.NewYork1.Level3.net (4.69.148.38) [AS 3356] 238.263 ms
MPLS Label=1126 CoS=0 TTL=1 S=1
8 ae-71-71.ebr1.NewYork1.Level3.net (4.69.134.69) [AS 3356] 229.877 ms ae-91-91.ebr1.NewYork1.Level3.net (4.69.134.77) [AS 3356] 244.583 ms ae-61-61.ebr1.NewYork1.Level3.net (4.69.134.65) [AS 3356] 241.199 ms
MPLS Label=1077 CoS=0 TTL=1 S=1
9 ae-42-42.ebr2.London1.Level3.net (4.69.137.69) [AS 3356] 257.364 ms 254.358 ms 270.183 ms
MPLS Label=1214 CoS=0 TTL=1 S=1
10 ae-56-221.csw2.London1.Level3.net (4.69.153.130) [AS 3356] 254.516 ms ae-58-223.csw2.London1.Level3.net (4.69.153.138) [AS 3356] 274.688 ms ae-59-224.csw2.London1.Level3.net (4.69.153.142) [AS 3356] 260.257 ms
MPLS Label=1024 CoS=0 TTL=1 S=1
11 * * *
12 195.50.122.182 (195.50.122.182) [AS 3356] 270.393 ms 259.238 ms 256.592 ms
13 209.212.111.186 (209.212.111.186) [AS 16637] 270.762 ms 259.754 ms 275.727 ms
MPLS Label=725474 CoS=0 TTL=1 S=1
14 ct-cr-1.za--ct-cr-2.za-d.mtnns.net (196.44.31.34) [AS 16637] 459.068 ms 445.827 ms 478.822 ms
MPLS Label=398546 CoS=1 TTL=1 S=1
15 tb-cr-2.za--ls-cr-1.uk.mtnns.net (196.44.31.112) [AS 16637] 413.039 ms 41.181.180.11 (41.181.180.11) [AS 16637] 458.338 ms 457.287 ms
MPLS Label=736430 CoS=1 TTL=1 S=1
16 db-nt-1.jev.co.za (196.44.31.5) [AS 16637] 414.214 ms 424.154 ms 410.929 ms
MPLS Label=513216 CoS=1 TTL=1 S=1
17 196.44.31.106 (196.44.31.106) [AS 16637] 411.412 ms 41.181.180.11 (41.181.180.11) [AS 16637] 475.531 ms 425.355 ms
MPLS Label=430703 CoS=1 TTL=1 S=1
18 * ct-cr-2.za--rb-cr-2.za-a.mtnns.net (196.44.31.30) [AS 16637] 429.734 ms *
MPLS Label=360822 CoS=1 TTL=1 S=1
19 * 41.181.178.69 (41.181.178.69) [AS 16637] 464.204 ms ipc-send-rb-3a.za.mtnbusiness.net (41.181.178.81) [AS 16637] 446.856 ms
20 * 41.181.180.11 (41.181.180.11) [AS 16637] 440.179 ms *
21 ipc-send-rb-3a.za.mtnbusiness.net (41.181.178.81) [AS 16637] 450.282 ms * 450.362 ms
22 * * *
23 rb-cr-1.za--jh-cr-2.za-a.mtnns.net (196.44.31.94) [AS 16637] 508.126 ms * *
MPLS Label=308704 CoS=1 TTL=1 S=0
MPLS Label=508 CoS=1 TTL=2 S=1
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *




traceroute looking-glass.telia.net
traceroute to looking-glass.telia.net (81.228.10.74), 30 hops max, 60 byte packets
1 192.168.1.254 (192.168.1.254) 7.184 ms 7.377 ms 7.544 ms
2 105-236-8-65-esr-lo.mtnbusiness.co.za (105.236.8.65) 99.327 ms 113.076 ms 126.621 ms
3 ipc-recieve-rb-2a.za.mtnbusiness.net (41.181.178.65) 153.491 ms 153.950 ms 154.709 ms
4 rb-cr-1.za--rb-dca-1.za-a.mtnns.net (196.44.0.146) 155.428 ms 156.435 ms 157.669 ms
5 jh-cr-2.za--rb-cr-1.za-a.mtnns.net (196.44.31.95) 158.589 ms 159.563 ms jh-cr-1.za--rb-cr-2.za.mtnns.net (196.44.0.42) 160.552 ms
6 qux-jh-dca-2.za-b.za.mtnbusiness.net (41.181.165.115) 160.920 ms 132.731 ms 125.716 ms
7 xe-4-1-0.edge5.Amsterdam1.Level3.net (212.72.41.89) 289.698 ms 290.100 ms 290.712 ms
8 4.69.162.149 (4.69.162.149) 286.047 ms 4.69.162.141 (4.69.162.141) 289.020 ms 4.69.162.157 (4.69.162.157) 323.219 ms
9 ae-2-52.edge4.Amsterdam1.Level3.net (4.69.139.170) 286.335 ms ae-1-51.edge4.Amsterdam1.Level3.net (4.69.139.138) 345.172 ms ae-2-52.edge4.Amsterdam1.Level3.net (4.69.139.170) 345.480 ms
10 4.68.70.30 (4.68.70.30) 371.864 ms telia-level3-xe.amsterdam1.Level3.net (213.244.165.250) 290.319 ms 4.68.70.30 (4.68.70.30) 372.218 ms
11 adm-bb4-link.telia.net (213.155.133.208) 346.074 ms adm-bb3-link.telia.net (213.155.134.180) 351.297 ms adm-bb3-link.telia.net (80.91.253.153) 351.738 ms
12 hbg-bb1-link.telia.net (213.155.133.41) 314.198 ms hbg-bb2-link.telia.net (80.91.245.75) 327.471 ms hbg-bb1-link.telia.net (213.155.133.41) 327.545 ms
13 kbn-bb2-link.telia.net (80.91.247.229) 331.898 ms kbn-bb1-link.telia.net (80.91.249.204) 333.834 ms kbn-bb1-link.telia.net (213.155.134.198) 298.096 ms
14 kbn-b4-link.telia.net (80.91.254.223) 325.727 ms kbn-b4-link.telia.net (213.155.135.183) 326.062 ms kbn-b3-link.telia.net (213.155.135.179) 326.398 ms
15 ld-h-peer3-link.telia.net (80.91.253.91) 298.900 ms m-b-peer3.telia.net (80.91.253.71) 340.916 ms mb-peer3-link.telia.net (80.91.253.83) 326.677 ms
16 m-b-c5-link.se.telia.net (81.228.82.206) 369.203 ms m-b-c5-link.se.telia.net (81.228.75.88) 376.016 ms m-b-c5-link.se.telia.net (81.228.93.240) 340.412 ms
17 m-sp-d3-link.se.telia.net (81.228.74.114) 368.832 ms 404.407 ms 404.702 ms
18 semal11rs-link.fre.skanova.net (81.228.18.145) 439.076 ms 439.725 ms 440.029 ms
19 juniperlg1-sn4.m-sp.skanova.net (81.228.10.74) 393.814 ms 395.287 ms 378.921 ms
 
Last edited:
PsyWulf said:
Well neither my Mweb nor Afrihost routes all the way to destination:o
Click to expand...

Not about the destination... look at all the random hopping around inside the mtnns/mtnbusiness network - including packet loss there too.
 
I had the issue of high latency last night, but its been fine all day so far. Is it just people in CT now or something?

Pete
 
AfriMan said:
Last night latencies went a little bit ape! We are not sure what the actual cause is, there are theories involving backhaul and QoS, but I'd rather not post hearsay until I know what the actual story is.

What I do know is that MTN have got this back to normal sometime this morning. The extent to which all users experienced this is not certain, I was personally not online at all last night so I can't honestly add anything.

We've implementing some monitoring controls to identify these issues as an Early Warning System to avert things getting out of hand in the future. We'll also be addressing the shaping policies and QoS so that we can try to pin down exactly where these issues are arising from and how we can ensure best overall experience for everyone.

I see someone has taken to quoting me on Twitter. So as I've mentioned before, it's a learning curve for us, we're getting better at this everyday, and our goal is to eventually be the best network and service in the country. I have every confidence in our team.
Click to expand...

ImageUploadedByTapatalk1351784752.144898.jpg

I can assure you this is not normal for a 4mbps line! Reported this 48h ago and still no joy! Oh wait my line was reset! What a ****ing joke
 
Last edited:
Got an account today, testing to Jhb from Ct:

2279224002.png


To Ct from Ct:


To London from Ct:
 
ill be moving over in a months time :) seriously guys i would blame the exchange in the local area if you have problems. so far Afrihost have been fine for me. did have one hiccup here but that was when the line upgrades took place
 
wez1007 said:
ill be moving over in a months time :) seriously guys i would blame the exchange in the local area if you have problems. so far Afrihost have been fine for me. did have one hiccup here but that was when the line upgrades took place
Click to expand...

Let's talk again in a month

As a matter of interest if it's my local exchange please give me a logical explanation as to why my line runs at 435KB/s on my fnb connect account & a whopping 157KB/s on Afrihost account?
 
Last edited:
Let's hope Afriman is using his internet connection tonight... Then he can experience the bliss of being an Afrihost customer himself :P

Oh, and I meant 130ms ping to my uplink in my previous post.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X