MWEB Uncapped Subscribers Feedback

Status
Not open for further replies.
MWEB Guy said:
Thanks for the information, the results you have provided reflects that your connection is better with MWEB than with Afrihost.
Click to expand...

Thanks, I will tell myself this, next time I stare at a page that's not loading. :erm:

*edit*

Time to try Openweb, I think.
 
MWEB Guy said:
Thanks for the information, the results you have provided reflects that your connection is better with MWEB than with Afrihost.
Click to expand...

How so? Both trace routes get there in 10 hops with a small difference in the times. The ping results are better on Afrihost than MWEB.
 
copacetic said:
Thanks, I will tell myself this, next time I stare at a page that's not loading. :erm:

*edit*

Time to try Openweb, I think.
Click to expand...

SabreWolfy said:
How so? Both trace routes get there in 10 hops with a small difference in the times. The ping results are better on Afrihost than MWEB.
Click to expand...


You are correct Sabrewolfy, the ping results are better on the Afrihost account.

Copacetic, please advise if you are just browsing when your pages dont load?
 
Pinging www.isgaming.co.za [196.38.180.2] with 32 bytes of data:
Reply from 196.38.180.2: bytes=32 time=13ms TTL=53
Reply from 196.38.180.2: bytes=32 time=55ms TTL=53
Request timed out.
Reply from 196.38.180.2: bytes=32 time=13ms TTL=53
Reply from 196.38.180.2: bytes=32 time=13ms TTL=53
Reply from 196.38.180.2: bytes=32 time=12ms TTL=53
Request timed out.
Request timed out.
Request timed out.
Reply from 196.38.180.2: bytes=32 time=12ms TTL=53
Request timed out.
Request timed out.
Reply from 196.38.180.2: bytes=32 time=13ms TTL=53
Reply from 196.38.180.2: bytes=32 time=12ms TTL=53
Request timed out.
Request timed out.
Request timed out.
Reply from 196.38.180.2: bytes=32 time=13ms TTL=53
Reply from 196.38.180.2: bytes=32 time=12ms TTL=53
Request timed out.
Reply from 196.38.180.2: bytes=32 time=12ms TTL=53
Request timed out.
Reply from 196.38.180.2: bytes=32 time=12ms TTL=53
Request timed out.
 
now it's timing out not even 1 png wtf is going on please as I want to chat via teamspeak. Also battlefield 3 crashed for me and my friend at same time
 
MWEB Guy said:
You are correct Sabrewolfy, the ping results are better on the Afrihost account.

Copacetic, please advise if you are just browsing when your pages dont load?
Click to expand...

Anyone else think that Mweb Guy's comments have become completely useless? I mean look at this, so people get him the info he asks for, you guys do the work, check back to see if anything useful is posted and this is what you get. Its pretty bad, I hope Mweb gets a better representative in here because Mweb Guy has been useless for months.
 
MWEB Guy said:
You are correct Sabrewolfy, the ping results are better on the Afrihost account.

Copacetic, please advise if you are just browsing when your pages dont load?
Click to expand...

Yep, just browsing, no sense in torrents or anything during the daylight hours, as they don't work, and obviously I'm not going to download, and then try surf at the same time and complain about it.
 
copacetic said:
Yep, just browsing, no sense in torrents or anything during the daylight hours, as they don't work, and obviously I'm not going to download, and then try surf at the same time and complain about it.
Click to expand...

Thanks for the information, please advise which router you are currently using?
 
Last edited:
Pinging www.isgaming.co.za [196.38.180.2] with 32 bytes of data:
Reply from 196.38.180.2: bytes=32 time=15ms TTL=56
Reply from 196.38.180.2: bytes=32 time=13ms TTL=56
Reply from 196.38.180.2: bytes=32 time=29ms TTL=56
Reply from 196.38.180.2: bytes=32 time=22ms TTL=56
Reply from 196.38.180.2: bytes=32 time=15ms TTL=56
Reply from 196.38.180.2: bytes=32 time=32ms TTL=56
Reply from 196.38.180.2: bytes=32 time=37ms TTL=56
Reply from 196.38.180.2: bytes=32 time=22ms TTL=56
Reply from 196.38.180.2: bytes=32 time=12ms TTL=56
Reply from 196.38.180.2: bytes=32 time=30ms TTL=56
Reply from 196.38.180.2: bytes=32 time=11ms TTL=56
Reply from 196.38.180.2: bytes=32 time=20ms TTL=56
Reply from 196.38.180.2: bytes=32 time=13ms TTL=56
Reply from 196.38.180.2: bytes=32 time=11ms TTL=56
Reply from 196.38.180.2: bytes=32 time=12ms TTL=56
Reply from 196.38.180.2: bytes=32 time=11ms TTL=56
Reply from 196.38.180.2: bytes=32 time=11ms TTL=56
Reply from 196.38.180.2: bytes=32 time=11ms TTL=56
Reply from 196.38.180.2: bytes=32 time=11ms TTL=56
Reply from 196.38.180.2: bytes=32 time=22ms TTL=56
Reply from 196.38.180.2: bytes=32 time=25ms TTL=56
Reply from 196.38.180.2: bytes=32 time=14ms TTL=56
Reply from 196.38.180.2: bytes=32 time=12ms TTL=56
Reply from 196.38.180.2: bytes=32 time=13ms TTL=56
Reply from 196.38.180.2: bytes=32 time=15ms TTL=56
Reply from 196.38.180.2: bytes=32 time=12ms TTL=56
Reply from 196.38.180.2: bytes=32 time=11ms TTL=56
Reply from 196.38.180.2: bytes=32 time=24ms TTL=56
Reply from 196.38.180.2: bytes=32 time=12ms TTL=56
Reply from 196.38.180.2: bytes=32 time=12ms TTL=56

Ping statistics for 196.38.180.2:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 37ms, Average = 17ms

Telkom Uncapped.
 
As far as I can see I am the only one with this problem MWEB Guy, but it comes and goes....
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X