Afrihost Business Uncapped Feedback - 2

Status
Not open for further replies.
Hey guys.

Battling tonight on my 20meg VDSL account to stream youtube. Buffering and pauses all over the show. My PFSense firewall is showing that my line is hardly being used. Is there a problem today?
 
Hummercellc said:
Telkom Internet switched to the IPC platform a few months ago, only SAIX & the Telkom Guest account do not use IPC.
Click to expand...

From my understanding Telkom do have different routers at their BRAS installations (or BNG) so it is possible that traffic can be routed differently to IPC, depending on where the failure is in the signal chain.
 
DaBump said:
Hey guys.

Battling tonight on my 20meg VDSL account to stream youtube. Buffering and pauses all over the show. My PFSense firewall is showing that my line is hardly being used. Is there a problem today?
Click to expand...

No problems generally that I am aware of. Can you give a quick indication of your throughput and latency on a speedtest?
 
Something is wrong, web pages take ages to open.

I clicked refresh on this page and it took 15 seconds to load.

 
Last edited:
Rickster said:
Something is wrong, web pages take ages to open.

I clicked refresh on this page and it took 15 seconds to load.

Click to expand...

That is definitely not the speeds that you should be seeing. When did this start?

Could you please send me a DM with your ADSL details so that I can investigate.
 
Does anyone else here get jumpy ping to mweb servers? My ping often jumps to 200ms+ randomly on cmd and goes into the 20s and then down to 13-12ms and then back up again.
 
Loppas said:
Does anyone else here get jumpy ping to mweb servers? My ping often jumps to 200ms+ randomly on cmd and goes into the 20s and then down to 13-12ms and then back up again.
Click to expand...

had this with a previous provider ; was a config issue upstream.
 
Loppas said:
Was it doing this only with mweb? I have a web africa trial account and it doesn't get jumpy ping to mweb based servers.
Click to expand...

IS based accounts (the one I'm on now) has, like you experience, no issues with gaming. The old provider I was on had the same issue as you, and it was with all mweb and some Vodacom hosted servers. Exactly the same symptoms, but the underlying issue could be different. Contact support with MTR tests and all info and hope for the best.

PM me for more info tomorrow, I'm off for tonight. Cheers
 
Loppas said:
Does anyone else here get jumpy ping to mweb servers? My ping often jumps to 200ms+ randomly on cmd and goes into the 20s and then down to 13-12ms and then back up again.
Click to expand...

I'm not aware of any general peering problems with Mweb, but best if we can see an example of what you're seeing from your side. If you've got some IP's, we can also test from our side.
 
AfriMan said:
I'm not aware of any general peering problems with Mweb, but best if we can see an example of what you're seeing from your side. If you've got some IP's, we can also test from our side.
Click to expand...

Pinging mweb.co.za [196.2.63.110] with 32 bytes of dat
Reply from 196.2.63.110: bytes=32 time=14ms TTL=116
Reply from 196.2.63.110: bytes=32 time=17ms TTL=116
Reply from 196.2.63.110: bytes=32 time=18ms TTL=116
Reply from 196.2.63.110: bytes=32 time=14ms TTL=116
Reply from 196.2.63.110: bytes=32 time=18ms TTL=116
Request timed out.
Reply from 196.2.63.110: bytes=32 time=19ms TTL=116
Reply from 196.2.63.110: bytes=32 time=19ms TTL=116
Reply from 196.2.63.110: bytes=32 time=14ms TTL=116
Reply from 196.2.63.110: bytes=32 time=12ms TTL=116
Reply from 196.2.63.110: bytes=32 time=12ms TTL=116
Reply from 196.2.63.110: bytes=32 time=13ms TTL=116
Reply from 196.2.63.110: bytes=32 time=188ms TTL=116
Reply from 196.2.63.110: bytes=32 time=18ms TTL=116
Reply from 196.2.63.110: bytes=32 time=17ms TTL=116
Reply from 196.2.63.110: bytes=32 time=16ms TTL=116
Reply from 196.2.63.110: bytes=32 time=17ms TTL=116
Reply from 196.2.63.110: bytes=32 time=16ms TTL=116
Reply from 196.2.63.110: bytes=32 time=13ms TTL=116
Reply from 196.2.63.110: bytes=32 time=16ms TTL=116
Reply from 196.2.63.110: bytes=32 time=16ms TTL=116
Reply from 196.2.63.110: bytes=32 time=18ms TTL=116
Reply from 196.2.63.110: bytes=32 time=19ms TTL=116
Reply from 196.2.63.110: bytes=32 time=13ms TTL=116

Tracing route to mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms login.router [192.168.0.1]
2 8 ms 8 ms 8 ms 105-236-10-129-esr-lo.mtnbusiness.co.za [105.236
.10.129]
3 10 ms 10 ms 11 ms ipc-recieve-tb-2a.mtnbusiness.net [41.181.54.86]

4 10 ms 10 ms 10 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.19
8.188]
5 11 ms 11 ms 11 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 12 ms 11 ms 11 ms 196.44.31.106
7 10 ms 10 ms 10 ms nl-ha-2.za--rb-cr-1.za-a.mtnns.net [196.44.0.121
]
8 11 ms 12 ms 13 ms 196-28-178-141.adsl.mweb.co.za [196.28.178.141]

