Afrihost Uncapped ADSL Feedback (Pt3)

Status
Not open for further replies.
I'm also getting highly pissed off with this **** adsl speeds. Browsing is just terrible.
I'm on a 4mb line and it feels worse than dial-up.

This ain't "PURE INTERNET JOY".

Unhappy Afrihost customer.
 
Another night after 10, another night where it gets beyond awful for gaming ......... seriously dunno how it gets worse the later it is.

112413966.png


112414240.png


C:\Users\Andre>ping google.co.za

Pinging google.co.za [74.125.233.3] with 32 bytes of data:
Reply from 74.125.233.3: bytes=32 time=189ms TTL=56
Reply from 74.125.233.3: bytes=32 time=190ms TTL=56
Reply from 74.125.233.3: bytes=32 time=188ms TTL=56
Reply from 74.125.233.3: bytes=32 time=205ms TTL=56

Ping statistics for 74.125.233.3:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 188ms, Maximum = 205ms, Average = 193ms

C:\Users\Andre>tracert google.co.za

Tracing route to google.co.za [74.125.233.3]
over a maximum of 30 hops:

1 16 ms 16 ms 16 ms 105-236-7-129-esr-lo.mtnbusiness.co.za [105.236.
7.129]
2 26 ms 25 ms 25 ms 41.181.221.218
3 25 ms 25 ms 25 ms rb-dca-2.za--qux-b.za.mtnbusiness.net [41.181.16
5.118]
4 215 ms 231 ms 215 ms rb-cr-1.za--rb-dca-2.mtnns.net [196.44.31.122]
5 231 ms 231 ms 230 ms jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95
]
6 48 ms 47 ms 232 ms jh-cr-1.za--jh-cr-2.za-a.mtnns.net [196.44.31.25
4]
7 207 ms 208 ms 224 ms ls-cr-2.uk--rb-cr-1.za-g.mtnns.net [196.44.31.11
4]
8 214 ms 215 ms 214 ms ls-pr-2.uk--ls-cr-1.uk-a.mtn.net [209.212.111.20
3]
9 215 ms 214 ms 214 ms google-peering-ls-pr-2.uk.mtnns.net [209.212.99.
13]
10 * 215 ms * 209.85.255.76
11 221 ms 214 ms 225 ms 66.249.95.9
12 209 ms 204 ms 189 ms 72.14.237.239
13 188 ms 206 ms 187 ms jnb01s07-in-f3.1e100.net [74.125.233.3]

Trace complete.

C:\Users\Andre>ping mybroadband.co.za

Pinging mybroadband.co.za [197.242.89.170] with 32 bytes of data:
Reply from 197.242.89.170: bytes=32 time=53ms TTL=52
Reply from 197.242.89.170: bytes=32 time=53ms TTL=52
Reply from 197.242.89.170: bytes=32 time=53ms TTL=52
Reply from 197.242.89.170: bytes=32 time=53ms TTL=52

Ping statistics for 197.242.89.170:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 53ms, Maximum = 53ms, Average = 53ms

C:\Users\Andre>tracert mybroadband.co.za

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

1 17 ms 17 ms 16 ms 105-236-7-129-esr-lo.mtnbusiness.co.za [105.236.
7.129]
2 26 ms 25 ms 26 ms 41.181.221.218
3 26 ms 26 ms 42 ms rb-dca-2.za--qux-b.za.mtnbusiness.net [41.181.16
5.118]
4 27 ms 26 ms 26 ms xp-dca-1.za--xp-cr-1.za-a.mtnns.net [196.44.0.15
5]
5 31 ms 27 ms 26 ms jh-cr-1.za--rb-cr-2.za.mtnns.net [196.44.0.42]
6 26 ms 26 ms 26 ms 196.44.0.72
7 * * * Request timed out.
8 53 ms 54 ms 54 ms CORE.GP-CN-HET-MEE-1.TO.GP-HV-ICT-MEE-1.DFA.P2P.
10G.za [41.84.13.66]
9 53 ms 53 ms 54 ms 41-66-132-246-f6.HET001-CPE-1-to-GP-CN-HET-MEE-1
.africainx.net [41.66.132.246]
10 54 ms 54 ms 54 ms core-access-switch1.jnb1.host-h.net [197.189.193
.1]
11 60 ms 59 ms * row-access-switch1-row3-4.jnb1.host-h.net [197.1
89.193.36]
12 52 ms * 53 ms 197.242.89.170

Trace complete.


And then Mweb prepaid -

112414677.png


C:\Users\Andre>ping google.co.za

Pinging google.co.za [74.125.233.3] with 32 bytes of data:
Reply from 74.125.233.3: bytes=32 time=29ms TTL=55
Reply from 74.125.233.3: bytes=32 time=29ms TTL=55
Reply from 74.125.233.3: bytes=32 time=29ms TTL=55
Reply from 74.125.233.3: bytes=32 time=29ms TTL=55

