Ping This IP (ISP result)

Grizz · Jul 24, 2013

FlatspinZA said:
Is it just me, or does anyone else see a problem with these pings?

yes lol, any ping result with more than 230+ is bad imo.

agentrfr · Jul 24, 2013

Openweb 4meg Gold
Sandton, Gauteng

Code:

C:\Users\Admin>ping 94.242.253.107

Pinging 94.242.253.107 with 32 bytes of data:
Reply from 94.242.253.107: bytes=32 time=189ms TTL=52
Reply from 94.242.253.107: bytes=32 time=189ms TTL=52
Reply from 94.242.253.107: bytes=32 time=188ms TTL=52
Reply from 94.242.253.107: bytes=32 time=189ms TTL=52

Ping statistics for 94.242.253.107:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 188ms, Maximum = 189ms, Average = 188ms

Although you can take out 25ms if you are in Capetown, so expect about 163ms.

Hummercellc · Jul 24, 2013

Pinging 94.242.253.107 with 32 bytes of data:
Reply from 94.242.253.107: bytes=32 time=232ms TTL=50
Reply from 94.242.253.107: bytes=32 time=229ms TTL=50
Reply from 94.242.253.107: bytes=32 time=229ms TTL=50
Reply from 94.242.253.107: bytes=32 time=229ms TTL=50

Ping statistics for 94.242.253.107:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 229ms, Maximum = 232ms, Average = 229ms

Afrihost 10mbps Pietermartizburg....

wingnut771 · Jul 24, 2013

ISP: Plugg 4mb Uncapped
Area: Durban

Pinging 94.242.253.107 with 32 bytes of data:
Reply from 94.242.253.107: bytes=32 time=208ms TTL=52
Reply from 94.242.253.107: bytes=32 time=207ms TTL=52
Reply from 94.242.253.107: bytes=32 time=207ms TTL=52
Reply from 94.242.253.107: bytes=32 time=207ms TTL=52

Ping statistics for 94.242.253.107:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 207ms, Maximum = 208ms, Average = 207ms

ElecEng · Jul 24, 2013

Neotel fibre cape town, although i feel it is routed through joburg anyway, right?

Pinging 94.242.253.107 with 32 bytes of data:
Reply from 94.242.253.107: bytes=32 time=165ms TTL=47
Reply from 94.242.253.107: bytes=32 time=163ms TTL=47
Reply from 94.242.253.107: bytes=32 time=163ms TTL=47
Reply from 94.242.253.107: bytes=32 time=163ms TTL=47

Ping statistics for 94.242.253.107:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 163ms, Maximum = 165ms, Average = 163ms

MDE · Jul 24, 2013

WISP. Amobia.com

--- 24 Jul 2013 16:58:26
--- IP (wlan0) 192.168.8.230

PING 94.242.253.107 (94.242.253.107) 56(84) bytes of data.
64 bytes from 94.242.253.107: icmp_seq=1 ttl=50 time=170 ms
64 bytes from 94.242.253.107: icmp_seq=2 ttl=50 time=178 ms
64 bytes from 94.242.253.107: icmp_seq=3 ttl=50 time=169 ms

--- 94.242.253.107 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2001ms
min = 169.380 ms
avg = 172.826 ms
max = 178.830 ms
mdev = 4.274 ms

Cosmic_Nomad · Jul 24, 2013

Telkom uncapped #2MB
Durban

timo@flycatcher ~ $ ping 94.242.253.107
PING 94.242.253.107 (94.242.253.107) 56(84) bytes of data.
64 bytes from 94.242.253.107: icmp_req=1 ttl=53 time=260 ms
64 bytes from 94.242.253.107: icmp_req=2 ttl=53 time=262 ms
64 bytes from 94.242.253.107: icmp_req=3 ttl=53 time=260 ms
64 bytes from 94.242.253.107: icmp_req=4 ttl=53 time=256 ms
64 bytes from 94.242.253.107: icmp_req=6 ttl=53 time=252 ms
64 bytes from 94.242.253.107: icmp_req=7 ttl=53 time=261 ms

Malooga · Jul 24, 2013

Hi, i had a go as well

C:\Users\Chris-home>ping -n 10 94.242.253.107

Pinging 94.242.253.107 with 32 bytes of data:
Reply from 94.242.253.107: bytes=32 time=196ms TTL=51
Reply from 94.242.253.107: bytes=32 time=185ms TTL=51
Reply from 94.242.253.107: bytes=32 time=191ms TTL=51
Reply from 94.242.253.107: bytes=32 time=194ms TTL=51
Reply from 94.242.253.107: bytes=32 time=194ms TTL=51
Reply from 94.242.253.107: bytes=32 time=188ms TTL=51
Reply from 94.242.253.107: bytes=32 time=187ms TTL=51
Reply from 94.242.253.107: bytes=32 time=190ms TTL=51
Reply from 94.242.253.107: bytes=32 time=185ms TTL=51
Reply from 94.242.253.107: bytes=32 time=186ms TTL=51

