Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In Register

Quick Links


Categories

In this Discussion

› › Can you ping this IP from Europe?
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Can you ping this IP from Europe?

serverianserverian Member
in General

72.29.87.105

Comments

  • xsetxset Member 
    ping 72.29.87.105
PING 72.29.87.105 (72.29.87.105) 56(84) bytes of data.
64 bytes from 72.29.87.105: icmp_req=1 ttl=47 time=147 ms
64 bytes from 72.29.87.105: icmp_req=2 ttl=47 time=147 ms
64 bytes from 72.29.87.105: icmp_req=3 ttl=47 time=147 ms
^C
--- 72.29.87.105 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 147.124/147.180/147.250/0.446 ms
    Thanked by 1serverian
  • SpiritSpirit Member

    Yes I can.
    Is there any story with this IP? Something you would like to share with us?

  • AmfyAmfy Member
    edited August 2013

    Germany, through Level3:
    $ ping 72.29.87.105 PING 72.29.87.105 (72.29.87.105) 56(84) bytes of data. 64 bytes from 72.29.87.105: icmp_req=1 ttl=51 time=127 ms 64 bytes from 72.29.87.105: icmp_req=2 ttl=51 time=127 ms 64 bytes from 72.29.87.105: icmp_req=3 ttl=51 time=127 ms 64 bytes from 72.29.87.105: icmp_req=4 ttl=51 time=127 ms 64 bytes from 72.29.87.105: icmp_req=5 ttl=51 time=127 ms

    UK
    ping 72.29.87.105 PING 72.29.87.105 (72.29.87.105) 56(84) bytes of data. 64 bytes from 72.29.87.105: icmp_req=1 ttl=52 time=101 ms 64 bytes from 72.29.87.105: icmp_req=2 ttl=52 time=101 ms 64 bytes from 72.29.87.105: icmp_req=3 ttl=52 time=101 ms 64 bytes from 72.29.87.105: icmp_req=4 ttl=52 time=101 ms

    NL, through NTT
    ping 72.29.87.105 PING 72.29.87.105 (72.29.87.105) 56(84) bytes of data. 64 bytes from 72.29.87.105: icmp_req=1 ttl=54 time=125 ms 64 bytes from 72.29.87.105: icmp_req=2 ttl=54 time=126 ms 64 bytes from 72.29.87.105: icmp_req=3 ttl=54 time=126 ms

    Thanked by 1serverian
  • AlexanderMAlexanderM Member, Top Host, Host Rep
    edited August 2013

    UK

    Pinging 72.29.87.105 with 32 bytes of data:

    Reply from 72.29.87.105: bytes=32 time=143ms TTL=49

    Reply from 72.29.87.105: bytes=32 time=142ms TTL=49

    Reply from 72.29.87.105: bytes=32 time=143ms TTL=49

    Reply from 72.29.87.105: bytes=32 time=143ms TTL=49

    Ping statistics for 72.29.87.105:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

    Approximate round trip times in milli-seconds:

    Minimum = 142ms, Maximum = 143ms, Average = 142ms

    Thanked by 1serverian
  • serverianserverian Member

    @Spirit said:
    Yes I can.
    Is there any story with this IP? Something you would like to share with us?

    I'm trying to see if i can fool myself with the idea of miami has good ping to europe :(

  • sundaymousesundaymouse Member

    PING 72.29.87.105 (72.29.87.105): 56 data bytes 64 bytes from 72.29.87.105: icmp_seq=0 ttl=48 time=156.761 ms 64 bytes from 72.29.87.105: icmp_seq=1 ttl=48 time=154.196 ms 64 bytes from 72.29.87.105: icmp_seq=2 ttl=48 time=156.279 ms 64 bytes from 72.29.87.105: icmp_seq=3 ttl=48 time=166.920 ms ^C --- 72.29.87.105 ping statistics --- 4 packets transmitted, 4 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 154.196/158.539/166.920/4.934 ms

    Thanked by 1serverian
  • taronyutaronyu Member

    Netherlands here averaging 121ms.

    Thanked by 1serverian
  • SetsuraSetsura Member
    edited August 2013

    Iceland

    PING 72.29.87.105 (72.29.87.105) 56(84) bytes of data.