Ping statistics for 74.125.233.3:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 29ms, Maximum = 29ms, Average = 29ms

C:\Users\Andre>tracert google.co.za

Tracing route to google.co.za [74.125.233.3]
over a maximum of 30 hops:

1 16 ms 16 ms 15 ms 41-133-124-1.dsl.mweb.co.za [41.133.124.1]
2 19 ms 18 ms 18 ms 197-82-5-250.dbn.mweb.co.za [197.82.5.250]
3 18 ms 19 ms 18 ms 197-82-2-3.dbn.mweb.co.za [197.82.2.3]
4 28 ms 29 ms 30 ms 197-80-7-5.jhb.mweb.co.za [197.80.7.5]
5 29 ms 30 ms 29 ms 197-80-96-6.jhb.mweb.co.za [197.80.96.6]
6 30 ms 30 ms 30 ms 72.14.237.239
7 30 ms 30 ms 29 ms jnb01s07-in-f3.1e100.net [74.125.233.3]

Trace complete.

C:\Users\Andre>ping mybroadband.co.za

Pinging mybroadband.co.za [197.242.89.170] with 32 bytes of data:
Reply from 197.242.89.170: bytes=32 time=32ms TTL=52
Reply from 197.242.89.170: bytes=32 time=32ms TTL=52
Reply from 197.242.89.170: bytes=32 time=32ms TTL=52
Reply from 197.242.89.170: bytes=32 time=33ms TTL=52

Ping statistics for 197.242.89.170:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 32ms, Maximum = 33ms, Average = 32ms

C:\Users\Andre>tracert mybroadband.co.za

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

1 16 ms 16 ms 16 ms 41-133-124-1.dsl.mweb.co.za [41.133.124.1]
2 18 ms 17 ms 18 ms 197-82-5-250.dbn.mweb.co.za [197.82.5.250]
3 18 ms 18 ms 17 ms 197-82-2-3.dbn.mweb.co.za [197.82.2.3]
4 32 ms 31 ms 32 ms 197-80-7-38.jhb.mweb.co.za [197.80.7.38]
5 31 ms 30 ms 30 ms africainx.jb1.napafrica.net [196.46.25.135]
6 33 ms 33 ms 33 ms CORE.GP-CN-HET-MEE-1.TO.GP-HV-ICT-MEE-1.DFA.P2P.
10G.za [41.84.13.66]
7 32 ms 33 ms 32 ms 41-66-132-246-f6.HET001-CPE-1-to-GP-CN-HET-MEE-1
.africainx.net [41.66.132.246]
8 34 ms 33 ms 34 ms core-access-switch1.jnb1.host-h.net [197.189.193
.1]
9 38 ms 35 ms 33 ms row-access-switch1-row3-4.jnb1.host-h.net [197.1
89.193.36]
10 32 ms 32 ms 32 ms 197.242.89.170

Trace complete.
 
The quality of service we are getting is just terrible. I'm trying to download VLC... 1 hour to get 23mb. Serious?
 
Battlefield was fine - though that was of course played from hosted servers.

Awesomenauts - which is hosted by the player p2p style was a HORRENDOUS.

Mumble however held up fine. So thank you for that.
 
Morning Guys!

We just received news that one of our IPC links in the North is currently down, this is reducing the amount of bandwidth that we have available a bit, MTN is working with Telkom to restore the IPC as quickly as possible.
 
Last edited:
Battlefield was fine - though that was of course played from hosted servers.

Awesomenauts - which is hosted by the player p2p style was a HORRENDOUS.

Mumble however held up fine. So thank you for that.

I haven't heard of Awesomenauts yet, which leads me to believe that we probably don't have a gaming profile activated and logged for it yet, let me see what I can do about that.
 
I see on the Afrihost site there is now an IPC link down in the north. This doesn't affect me but I just have to say Afriman/guy/girl/genie, holy crap you guys always seem to have a problem with something.
 
I see on the Afrihost site there is now an IPC link down in the north. This doesn't affect me but I just have to say Afriman/guy/girl/genie, holy crap you guys always seem to have a problem with something.

In this case, it is the actual Telkom infrastructure that we get from them that is down, it is not a major issue, as we are managing the available bandwidth significantly better than we have done in the past, but downloads and latencies may be a bit off of the usual.
 
I haven't heard of Awesomenauts yet, which leads me to believe that we probably don't have a gaming profile activated and logged for it yet, let me see what I can do about that.

that couldn't be why my DDO is suffering terribly could it?
 
Another quick update, the performance issue to Youtube appears to have been resolved, all the routing is now going to the correct servers in South Africa.

Thanks to giggity for taking the time to test with me and posting that very useful tutorial.
 
Aaaaaah!

Thanks! I will get our Team on this!

Another quick update, the performance issue to Youtube appears to have been resolved, all the routing is now going to the correct servers in South Africa.

Thanks to giggity for taking the time to test with me and posting that very useful tutorial.

awesome and awesome
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X