Ping statistics for 94.242.253.107:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 185ms, Maximum = 196ms, Average = 189ms

Plumstead, cape town.
Afrihost 10meg line, uncapped.

C:\Users\Chris-home>tracert 94.242.253.107

Tracing route to foco.co [94.242.253.107]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms login.router [10.0.0.2]
2 8 ms 25 ms 9 ms 105-236-9-65-esr-lo.mtnbusiness.co.za [105.236.9.65]
3 15 ms 16 ms 18 ms 41.181.221.254
4 8 ms 12 ms 7 ms 41.181.184.28
5 23 ms 17 ms 12 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 9 ms 8 ms 8 ms 196.44.31.106
7 199 ms 191 ms 193 ms am-cr-1.am--lt-cr-1.uk-a.mtnns.net [196.44.31.221]
8 161 ms 152 ms 158 ms ls-pr-1.uk--ls-cr-1.uk-a.mtn.net [209.212.111.83]
9 154 ms 156 ms 176 ms peering.linx.eu.iptransit.com [195.66.225.106]
10 188 ms 184 ms 191 ms te2-1.r1.lux.iptransit.com [199.59.206.134]
11 164 ms 185 ms 178 ms te-9-2.r1.stnsl.lux.as5577.net [199.59.206.26]
12 * 181 ms 167 ms 100g.bissen.lux.as5577.net [83.243.12.2]
13 163 ms 175 ms 163 ms foco.co [94.242.253.106]
14 188 ms 190 ms 189 ms foco.co [94.242.253.107]

Trace complete.

ld13 · Jul 24, 2013

Pings from Cape Town / Helderberg on a 1mbps line

Capped Afrihost:
Reply from 94.242.253.107: bytes=32 time=164ms TTL=53

Capped Mweb:
Reply from 94.242.253.107: bytes=32 time=165ms TTL=53

Capped WebAfrica:
Reply from 94.242.253.107: bytes=32 time=169ms TTL=49

Capped SAINET:
Reply from 94.242.253.107: bytes=32 time=230ms TTL=51

Malooga · Jul 24, 2013

ld13 said:
Pings from Cape Town / Helderberg on a 1mbps line

Capped Afrihost:
Reply from 94.242.253.107: bytes=32 time=164ms TTL=53

Witchcraft !?!

ld13 · Jul 24, 2013

Malooga said:
Witchcraft !?!

Nein

Reply from 94.242.253.107: bytes=32 time=165ms TTL=53
Reply from 94.242.253.107: bytes=32 time=164ms TTL=53
Reply from 94.242.253.107: bytes=32 time=165ms TTL=53
Reply from 94.242.253.107: bytes=32 time=165ms TTL=53
Reply from 94.242.253.107: bytes=32 time=164ms TTL=53
Reply from 94.242.253.107: bytes=32 time=164ms TTL=53

PostmanPot · Jul 24, 2013

MWEB/Cape Town:

Pinging 94.242.253.107 with 32 bytes of data:
Reply from 94.242.253.107: bytes=32 time=164ms TTL=51
Reply from 94.242.253.107: bytes=32 time=162ms TTL=51
Reply from 94.242.253.107: bytes=32 time=163ms TTL=51
Reply from 94.242.253.107: bytes=32 time=163ms TTL=51

Tinuva · Jul 24, 2013

Web Africa/Cape Town

C:\Users\Tinuva>ping 94.242.253.107

Pinging 94.242.253.107 with 32 bytes of data:
Reply from 94.242.253.107: bytes=32 time=169ms TTL=49
Reply from 94.242.253.107: bytes=32 time=167ms TTL=49
Reply from 94.242.253.107: bytes=32 time=167ms TTL=49
Reply from 94.242.253.107: bytes=32 time=176ms TTL=49

Ping statistics for 94.242.253.107:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 167ms, Maximum = 176ms, Average = 169ms

Chevron · Jul 24, 2013

While streaming twitch at 720p on Openweb Gold JHB:

Pinging 94.242.253.107 with 32 bytes of data:
Reply from 94.242.253.107: bytes=32 time=189ms TTL=53
Reply from 94.242.253.107: bytes=32 time=208ms TTL=53
Reply from 94.242.253.107: bytes=32 time=188ms TTL=53
Reply from 94.242.253.107: bytes=32 time=187ms TTL=53

Ping statistics for 94.242.253.107:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 187ms, Maximum = 208ms, Average = 193ms

Chevron · Jul 24, 2013

So looks like we can tell what city people are in from their pings.

170 - CPT
190 - JHB
210 - DBN

Malooga · Jul 25, 2013

Another from CPT, Mweb...1meg connection...

C:\Users\Chris-home>ping -n 10 94.242.253.107