64 bytes from 72.29.87.105: icmp_req=1 ttl=57 time=152 ms
64 bytes from 72.29.87.105: icmp_req=2 ttl=57 time=152 ms
64 bytes from 72.29.87.105: icmp_req=3 ttl=57 time=152 ms
64 bytes from 72.29.87.105: icmp_req=4 ttl=57 time=152 ms
64 bytes from 72.29.87.105: icmp_req=5 ttl=57 time=151 ms
^C
--- 72.29.87.105 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4006ms
rtt min/avg/max/mdev = 151.736/152.440/152.911/0.474 ms
    Thanked by 1serverian
  • DomainBopDomainBop Member

    Italy

    PING 72.29.87.105 (72.29.87.105) 56(84) bytes of data.
64 bytes from 72.29.87.105: icmp_req=1 ttl=49 time=118 ms
64 bytes from 72.29.87.105: icmp_req=2 ttl=49 time=118 ms
64 bytes from 72.29.87.105: icmp_req=3 ttl=49 time=118 ms
64 bytes from 72.29.87.105: icmp_req=4 ttl=49 time=118 ms
64 bytes from 72.29.87.105: icmp_req=5 ttl=49 time=118 ms
64 bytes from 72.29.87.105: icmp_req=6 ttl=49 time=118 ms
^C
--- 72.29.87.105 ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5005ms
rtt min/avg/max/mdev = 118.384/118.445/118.555/0.402 ms

    Iceland

    PING 72.29.87.105 (72.29.87.105) 56(84) bytes of data.
64 bytes from 72.29.87.105: icmp_req=1 ttl=57 time=143 ms
64 bytes from 72.29.87.105: icmp_req=2 ttl=57 time=143 ms
64 bytes from 72.29.87.105: icmp_req=3 ttl=57 time=143 ms
64 bytes from 72.29.87.105: icmp_req=4 ttl=57 time=143 ms
64 bytes from 72.29.87.105: icmp_req=5 ttl=57 time=143 ms
64 bytes from 72.29.87.105: icmp_req=6 ttl=57 time=143 ms
64 bytes from 72.29.87.105: icmp_req=7 ttl=57 time=143 ms
^C
--- 72.29.87.105 ping statistics ---
7 packets transmitted, 7 received, 0% packet loss, time 6009ms
rtt min/avg/max/mdev = 143.122/143.271/143.512/0.144 ms

    Russia

    PING 72.29.87.105 (72.29.87.105) 56(84) bytes of data.
64 bytes from 72.29.87.105: icmp_req=1 ttl=51 time=178 ms
64 bytes from 72.29.87.105: icmp_req=2 ttl=51 time=178 ms
64 bytes from 72.29.87.105: icmp_req=3 ttl=51 time=171 ms
64 bytes from 72.29.87.105: icmp_req=4 ttl=51 time=178 ms
64 bytes from 72.29.87.105: icmp_req=5 ttl=51 time=171 ms
^C
--- 72.29.87.105 ping statistics ---
6 packets transmitted, 5 received, 16% packet loss, time 5006ms
rtt min/avg/max/mdev = 171.865/175.813/178.486/3.222 ms

    Spain

    PING 72.29.87.105 (72.29.87.105) 56(84) bytes of data.
64 bytes from 72.29.87.105: icmp_req=1 ttl=49 time=122 ms
64 bytes from 72.29.87.105: icmp_req=2 ttl=49 time=123 ms
64 bytes from 72.29.87.105: icmp_req=3 ttl=49 time=122 ms
64 bytes from 72.29.87.105: icmp_req=4 ttl=49 time=123 ms
64 bytes from 72.29.87.105: icmp_req=5 ttl=49 time=122 ms
64 bytes from 72.29.87.105: icmp_req=6 ttl=49 time=122 ms
^C
--- 72.29.87.105 ping statistics ---
7 packets transmitted, 6 received, 14% packet loss, time 6008ms
rtt min/avg/max/mdev = 122.548/123.000/123.722/0.549 ms

    France

    PING 72.29.87.105 (72.29.87.105) 56(84) bytes of data.
