Could be a port error of sorts.
If you're still down now shoot me a PM with your DSL username and I'll get it checked out.
-
Join the MyBroadband community
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
-
Question of the Day: Are you keeping your Prime subscription?
- Status
Could be a port error of sorts.
If you're still down now shoot me a PM with your DSL username and I'll get it checked out.
wingnut771
Honorary Master
Nothing wrong with saving int traffic, but not having enough int traffic where things buffer is wrong.
wingnut771
Honorary Master
I'm not, no, but then I'm not in Cape Town.
I'm not sure I follow?
Icemanbrfc
Honorary Master
i was streaming the Barcelona game last night with no issues... The only time it buffered, was when Barca scored their 7th goal. Think my internet couldnt believe the score line 
My DSL was perfect for the past week, yesterday it went back to the usual garbage. Streaming struggling, playstation network downloads struggling to hit 2mbps on a 20mbps line, in game pings of about 120ms to local mweb servers.
I'm absolutely fed up, this issue has been on and off randomly for people in Durban for weeks now and to me it seems like all afrihost does is HOPES that the problem sorts itself out, and then when it resurfaces, claims to be looking into it. How many more tracerts and ping tests do you want? Do I pay R800pm to Afrihost so that I can sit and run tracerts all day?
I'm absolutely fed up, this issue has been on and off randomly for people in Durban for weeks now and to me it seems like all afrihost does is HOPES that the problem sorts itself out, and then when it resurfaces, claims to be looking into it. How many more tracerts and ping tests do you want? Do I pay R800pm to Afrihost so that I can sit and run tracerts all day?
Icemanbrfc
Honorary Master
did you indicate to the guys, that for the past week things were perfect? Because now its not, now you dont want to provide tests so the guys can actually see what has changed? strange
Bit unfair to Afrihost imo
Sorry to hear about the hassles here.
I see the last post you mentioned similar issues, although these have all been cleared up.
What DNS servers are you currently using?
I have a friend on Afrihost as well, from Durban as well, yesterday we we're both playing with 100ms ping on afrihost, we both had streaming issues, both of our issues were resolved when we switched to alternate ISPs.
If this was the first time I've been having these specific issues, fair enough I'm being unreasonable, but this has been an ongoing issue, and every time it happens I must sit and send daily tracerts in hope that it sorts out?
I think you misunderstand what Afrihost is, it's a business, not a free service. I pay for it and thus expect a certain level of quality, and it's quiet simple, if issues don't resolve by the 23rd, I'll just be cancelling and going elsewhere.
AUTO DNS, I don't fiddle with any of the modem settings. Everything worked fine up until about 2PM yesterday then it started it's usual issues
Not aware of any overall issues in the region or our network, I'm afraid I'll need to take a look at some test results.
If you'd prefer I can escalate your query through to our Critical Care team so you have a single point of contact?
Here are some tracerts. This is the last time I'm doing this. First one is to a filesharing host in europe that I use, second one is a game server run by mweb.
C:\WINDOWS\system32>tracert www.rapidgator.net
Tracing route to www.rapidgator.net [195.211.221.116]
over a maximum of 30 hops:
1 2 ms 1 ms 2 ms 192.168.1.1
2 * * * Request timed out.
3 27 ms 27 ms 26 ms dbn-up2.ip.adsl.co.za [169.1.5.174]
4 27 ms 27 ms 26 ms dbn-in1.ip.adsl.co.za [169.1.5.204]
5 26 ms 27 ms 26 ms 41.162.84.192
6 34 ms 35 ms 38 ms 172.18.1.162
7 34 ms * * if-ae-7-0.tcore2.JSO-Johannesburg.as6453.net [41.206.179.13]
8 220 ms 249 ms 220 ms if-ae-2-2.tcore1.JSO-Johannesburg.as6453.net [216.6.55.85]
9 217 ms 217 ms 218 ms if-ae-4-2.tcore1.KLT-Cape-Town.as6453.net [41.206.178.2]
10 212 ms 214 ms 210 ms if-ae-5-2.tcore2.PV9-Lisbon.as6453.net [80.231.159.129]
11 227 ms 210 ms 213 ms if-ae-7-2.tcore2.WV6-Madrid.as6453.net [80.231.159.30]
12 211 ms 210 ms 210 ms if-ae-11-2.tcore1.WV6-Madrid.as6453.net [80.231.91.65]
13 221 ms 210 ms 211 ms if-ae-5-2.tcore2.WYN-Marseille.as6453.net [80.231.200.5]
14 210 ms 211 ms 210 ms if-ae-7-2.tcore2.FNM-Frankfurt.as6453.net [80.231.200.78]
15 214 ms 213 ms 211 ms if-ae-12-2.tcore1.FNM-Frankfurt.as6453.net [195.219.87.2]
16 212 ms 211 ms 210 ms if-ae-2-2.thar1.F2C-Frankfurt.as6453.net [195.219.156.130]
17 211 ms 211 ms 211 ms 195.219.148.90
18 251 ms 252 ms 252 ms pe26.Moscow.gldn.net [79.104.225.59]
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
C:\WINDOWS\system32>tracert 197.80.200.161
Tracing route to 197-80-200-161.jhb.mweb.co.za [197.80.200.161]
over a maximum of 30 hops:
1 2 ms 2 ms 2 ms 192.168.1.1
2 * * * Request timed out.
3 28 ms 27 ms 26 ms dbn-up2.ip.adsl.co.za [169.1.5.174]
4 27 ms 26 ms 27 ms dbn-in1.ip.adsl.co.za [169.1.5.204]
5 * 90 ms 90 ms optinet.ixp.durban [196.10.141.75]
6 105 ms 106 ms 106 ms 197-82-7-1.dbn.mweb.co.za [197.82.7.1]
7 103 ms 105 ms 102 ms te0-0-0-0.vic-p-1.optinet.net [197.84.4.38]
8 * 101 ms 101 ms 101.bu-ether5.vic-pe-1.optinet.net [197.80.7.9]
9 101 ms 101 ms 101 ms bu-ether3.mca-pe-1.optinet.net [197.80.4.37]
10 100 ms * 100 ms 197-80-96-30.jhb.mweb.co.za [197.80.96.30]
11 100 ms 101 ms 100 ms 197-80-200-161.jhb.mweb.co.za [197.80.200.161]
Trace complete.
C:\WINDOWS\system32>
ping test that was requested the last time.
C:\WINDOWS\system32>ping bras.afrihost.com
Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=26ms TTL=63
Reply from 155.239.255.250: bytes=32 time=26ms TTL=63
Reply from 155.239.255.250: bytes=32 time=25ms TTL=63
Reply from 155.239.255.250: bytes=32 time=26ms TTL=63
Ping statistics for 155.239.255.250:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 25ms, Maximum = 26ms, Average = 25ms
I know troubleshooting can be tedious, but without it, it's impossible to tell what's going wrong and where.
Would you not prefer to talk to someone as opposed to running tests and posting them on the forum?
I'd prefer the problem is sorted out as soon as possible, would talking to someone expedite the troubleshooting process? If so I'll go that route.
Seeing as I'm having the same issues that I was having a couple weeks ago along with the other guys in Durban, can you tell me how afrihost solved that problem then? Surely if the network engineers fixed that issue as opposed to just waiting for it to fix itself, your network guys should have a solution ready to implement immediately?
Charmingmage10
Well-Known Member
Same problems...
Vorastra
Honorary Master
Is there currently something affecting P2P? Has shaping finally kicked in after all these months? Clientzone says there is no shaping at the moment.
Also another question. Does P2P get shaped before HTTP downloads or do they get shaped at the same time? I ask because I test shaping in general by trying an HTTP download from Nvidia or something.
Also another question. Does P2P get shaped before HTTP downloads or do they get shaped at the same time? I ask because I test shaping in general by trying an HTTP download from Nvidia or something.
I understand you're frustrated, but if we aren't seeing any trends in the region and we can't spot an issue on our end, troubleshooting is the only way to go.
You're welcome to PM me your account info and I'll put you in touch with our Critical Care team.
I do need to stress though, if we're aware of an issue in the area we'll fix it. But we can't implement a fix if we can't see anything wrong.
Any tests I can take a look at?
- Status