MWEB Uncapped Subscribers Feedback

Status
Not open for further replies.
Looks like its back again.

Failure at Mweb?

Before:
traceroute: Warning: www.microsoft.com has multiple addresses; using 207.46.170.10
traceroute to lb1.www.ms.akadns.net (207.46.170.10), 30 hops max, 40 byte packets
1 41-133-108-1.dsl.mweb.co.za (41.133.108.1) 7.241 ms 7.646 ms 8.028 ms
2 196-28-178-202.adsl.mweb.co.za (196.28.178.202) 8.313 ms 8.140 ms 8.750 ms
3 196-28-179-11.adsl.mweb.co.za (196.28.179.11) 9.094 ms 8.120 ms 8.079 ms
4 196-28-178-97.adsl.mweb.co.za (196.28.178.97) 9.785 ms 11.404 ms 9.662 ms
5 gig-0-0-1.vic-hscore-3.mweb.co.za (196.22.169.45) 32.272 ms 32.256 ms 31.864 ms
6 196.22.169.61 (196.22.169.61) 33.046 ms 36.152 ms 34.665 ms
7 * * *
Click to expand...

After:
PHP: 
 1  41-133-108-1.dsl.mweb.co.za (41.133.108.1)  7.870 ms  7.672 ms  7.736 ms
 2  196-28-178-166.adsl.mweb.co.za (196.28.178.166)  8.814 ms  8.031 ms  10.853 ms
 3  196-28-179-11.adsl.mweb.co.za (196.28.179.11)  8.227 ms  9.050 ms  8.575 ms
 4  196-28-178-97.adsl.mweb.co.za (196.28.178.97)  9.933 ms  9.725 ms  10.500 ms
 5  gig-0-0-2.vic-hscore-3.mweb.co.za (196.22.169.49)  32.226 ms  32.360 ms  32.166 ms
 6  196.22.169.61 (196.22.169.61)  32.435 ms  36.921 ms  34.898 ms
 7  tengig-0-0-0-0-11.vic-up-2.mweb.co.za (196.22.169.226)  33.033 ms  35.081 ms  34.849 ms
 
Last edited:
Back up. Seems it broke inside MWEB's network.

Code: 
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 40 byte packets
 1  192.168.5.1  0.145 ms  0.120 ms  0.112 ms
 2  41.133.86.1  7.062 ms  8.854 ms  10.172 ms
 3  196.22.169.170  17.057 ms  18.013 ms  19.135 ms
 4  * * *
 5  * * *
 6  * * *

Back up now though.
 
Up but miserably slow


PING www.l.google.com (155.232.240.19): 56 data bytes
64 bytes from 155.232.240.19: icmp_seq=0 ttl=57 time=537.451 ms
64 bytes from 155.232.240.19: icmp_seq=2 ttl=57 time=679.547 ms
64 bytes from 155.232.240.19: icmp_seq=3 ttl=57 time=493.815 ms
64 bytes from 155.232.240.19: icmp_seq=4 ttl=57 time=641.058 ms
64 bytes from 155.232.240.19: icmp_seq=5 ttl=57 time=562.214 ms
64 bytes from 155.232.240.19: icmp_seq=6 ttl=57 time=641.329 ms

:sick:
 
Last edited:
Speed okay here

Pinging www.l.google.com [64.233.179.104] with 32 bytes of data:
Reply from 64.233.179.104: bytes=32 time=13ms TTL=54
Reply from 64.233.179.104: bytes=32 time=13ms TTL=54
Reply from 64.233.179.104: bytes=32 time=12ms TTL=54
Reply from 64.233.179.104: bytes=32 time=12ms TTL=54

Ping statistics for 64.233.179.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 13ms, Average = 12ms
 
Code: 
Pinging www.l.google.com [155.232.240.19] with 32 bytes of
Reply from 155.232.240.19: bytes=32 time=46ms TTL=54
Reply from 155.232.240.19: bytes=32 time=45ms TTL=54
Reply from 155.232.240.19: bytes=32 time=45ms TTL=54
Reply from 155.232.240.19: bytes=32 time=47ms TTL=55
Reply from 155.232.240.19: bytes=32 time=46ms TTL=55
Request timed out.
Request timed out.
Reply from 155.232.240.19: bytes=32 time=47ms TTL=55
Request timed out.
Reply from 155.232.240.19: bytes=32 time=48ms TTL=55
Reply from 155.232.240.19: bytes=32 time=63ms TTL=55
Reply from 155.232.240.19: bytes=32 time=48ms TTL=55
Reply from 155.232.240.19: bytes=32 time=48ms TTL=55
Request timed out.
Reply from 155.232.240.19: bytes=32 time=48ms TTL=55
Request timed out.

Ping statistics for 155.232.240.19:
    Packets: Sent = 16, Received = 11, Lost = 5 (31% loss),
Approximate round trip times in milli-seconds:
    Minimum = 45ms, Maximum = 63ms, Average = 48ms
 
About 30% packet loss, I think something's gone and exploded >.<

All ISP's go through this now and then, MWEB will have it up and running soon, I'm sure.

In the meantime, Afrihost ftw :)
 
Mweb unusable at the mo. Back to my trusty Afrihost back-up account.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X