64 bytes from 72.29.87.105: icmp_req=1 ttl=51 time=98.0 ms
64 bytes from 72.29.87.105: icmp_req=2 ttl=51 time=97.8 ms
64 bytes from 72.29.87.105: icmp_req=3 ttl=51 time=97.8 ms
64 bytes from 72.29.87.105: icmp_req=4 ttl=51 time=97.9 ms
64 bytes from 72.29.87.105: icmp_req=5 ttl=51 time=97.8 ms
64 bytes from 72.29.87.105: icmp_req=6 ttl=51 time=97.9 ms
^C
--- 72.29.87.105 ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 4999ms
rtt min/avg/max/mdev = 97.816/97.930/98.096/0.270 ms

    Netherlands

    PING 72.29.87.105 (72.29.87.105) 56(84) bytes of data.
64 bytes from 72.29.87.105: icmp_req=1 ttl=51 time=103 ms
64 bytes from 72.29.87.105: icmp_req=2 ttl=51 time=103 ms
64 bytes from 72.29.87.105: icmp_req=3 ttl=51 time=103 ms
64 bytes from 72.29.87.105: icmp_req=4 ttl=51 time=103 ms
64 bytes from 72.29.87.105: icmp_req=5 ttl=51 time=103 ms
64 bytes from 72.29.87.105: icmp_req=6 ttl=51 time=103 ms
64 bytes from 72.29.87.105: icmp_req=7 ttl=51 time=103 ms
^C
--- 72.29.87.105 ping statistics ---
7 packets transmitted, 7 received, 0% packet loss, time 6000ms
rtt min/avg/max/mdev = 103.143/103.224/103.418/0.353 ms

    UK

    PING 72.29.87.105 (72.29.87.105) 56(84) bytes of data.
64 bytes from 72.29.87.105: icmp_req=1 ttl=55 time=95.6 ms
64 bytes from 72.29.87.105: icmp_req=2 ttl=55 time=95.5 ms
64 bytes from 72.29.87.105: icmp_req=3 ttl=55 time=95.4 ms
64 bytes from 72.29.87.105: icmp_req=4 ttl=55 time=95.4 ms
64 bytes from 72.29.87.105: icmp_req=5 ttl=55 time=95.4 ms
64 bytes from 72.29.87.105: icmp_req=6 ttl=55 time=95.4 ms
^C
--- 72.29.87.105 ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5005ms
rtt min/avg/max/mdev = 95.453/95.502/95.639/0.315 ms

    ...and for good measure, Africa...South Africa

    PING 72.29.87.105 (72.29.87.105) 56(84) bytes of data.
64 bytes from 72.29.87.105: icmp_req=1 ttl=47 time=268 ms
64 bytes from 72.29.87.105: icmp_req=2 ttl=47 time=268 ms
64 bytes from 72.29.87.105: icmp_req=3 ttl=47 time=268 ms
64 bytes from 72.29.87.105: icmp_req=4 ttl=47 time=268 ms
64 bytes from 72.29.87.105: icmp_req=5 ttl=47 time=268 ms
64 bytes from 72.29.87.105: icmp_req=6 ttl=47 time=268 ms
64 bytes from 72.29.87.105: icmp_req=7 ttl=47 time=268 ms
64 bytes from 72.29.87.105: icmp_req=8 ttl=47 time=268 ms
64 bytes from 72.29.87.105: icmp_req=9 ttl=47 time=268 ms
64 bytes from 72.29.87.105: icmp_req=10 ttl=47 time=268 ms
^C
--- 72.29.87.105 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9010ms
rtt min/avg/max/mdev = 268.633/268.723/268.858/0.616 ms
  • twaintwain Member

    It's a HostDime IP they are in Miami too, or IP is in Orlando going thru Miami?

  • DomainBopDomainBop Member

    @twain said:
    It's a HostDime IP they are in Miami too, or IP is in Orlando going thru Miami?

    traceroute from my VPS at VelociHost/Colohouse in Miami

     1  38.89.160.1 (38.89.160.1)  0.772 ms  1.852 ms  2.012 ms
 2  gi3-2.ccr01.mia09.atlas.cogentco.com (38.88.36.13)  4.631 ms  4.770 ms  4.994 ms
 3  te0-6-0-5.ccr22.mia01.atlas.cogentco.com (154.54.85.205)  2.364 ms  2.450 ms  2.522 ms
 4  be2054.ccr21.mia03.atlas.cogentco.com (154.54.80.42)  2.818 ms be2055.ccr21.mia03.atlas.cogentco.com (154.54.24.234)  2.684 ms  2.553 ms
 5  ge-7-6.car2.Atlanta1.Level3.net (4.68.110.169)  1.991 ms  1.866 ms  2.079 ms
 6  ae-32-52.ebr2.Miami1.Level3.net (4.69.138.123)  5.302 ms  5.048 ms  4.974 ms
 7  ae-3-5.bar2.Orlando1.Level3.net (4.69.148.210)  5.693 ms  5.788 ms  6.119 ms
 8  ae-0-11.bar1.Orlando1.Level3.net (4.69.137.145)  5.423 ms  5.949 ms  5.811 ms
 9  72-29-87-105.static.dimenoc.com (72.29.87.105)  6.043 ms  6.242 ms  6.098 ms
  • markmark Member

    UK (OpenITC):

    Pinging 72.29.87.105 with 32 bytes of data:
Reply from 72.29.87.105: bytes=32 time=106ms TTL=56
Reply from 72.29.87.105: bytes=32 time=107ms TTL=56
Reply from 72.29.87.105: bytes=32 time=106ms TTL=56
Reply from 72.29.87.105: bytes=32 time=106ms TTL=56

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

    UK (DotVPS):

    PING 72.29.87.105 (72.29.87.105) 56(84) bytes of data. 64 bytes from 72.29.87.105: icmp_req=1 ttl=55 time=106 ms 64 bytes from 72.29.87.105: icmp_req=2 ttl=55 time=104 ms 64 bytes from 72.29.87.105: icmp_req=3 ttl=55 time=104 ms 64 bytes from 72.29.87.105: icmp_req=4 ttl=55 time=104 ms ^C --- 72.29.87.105 ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3000ms rtt min/avg/max/mdev = 104.162/104.831/106.050/0.779 ms

    UK (EDIS):

    PING 72.29.87.105 (72.29.87.105) 56(84) bytes of data. 64 bytes from 72.29.87.105: icmp_req=1 ttl=49 time=95.5 ms 64 bytes from 72.29.87.105: icmp_req=2 ttl=49 time=94.5 ms 64 bytes from 72.29.87.105: icmp_req=3 ttl=49 time=94.1 ms 64 bytes from 72.29.87.105: icmp_req=4 ttl=49 time=94.6 ms ^C --- 72.29.87.105 ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3004ms rtt min/avg/max/mdev = 94.146/94.728/95.561/0.561 ms

    UK (URPad):

    PING 72.29.87.105 (72.29.87.105) 56(84) bytes of data. 64 bytes from 72.29.87.105: icmp_seq=1 ttl=51 time=124 ms 64 bytes from 72.29.87.105: icmp_seq=2 ttl=51 time=122 ms 64 bytes from 72.29.87.105: icmp_seq=3 ttl=51 time=127 ms 64 bytes from 72.29.87.105: icmp_seq=4 ttl=51 time=124 ms ^C --- 72.29.87.105 ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3478ms rtt min/avg/max/mdev = 122.709/125.030/127.616/1.758 ms

    Netherlands (HostSlim):

    PING 72.29.87.105 (72.29.87.105) 56(84) bytes of data. 64 bytes from 72.29.87.105: icmp_req=1 ttl=49 time=143 ms 64 bytes from 72.29.87.105: icmp_req=2 ttl=49 time=142 ms 64 bytes from 72.29.87.105: icmp_req=3 ttl=49 time=143 ms 64 bytes from 72.29.87.105: icmp_req=4 ttl=49 time=142 ms ^C --- 72.29.87.105 ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3003ms rtt min/avg/max/mdev = 142.731/143.173/143.728/0.456 ms

    UK (Virgin Media - my home broadband provider):

    Pinging 72.29.87.105 with 32 bytes of data:

Reply from 72.29.87.105: bytes=32 time=126ms TTL=50
Reply from 72.29.87.105: bytes=32 time=123ms TTL=50
Reply from 72.29.87.105: bytes=32 time=123ms TTL=50
Reply from 72.29.87.105: bytes=32 time=123ms TTL=50

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

    Hope that's enough for you - sorry for the UK bias!

  • lycidelycide Member

    FR (OVH Gravelines)

    root@dedi:~# ping 72.29.87.105
