Can someone using M-Web uncapped ping this IP for me ?

eddief1

eddief1

Expert Member
Joined
Feb 26, 2008
Messages
1,523
Reaction score
301
I am getting 196ms using webafrica prepaid, can someone try this for me from a 4mbps M-Web uncapped business or standard account. Thanks guys.

84.234.16.101

ED
 
C:\Users\*>ping 84.234.16.101 -t

Pinging 84.234.16.101 with 32 bytes of data:
Reply from 84.234.16.101: bytes=32 time=211ms TTL=51
Reply from 84.234.16.101: bytes=32 time=280ms TTL=51
Reply from 84.234.16.101: bytes=32 time=321ms TTL=51
Reply from 84.234.16.101: bytes=32 time=242ms TTL=51
Request timed out.
Reply from 84.234.16.101: bytes=32 time=278ms TTL=51
Reply from 84.234.16.101: bytes=32 time=301ms TTL=51
Reply from 84.234.16.101: bytes=32 time=214ms TTL=51
Reply from 84.234.16.101: bytes=32 time=222ms TTL=51
Reply from 84.234.16.101: bytes=32 time=242ms TTL=51
Reply from 84.234.16.101: bytes=32 time=220ms TTL=51
Reply from 84.234.16.101: bytes=32 time=248ms TTL=51
Reply from 84.234.16.101: bytes=32 time=347ms TTL=51
Reply from 84.234.16.101: bytes=32 time=660ms TTL=51
Reply from 84.234.16.101: bytes=32 time=762ms TTL=51
Reply from 84.234.16.101: bytes=32 time=284ms TTL=51
Reply from 84.234.16.101: bytes=32 time=234ms TTL=51
Reply from 84.234.16.101: bytes=32 time=309ms TTL=51
Reply from 84.234.16.101: bytes=32 time=252ms TTL=51
Reply from 84.234.16.101: bytes=32 time=252ms TTL=51

Ping statistics for 84.234.16.101:
Packets: Sent = 20, Received = 19, Lost = 1 (5% l
Approximate round trip times in milli-seconds:
Minimum = 211ms, Maximum = 762ms, Average = 309ms
 
There is something wrong today ping is 530ms to that ip from 4MB MWEB Account. 736ms 4MB IS Account
 
Thanks guys, appreciate it...looks like webafrica have a better connection to london, i get 196ms constant on the prepaid account...but alas it's so expensive per GB...Wonder if the 'business class' uncapped would yield better results ?
 
eddief1 said:
Thanks guys, appreciate it...looks like webafrica have a better connection to london, i get 196ms constant on the prepaid account...but alas it's so expensive per GB...Wonder if the 'business class' uncapped would yield better results ?
Click to expand...

Starting to feel like a tape recorder today.

Ask the openweb GOLD uncapped guys to ping that IP for you.
 
everything is so slooooooowwwwwwwww today omf. My 4mb line is now a 256k line.

btw I ping 549ms.
 
eddief1 said:
I am getting 196ms using webafrica prepaid, can someone try this for me from a 4mbps M-Web uncapped business or standard account. Thanks guys.

84.234.16.101

ED
Click to expand...

384kbps MWeb Connect uncapped shaped account:

Code: 
$ ping 84.234.16.101
PING 84.234.16.101 (84.234.16.101) 56(84) bytes of data.
64 bytes from 84.234.16.101: icmp_seq=1 ttl=54 time=570 ms
64 bytes from 84.234.16.101: icmp_seq=2 ttl=54 time=564 ms
64 bytes from 84.234.16.101: icmp_seq=3 ttl=54 time=551 ms
64 bytes from 84.234.16.101: icmp_seq=4 ttl=54 time=558 ms
64 bytes from 84.234.16.101: icmp_seq=5 ttl=54 time=561 ms
64 bytes from 84.234.16.101: icmp_seq=6 ttl=54 time=565 ms
64 bytes from 84.234.16.101: icmp_seq=7 ttl=54 time=567 ms
64 bytes from 84.234.16.101: icmp_seq=8 ttl=54 time=561 ms
64 bytes from 84.234.16.101: icmp_seq=9 ttl=54 time=556 ms
 
Not M-Web but putting it out there for fun:

Code: 
root@****cmon2:~# ping -c 4 84.234.16.101
PING 84.234.16.101 (84.234.16.101) 56(84) bytes of data.
64 bytes from 84.234.16.101: icmp_seq=1 ttl=56 time=153 ms
64 bytes from 84.234.16.101: icmp_seq=2 ttl=56 time=153 ms
64 bytes from 84.234.16.101: icmp_seq=3 ttl=56 time=153 ms
64 bytes from 84.234.16.101: icmp_seq=4 ttl=56 time=153 ms

--- 84.234.16.101 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 153.333/153.430/153.525/0.487 ms
DSL line might add another 10ms or so.
 
also just for fun... :)

N:\>PING 84.234.16.101

Pinging 84.234.16.101 with 32 bytes of data:


N:\>PING 84.234.16.101 -t

Pinging 84.234.16.101 with 32 bytes of data:

Reply from 84.234.16.101: bytes=32 time=159ms TTL=52
Reply from 84.234.16.101: bytes=32 time=228ms TTL=52
Reply from 84.234.16.101: bytes=32 time=159ms TTL=52
Reply from 84.234.16.101: bytes=32 time=160ms TTL=52
Reply from 84.234.16.101: bytes=32 time=159ms TTL=52
Reply from 84.234.16.101: bytes=32 time=159ms TTL=52
Reply from 84.234.16.101: bytes=32 time=159ms TTL=52
Reply from 84.234.16.101: bytes=32 time=160ms TTL=52
Reply from 84.234.16.101: bytes=32 time=160ms TTL=52
Reply from 84.234.16.101: bytes=32 time=159ms TTL=52
Reply from 84.234.16.101: bytes=32 time=160ms TTL=52
Reply from 84.234.16.101: bytes=32 time=159ms TTL=52
Reply from 84.234.16.101: bytes=32 time=164ms TTL=52
Reply from 84.234.16.101: bytes=32 time=159ms TTL=52
Reply from 84.234.16.101: bytes=32 time=159ms TTL=52
Reply from 84.234.16.101: bytes=32 time=161ms TTL=52
Reply from 84.234.16.101: bytes=32 time=161ms TTL=52

Ping statistics for 84.234.16.101:
Packets: Sent = 17, Received = 17, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 159ms, Maximum = 228ms, Average = 163ms
C
Click to expand...
 
PING 84.234.16.101 (84.234.16.101): 56 data bytes
64 bytes from 84.234.16.101: icmp_seq=0 ttl=51 time=176.848 ms
64 bytes from 84.234.16.101: icmp_seq=1 ttl=51 time=177.426 ms
64 bytes from 84.234.16.101: icmp_seq=2 ttl=51 time=177.519 ms
64 bytes from 84.234.16.101: icmp_seq=3 ttl=51 time=178.007 ms
64 bytes from 84.234.16.101: icmp_seq=4 ttl=51 time=177.905 ms
64 bytes from 84.234.16.101: icmp_seq=5 ttl=51 time=177.200 ms
64 bytes from 84.234.16.101: icmp_seq=6 ttl=51 time=176.853 ms
64 bytes from 84.234.16.101: icmp_seq=0 ttl=51 time=176.681 ms
64 bytes from 84.234.16.101: icmp_seq=1 ttl=51 time=176.663 ms
64 bytes from 84.234.16.101: icmp_seq=2 ttl=51 time=176.892 ms
Click to expand...

Now I feel small :(
 
Phoned MWEB Support. Mweb blaming Telkom for the outage in Fourways. Switched to backup prepaid account and It flies.
 
Mweb uncapped unshaped (4MBbit)

Tracing route to srv120.dedicated.netrino.co.uk [84.234.16.101]
over a maximum of 30 hops:
0 **** (local)
1 **** (local)
2 **** (local)
3 tengig-0-0-0-104.vic-ipc-1.mweb.co.za [196.22.169.146]
4 vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
5 tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.169.225]
6 tengig-0-2-0-0.mid-1.mweb.co.za [196.22.169.219]
7 pos-0-0-0-0.lon-1.mweb.co.za [196.22.163.230]
8 linx-brocade1.netrino.co.uk [195.66.225.18]
9 bs1-core.netrino.co.uk [84.234.19.5]
10 srv120.dedicated.netrino.co.uk [84.234.16.101]

Computing statistics for 250 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 **** (local) 0/ 100 = 0% |
1 1ms 0/ 100 = 0% 0/ 100 = 0% **** (local) 0/ 100 = 0% |
2 372ms 0/ 100 = 0% 0/ 100 = 0% **** (local) 0/ 100 = 0% |
3 374ms 0/ 100 = 0% 0/ 100 = 0% tengig-0-0-0-104.vic-ipc-1.mweb.co.za [196.22.169.146] 0/ 100 = 0% |
4 267ms 0/ 100 = 0% 0/ 100 = 0% vl-92.vic-hscore-1.mweb.co.za [196.22.189.2] 0/ 100 = 0% |
5 395ms 0/ 100 = 0% 0/ 100 = 0% tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.169.225] 0/ 100 = 0% |
6 322ms 0/ 100 = 0% 0/ 100 = 0% tengig-0-2-0-0.mid-1.mweb.co.za [196.22.169.219] 0/ 100 = 0% |
7 493ms 0/ 100 = 0% 0/ 100 = 0% pos-0-0-0-0.lon-1.mweb.co.za [196.22.163.230] 0/ 100 = 0% |
8 481ms 0/ 100 = 0% 0/ 100 = 0% linx-brocade1.netrino.co.uk [195.66.225.18] 0/ 100 = 0% |
9 600ms 0/ 100 = 0% 0/ 100 = 0% bs1-core.netrino.co.uk [84.234.19.5] 0/ 100 = 0% |
10 459ms 0/ 100 = 0% 0/ 100 = 0% srv120.dedicated.netrino.co.uk [84.234.16.101]

Trace complete.
 
4meg OW Gold

Pinging 84.234.16.101 with 32 bytes of data:
Reply from 84.234.16.101: bytes=32 time=258ms TTL=54
Reply from 84.234.16.101: bytes=32 time=258ms TTL=54
Reply from 84.234.16.101: bytes=32 time=257ms TTL=54
Reply from 84.234.16.101: bytes=32 time=259ms TTL=54

Ping statistics for 84.234.16.101:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 257ms, Maximum = 259ms, Average = 258ms
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X