Pinging 94.242.253.107 with 32 bytes of data:
Reply from 94.242.253.107: bytes=32 time=169ms TTL=52
Reply from 94.242.253.107: bytes=32 time=167ms TTL=52
Reply from 94.242.253.107: bytes=32 time=168ms TTL=52
Reply from 94.242.253.107: bytes=32 time=169ms TTL=52
Reply from 94.242.253.107: bytes=32 time=167ms TTL=52
Reply from 94.242.253.107: bytes=32 time=168ms TTL=52
Reply from 94.242.253.107: bytes=32 time=168ms TTL=52
Reply from 94.242.253.107: bytes=32 time=168ms TTL=52
Reply from 94.242.253.107: bytes=32 time=168ms TTL=52
Reply from 94.242.253.107: bytes=32 time=167ms TTL=52

Ping statistics for 94.242.253.107:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 167ms, Maximum = 169ms, Average = 167ms

C:\Users\Chris-home>tracert 94.242.253.107

Tracing route to foco.co [94.242.253.107]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms www.asusnetwork.net [192.168.1.1]
2 14 ms 12 ms 14 ms 41-132-74-1.dsl.mweb.co.za [41.132.74.1]
3 12 ms 15 ms 15 ms te1-1-0.505.cpt-ipc-1.mweb.co.za [196.28.178.178]
4 15 ms 14 ms 15 ms 197-84-2-2.cpt.mweb.co.za [197.84.2.2]
5 198 ms 199 ms 199 ms 197-84-5-226.cpt.mweb.co.za [197.84.5.226]
6 164 ms 163 ms 162 ms 197-84-4-197.cpt.mweb.co.za [197.84.4.197]
7 165 ms 160 ms 177 ms 176.67.177.148
8 161 ms 164 ms 163 ms 176.67.177.236
9 159 ms 159 ms 159 ms peering.linx.eu.iptransit.com [195.66.225.106]
10 168 ms 173 ms 167 ms te2-1.r1.lux.iptransit.com [199.59.206.134]
11 173 ms 170 ms 173 ms te-7-3.r1.stnsl.lux.as5577.net [199.59.206.30]
12 168 ms 168 ms 169 ms 100g.bissen.lux.as5577.net [83.243.12.2]
13 169 ms 168 ms 167 ms foco.co [94.242.253.106]
14 168 ms 167 ms 168 ms foco.co [94.242.253.107]

Trace complete.

This is making me realise there may be something wrong with my home connection.

blunt · Jul 25, 2013

4MB Afrihost Uncapped CPT

64 bytes from 94.242.253.107: icmp_seq=1 ttl=52 time=173.279 ms
64 bytes from 94.242.253.107: icmp_seq=2 ttl=52 time=165.217 ms
64 bytes from 94.242.253.107: icmp_seq=3 ttl=52 time=166.148 ms
64 bytes from 94.242.253.107: icmp_seq=4 ttl=52 time=171.099 ms
64 bytes from 94.242.253.107: icmp_seq=5 ttl=52 time=165.864 ms
64 bytes from 94.242.253.107: icmp_seq=6 ttl=52 time=164.198 ms
64 bytes from 94.242.253.107: icmp_seq=7 ttl=52 time=172.314 ms

CaffeinePirate · Jul 25, 2013

Kzn Midlands, Jireh on Neotel

Ping 94.242.253.107
Round trip time to 94.242.253.107: 120 ms
Round trip time to 94.242.253.107: 120 ms
Round trip time to 94.242.253.107: 120 ms
Round trip time to 94.242.253.107: 120 ms
Round trip time to 94.242.253.107: 120 ms
Round trip time to 94.242.253.107: 120 ms
Round trip time to 94.242.253.107: 120 ms
Round trip time to 94.242.253.107: 120 ms
Round trip time to 94.242.253.107: 120 ms
Round trip time to 94.242.253.107: 120 ms
Average time over 10 pings: 120 ms

Grizz · Jul 25, 2013

CaffeinePirate said:
Kzn Midlands, Jireh on Neotel

Ping 94.242.253.107
Round trip time to 94.242.253.107: 120 ms
Round trip time to 94.242.253.107: 120 ms
Round trip time to 94.242.253.107: 120 ms
Round trip time to 94.242.253.107: 120 ms
Round trip time to 94.242.253.107: 120 ms
Round trip time to 94.242.253.107: 120 ms
Round trip time to 94.242.253.107: 120 ms
Round trip time to 94.242.253.107: 120 ms
Round trip time to 94.242.253.107: 120 ms
Round trip time to 94.242.253.107: 120 ms
Average time over 10 pings: 120 ms

WTF

ponder · Jul 25, 2013

Grizz said:
WTF

c is no longer a constant!!!

Join the MyBroadband community

Get started

Ping This IP (ISP result)

Well-Known Member

Executive Member

Expert Member

Honorary Master

Senior Member

Expert Member

Senior Member

Well-Known Member

Honorary Master

Well-Known Member

Honorary Master

Honorary Master

The Magician

Serial breaker of phones

Serial breaker of phones

Well-Known Member

Expert Member

Well-Known Member

Well-Known Member

Honorary Master