PING 72.29.87.105 (72.29.87.105) 56(84) bytes of data.
64 bytes from 72.29.87.105: icmp_req=1 ttl=50 time=97.4 ms
64 bytes from 72.29.87.105: icmp_req=2 ttl=50 time=97.4 ms
64 bytes from 72.29.87.105: icmp_req=3 ttl=50 time=97.3 ms
64 bytes from 72.29.87.105: icmp_req=4 ttl=50 time=97.4 ms
64 bytes from 72.29.87.105: icmp_req=5 ttl=50 time=97.4 ms
64 bytes from 72.29.87.105: icmp_req=6 ttl=50 time=97.4 ms
^C
--- 72.29.87.105 ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5007ms
rtt min/avg/max/mdev = 97.369/97.449/97.491/0.405 ms

    UK (LowEndSpirit Newcastle)

    root@status:/# ping 72.29.87.105
PING 72.29.87.105 (72.29.87.105) 56(84) bytes of data.
64 bytes from 72.29.87.105: icmp_req=1 ttl=51 time=103 ms
64 bytes from 72.29.87.105: icmp_req=2 ttl=51 time=104 ms
64 bytes from 72.29.87.105: icmp_req=3 ttl=51 time=103 ms
64 bytes from 72.29.87.105: icmp_req=4 ttl=51 time=103 ms
64 bytes from 72.29.87.105: icmp_req=5 ttl=51 time=103 ms
64 bytes from 72.29.87.105: icmp_req=6 ttl=51 time=103 ms
64 bytes from 72.29.87.105: icmp_req=7 ttl=51 time=103 ms
^C
--- 72.29.87.105 ping statistics ---
7 packets transmitted, 7 received, 0% packet loss, time 6008ms
rtt min/avg/max/mdev = 103.658/103.829/104.097/0.223 ms

    UK (Virgin Media - home connection)

    C:\Users\Chris>ping 72.29.87.105

Pinging 72.29.87.105 with 32 bytes of data:
Reply from 72.29.87.105: bytes=32 time=123ms TTL=50
Reply from 72.29.87.105: bytes=32 time=123ms TTL=50
Reply from 72.29.87.105: bytes=32 time=126ms TTL=50
Reply from 72.29.87.105: bytes=32 time=123ms TTL=50

Ping statistics for 72.29.87.105:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 123ms, Maximum = 126ms, Average = 123ms
  • draziloxdrazilox Member

    Helsinki, Finland

    Pinging 72.29.87.105 with 32 bytes of data:
Reply from 72.29.87.105: bytes=32 time=164ms TTL=55
Reply from 72.29.87.105: bytes=32 time=162ms TTL=55
Reply from 72.29.87.105: bytes=32 time=162ms TTL=55
Reply from 72.29.87.105: bytes=32 time=164ms TTL=55