9 17 ms 15 ms 14 ms tengig-0-0-0-1-cpt-p-1.mweb.co.za [197.84.7.1]
10 12 ms 11 ms 12 ms vl-11-cpt-hscore-1.mweb.co.za [197.84.5.238]
11 33 ms 19 ms 21 ms 196.28.178.66
12 13 ms 12 ms 12 ms cte-core-sw2.vwol.net [196.41.144.35]
13 13 ms 12 ms 13 ms mweb.co.za [196.2.63.110]


Pinging 197.85.190.43 with 32 bytes of data
Reply from 197.85.190.43: bytes=32 time=13ms TTL=51
Reply from 197.85.190.43: bytes=32 time=13ms TTL=51
Reply from 197.85.190.43: bytes=32 time=16ms TTL=51
Reply from 197.85.190.43: bytes=32 time=12ms TTL=51
Reply from 197.85.190.43: bytes=32 time=15ms TTL=51
Reply from 197.85.190.43: bytes=32 time=14ms TTL=51
Reply from 197.85.190.43: bytes=32 time=15ms TTL=51
Reply from 197.85.190.43: bytes=32 time=14ms TTL=51
Reply from 197.85.190.43: bytes=32 time=19ms TTL=51
Reply from 197.85.190.43: bytes=32 time=14ms TTL=51
Reply from 197.85.190.43: bytes=32 time=19ms TTL=51
Reply from 197.85.190.43: bytes=32 time=16ms TTL=51
Reply from 197.85.190.43: bytes=32 time=16ms TTL=51
Reply from 197.85.190.43: bytes=32 time=14ms TTL=51
Reply from 197.85.190.43: bytes=32 time=14ms TTL=51
Reply from 197.85.190.43: bytes=32 time=17ms TTL=51
Reply from 197.85.190.43: bytes=32 time=18ms TTL=51
Reply from 197.85.190.43: bytes=32 time=18ms TTL=51
Reply from 197.85.190.43: bytes=32 time=14ms TTL=51
Reply from 197.85.190.43: bytes=32 time=16ms TTL=51
Reply from 197.85.190.43: bytes=32 time=18ms TTL=51
Reply from 197.85.190.43: bytes=32 time=13ms TTL=51
Reply from 197.85.190.43: bytes=32 time=16ms TTL=51
Reply from 197.85.190.43: bytes=32 time=19ms TTL=51

Tracing route to intoxicated.co.za [197.85.190.43]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms login.router [192.168.0.1]
2 9 ms 8 ms 8 ms 105-236-10-129-esr-lo.mtnbusiness.co.za [105.236
.10.129]
3 11 ms 10 ms 9 ms 41.181.51.182
4 19 ms 35 ms 10 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.19
8.188]
5 11 ms 11 ms 11 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 12 ms 11 ms 18 ms 196.44.31.106
7 10 ms 10 ms 10 ms nl-ha-2.za--rb-cr-1.za-a.mtnns.net [196.44.0.121
]
8 15 ms 13 ms 13 ms 196-28-178-141.adsl.mweb.co.za [196.28.178.141]

9 15 ms 13 ms 14 ms tengig-0-7-0-3-cpt-p-2.mweb.co.za [197.84.7.2]
10 19 ms 17 ms 18 ms vl-12-cpt-hscore-2.mweb.co.za [197.84.5.254]
11 16 ms 16 ms 17 ms vp-02-14.bb.ctn.c27.za.net [196.28.178.70]
12 14 ms 16 ms 17 ms 197-85-139-78.cpt.mweb.co.za [197.85.139.78]
13 13 ms 14 ms 15 ms intoxicated.co.za [197.85.190.43]

Trace complete.
 
AfriGuy said:
Hhhmm, could just be an ICMP timeout of sorts - is the overall experience being hampered by this at all?
Click to expand...

No it still seems to be playable in games. I tried pinging these servers on my web africa trial account and it was even more erratic and on my mweb trial account i still get an occasional 200ms+ jump but its stable. It only happens with cape town mweb based servers.
 
Last edited:
Loppas said:
No it still seems to be playable in games. I tried pinging these servers on my web africa trial account and it was even more erratic and on my mweb trial account i still get an occasional 200ms+ jump but its stable. It only happens with cape town mweb based servers.
Click to expand...

That is pretty odd - I guess it depends on how their routers. switches and other network equipment is setup. ICMP timeouts and jumps can happen.
 
Internet has turned to crap again. 500+ms latency and download speeds of 1-3Mbps on my 8Mbit account.
 
Yup just on midnight

C:\Users\Joshua>tracert 188.165.200.200

Tracing route to ns345728.ip-188-165-200.eu [188.165.200.200]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 8 ms 8 ms 8 ms 105-236-6-1-esr-lo.mtnbusiness.co.za [105.236.6.1]
3 491 ms 526 ms 571 ms ipc-recieve-jh-1a.za.mtnbusiness.net [41.181.178.5]
4 576 ms 628 ms 627 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
5 614 ms 555 ms 525 ms jh-dca-2.za--qux-b.za.mtnbusiness.net [41.181.165.114]
6 707 ms 731 ms 731 ms 41.181.180.10
7 730 ms 723 ms 699 ms ls-cr-2.uk--rb-cr-1.za.mtnns.net [196.44.31.114]
8 714 ms 697 ms 679 ms ls-pr-1.uk--ls-cr-2.uk-a.mtn.net [209.212.111.201]
9 * * * Request timed out.
10 698 ms 676 ms 678 ms rbx-g2-a9.fr.eu [91.121.131.177]
11 708 ms 672 ms 745 ms vss-3-6k.fr.eu [213.251.130.77]
12 703 ms 699 ms 728 ms ns345728.ip-188-165-200.eu [188.165.200.200]

Trace complete.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X