Ping statistics for 72.29.87.105:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 162ms, Maximum = 164ms, Average = 163ms
  • MaouniqueMaounique Host Rep, Veteran

    116 ms flat from .it

  • super320super320 Member

    @serverian said:
    72.29.87.105

    You can check this in URL: http://www.super-ping.com/?ping=72.29.87.105

  • StableVDSStableVDS Member
    edited August 2013

    NL Swiftway

    PING 72.29.87.105 (72.29.87.105) 56(84) bytes of data.
    64 bytes from 72.29.87.105: icmp_seq=1 ttl=57 time=111 ms
    64 bytes from 72.29.87.105: icmp_seq=2 ttl=57 time=111 ms
    64 bytes from 72.29.87.105: icmp_seq=3 ttl=57 time=111 ms
    64 bytes from 72.29.87.105: icmp_seq=4 ttl=57 time=111 ms
    64 bytes from 72.29.87.105: icmp_seq=5 ttl=57 time=111 ms

    --- 72.29.87.105 ping statistics ---
    5 packets transmitted, 5 received, 0% packet loss, time 4116ms
    rtt min/avg/max/mdev = 111.065/111.351/111.620/0.196 ms

    NL Netrouting
    PING 72.29.87.105 (72.29.87.105) 56(84) bytes of data.
    64 bytes from 72.29.87.105: icmp_seq=1 ttl=49 time=120 ms
    64 bytes from 72.29.87.105: icmp_seq=2 ttl=49 time=120 ms
    64 bytes from 72.29.87.105: icmp_seq=3 ttl=49 time=120 ms
    64 bytes from 72.29.87.105: icmp_seq=4 ttl=49 time=120 ms
    64 bytes from 72.29.87.105: icmp_seq=5 ttl=49 time=120 ms

    --- 72.29.87.105 ping statistics ---
    5 packets transmitted, 5 received, 0% packet loss, time 4123ms
    rtt min/avg/max/mdev = 120.012/120.064/120.113/0.221 ms

  • wychwych Member
    edited August 2013

    Microsoft Windows [Version 6.x.7601m]
    Copyright (c) 2009 Microsoft Corporation. All rights reserved.

    C:\Users\AAAAA>ping 72.29.87.105

    Pinging 72.29.87.105 with 32 bytes of data:
    Reply from 72.29.87.105: bytes=32 time=120ms TTL=49
    ..
    Reply from 72.29.87.105: bytes=32 time=119ms TTL=49
    ..
    Reply from 72.29.87.105: bytes=32 time=119ms TTL=49
    ..
    Reply from 72.29.87.105: bytes=32 time=119ms TTL=49
    ..

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

    From TalkTalk - Manchester, UK...

  • callecalle Member
    edited August 2013

    Sweden

    ping 72.29.87.105

    Pinging 72.29.87.105 with 32 bytes of data:

    Reply from 72.29.87.105: bytes=32 time=148ms TTL=47

    Reply from 72.29.87.105: bytes=32 time=148ms TTL=47

    Reply from 72.29.87.105: bytes=32 time=148ms TTL=47

    Reply from 72.29.87.105: bytes=32 time=148ms TTL=47

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

  • trexostrexos Member 
    Antwort von 72.29.87.105: Bytes=32 Zeit=178ms TTL=49
Antwort von 72.29.87.105: Bytes=32 Zeit=176ms TTL=50
Antwort von 72.29.87.105: Bytes=32 Zeit=178ms TTL=50
Antwort von 72.29.87.105: Bytes=32 Zeit=178ms TTL=49

    From Germany.

  • zfedorazfedora Member

    France:

    # ping 72.29.87.105
PING 72.29.87.105 (72.29.87.105) 56(84) bytes of data.
64 bytes from 72.29.87.105: icmp_req=1 ttl=51 time=131 ms
64 bytes from 72.29.87.105: icmp_req=2 ttl=51 time=133 ms
64 bytes from 72.29.87.105: icmp_req=3 ttl=51 time=138 ms
64 bytes from 72.29.87.105: icmp_req=4 ttl=51 time=130 ms
64 bytes from 72.29.87.105: icmp_req=5 ttl=51 time=132 ms
64 bytes from 72.29.87.105: icmp_req=6 ttl=51 time=140 ms
64 bytes from 72.29.87.105: icmp_req=7 ttl=51 time=144 ms
64 bytes from 72.29.87.105: icmp_req=8 ttl=51 time=131 ms
64 bytes from 72.29.87.105: icmp_req=9 ttl=51 time=129 ms
64 bytes from 72.29.87.105: icmp_req=10 ttl=51 time=139 ms
^C
--- 72.29.87.105 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9011ms
rtt min/avg/max/mdev = 129.638/135.153/144.266/4.959 ms
  • serverianserverian Member

    Okay thanks guys, I'm convinced that this won't work for Europe.

  • mpkossenmpkossen Member

    Considering HostDime?

  • serverianserverian Member

    @mpkossen said:
    Considering HostDime?

    For backupsy, I'm having a node setup there today. But this tests were for another project.

    Thanked by 1mpkossen
  • DomainBopDomainBop Member

    @serverian said:
    For backupsy, I'm having a node setup there today. But this tests were for another project.

    Is the HostDime datacenter in Orlando or did they open one in Miami? The traceroute and the 6ms ping times from Colohouse Miami to the IP address looked like Orlando.

Sign In or Register to comment.