Howdy, Stranger!

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


Does it pingable from your location
New on LowEndTalk? Please Register and read our Community Rules.

Does it pingable from your location

vpsGODvpsGOD Member, Provider
edited September 2014 in General

Hi LET
I am running an issue with provider and twisting my hair after reading the support ticket reply..

Does IP needs times to propagate all around world??? If yes how long !?

IP : 104.128.226.19 / 22
Could you post the ping result of yours with location

C:\Users\Dead End>ping 104.128.226.22
Pinging 104.128.226.22 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 104.128.226.22:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

Online test shows its up in US only
http://cloudmonitor.ca.com/en/ping.php?vtt=1410270520&varghost=104.128.226.22&vhost=_&vaction=ping&ping=Start

Comments

  • works for me

    Thanked by 1vpsGOD
  • vpsGODvpsGOD Member, Provider

    hostnoob - Location US or other

  • A single IP won't need to propagate, it works immediately. That's just for DNS only. It's pinging from me with 133ms.

    Thanked by 1vpsGOD
  • rds100rds100 Member
    edited September 2014
  • I can reach it just fine, from inside and outside the US.

    Wait, are you using HostUS?

    @AlexanderM

  • vpsGODvpsGOD Member, Provider

    @rds100 - i have updated just-ping result
    http://cloudmonitor.ca.com/en/ping.php?vtt=1410271492&varghost=104.128.226.19&vhost=_&vaction=ping&ping=Start

    Result says its up only in few USA location

  • pingable

    PING 104.128.226.19 (104.128.226.19) 56(84) bytes of data.
    64 bytes from 104.128.226.19: icmp_seq=1 ttl=51 time=394 ms
    64 bytes from 104.128.226.19: icmp_seq=2 ttl=51 time=417 ms
    64 bytes from 104.128.226.19: icmp_seq=3 ttl=51 time=441 ms
    64 bytes from 104.128.226.19: icmp_seq=4 ttl=51 time=260 ms
    64 bytes from 104.128.226.19: icmp_seq=5 ttl=51 time=260 ms
    64 bytes from 104.128.226.19: icmp_seq=6 ttl=51 time=260 ms
    64 bytes from 104.128.226.19: icmp_seq=7 ttl=51 time=262 ms
    
    Thanked by 1vpsGOD
  • definedcodedefinedcode Member
    edited September 2014

    Pingable from our servers in the Netherlands:

    [email protected]:~$ ping 104.128.226.22 -c5
    PING 104.128.226.22 (104.128.226.22) 56(84) bytes of data.
    64 bytes from 104.128.226.22: icmp_seq=1 ttl=54 time=103 ms
    64 bytes from 104.128.226.22: icmp_seq=2 ttl=54 time=103 ms
    64 bytes from 104.128.226.22: icmp_seq=3 ttl=54 time=103 ms
    64 bytes from 104.128.226.22: icmp_seq=4 ttl=54 time=103 ms
    64 bytes from 104.128.226.22: icmp_seq=5 ttl=54 time=103 ms

    --- 104.128.226.22 ping statistics ---
    5 packets transmitted, 5 received, 0% packet loss, time 4005ms
    rtt min/avg/max/mdev = 103.370/103.479/103.649/0.110 ms

    Thanked by 1vpsGOD
  • @suraj4u said:
    hostnoob - Location US or other

    UK, NL, SE, US and FR

    Thanked by 1vpsGOD
  • vpsGODvpsGOD Member, Provider

    @eddynetweb - yes ..hostus

    @berndy2001 - looking glass http://lg.he.net
    I get timedout on europe.. looks ok in US

    @tommy- thanks
    @definedcode - thanks
    @hostnoob - but i cant get even in France(FReeSAS) .. But NL(leaseweb) its working

  • @suraj4u said:
    hostnoob - but i cant get even in France(FReeSAS) .. But NL(leaseweb) its working

    This is france:

    [[email protected] ~]# ping 104.128.226.22 -c5
    PING 104.128.226.22 (104.128.226.22) 56(84) bytes of data.
    64 bytes from 104.128.226.22: icmp_seq=1 ttl=49 time=108 ms
    64 bytes from 104.128.226.22: icmp_seq=2 ttl=49 time=108 ms
    64 bytes from 104.128.226.22: icmp_seq=3 ttl=49 time=108 ms
    64 bytes from 104.128.226.22: icmp_seq=4 ttl=49 time=108 ms
    64 bytes from 104.128.226.22: icmp_seq=5 ttl=49 time=108 ms

    --- 104.128.226.22 ping statistics ---
    5 packets transmitted, 5 received, 0% packet loss, time 4114ms
    rtt min/avg/max/mdev = 108.499/108.565/108.625/0.419 ms

    Thanked by 1vpsGOD
  • wychwych Member
    edited September 2014

    If you have made a DNS entry it can take time to propagate, you can check it here ( https://www.whatsmydns.net/ ), however IP's do not need to propagate.

    As you said a /22 maybe the routing is still being setup within the DC?

    Thanked by 1vpsGOD
  • vpsGODvpsGOD Member, Provider

    My france ping.. packet loss

    C:\Users\Administrator>ipconfig

    Windows IP Configuration

    Ethernet adapter Local Area Connection:

    Connection-specific DNS Suffix . :
    Link-local IPv6 Address . . . . . : fe80::4552:baa5:cef4:86e7%18
    IPv4 Address. . . . . . . . . . . : 169.254.123.35
    Subnet Mask . . . . . . . . . . . : 255.255.0.0
    Default Gateway . . . . . . . . . :

    Ethernet adapter Ethernet 2:

    Connection-specific DNS Suffix . : online.net
    Link-local IPv6 Address . . . . . : fe80::1ce9:7218:774:13a1%13
    IPv4 Address. . . . . . . . . . . : 62.210.204.34
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Default Gateway . . . . . . . . . : fe80::be16:65ff:fe50:4967%13
    62.210.204.1

    Ethernet adapter Ethernet:

    Connection-specific DNS Suffix . :
    IPv4 Address. . . . . . . . . . . : 10.90.80.132
    Subnet Mask . . . . . . . . . . . : 255.255.255.192
    Default Gateway . . . . . . . . . :

    C:\Users\Administrator>ping 104.128.226.22

    Pinging 104.128.226.22 with 32 bytes of data:
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.

    Ping statistics for 104.128.226.22:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

    C:\Users\Administrator>

  • @suraj4u said:
    eddynetweb - yes ..hostus

    berndy2001 - looking glass http://lg.he.net
    I get timedout on europe.. looks ok in US

    tommy- thanks
    definedcode - thanks
    hostnoob - but i cant get even in France(FReeSAS) .. But NL(leaseweb) its working

    Sorry I have no idea. Works for me from anywhere, and that cloudmonitor site works for my sites so I dunno. Weird.

  • It appears to only be routing in some locations.

    https://www.site24x7.com/public/t/results-1410273222718.html

    Thanked by 1vpsGOD
  • Pinging 104.128.226.19 with 32 bytes of data:
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.

    From Vietnam :v

    Thanked by 1vpsGOD
  • vpsGODvpsGOD Member, Provider
    edited September 2014

    eddynetweb said: It appears to only be routing in some locations.
    https://www.site24x7.com/public/t/results-1410273222718.html

    Thats the issue.. Lets me wait what my provider going to say

    @ windytime90 - Thanks for vietnam update ..

  • Pingable Jakarta, Indonesia

    C:\Users\Noerman>ping 104.128.226.22
    
    Pinging 104.128.226.22 with 32 bytes of data:
    Reply from 104.128.226.22: bytes=32 time=275ms TTL=49
    Reply from 104.128.226.22: bytes=32 time=274ms TTL=49
    Reply from 104.128.226.22: bytes=32 time=274ms TTL=49
    Reply from 104.128.226.22: bytes=32 time=274ms TTL=49
    
    Ping statistics for 104.128.226.22:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 274ms, Maximum = 275ms, Average = 274ms
    
    Thanked by 1vpsGOD
  • Its because its probably a new range and Quickpacket has not requested Cogent or whoever their upstream is to add the prefix to their filter list.

    Thanked by 1vpsGOD
  • vpsGODvpsGOD Member, Provider
  • Piscataway, New Jersey:

    [[email protected]]# ping 104.128.226.19

    PING 104.128.226.19 (104.128.226.19) 56(84) bytes of data.

    64 bytes from 104.128.226.19: icmp_seq=1 ttl=52 time=30.5 ms

    64 bytes from 104.128.226.19: icmp_seq=2 ttl=52 time=30.6 ms

    64 bytes from 104.128.226.19: icmp_seq=3 ttl=52 time=30.6 ms

    64 bytes from 104.128.226.19: icmp_seq=4 ttl=52 time=30.7 ms

    64 bytes from 104.128.226.19: icmp_seq=5 ttl=52 time=30.6 ms

    64 bytes from 104.128.226.19: icmp_seq=6 ttl=52 time=30.6 ms



    --- 104.128.226.19 ping statistics ---

    6 packets transmitted, 6 received, 0% packet loss, time 5736ms

    rtt min/avg/max/mdev = 30.573/30.641/30.737/0.052 ms




    Los Angeles (Home internet):

    C:\Users\John>ping 104.128.226.19



    Pinging 104.128.226.19 with 32 bytes of data:

    Reply from 104.128.226.19: bytes=32 time=90ms TTL=47

    Reply from 104.128.226.19: bytes=32 time=90ms TTL=47

    Reply from 104.128.226.19: bytes=32 time=91ms TTL=47

    Reply from 104.128.226.19: bytes=32 time=90ms TTL=47



    Ping statistics for 104.128.226.19:

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

    Approximate round trip times in milli-seconds:

    Minimum = 90ms, Maximum = 91ms, Average = 90ms

    Thanked by 1vpsGOD
  • vpsGODvpsGOD Member, Provider

    @MarkTurner - It may be.. thanks

    @GreenHostBox - Thanks Looks good inside USA

    looking some one in india, pakistan,srilanka to provide result

  • AlexanderMAlexanderM Top Provider

    Could you PM me your ticket please @suraj4u

    Thanks

    Thanked by 1vpsGOD
  • AlexanderMAlexanderM Top Provider
    edited September 2014

    Found your ticket, it's not a vps hence why I haven't had dealings with your ticket. I've taken over and will let you know vie ticket.

    @markturner FYI we utilise other providers than qps and we only have one of our cPanel nodes with them, and the issue is nothing to do with them. It's not difficult to check that out, being a network admin your self.

    Alexander

  • vpsGODvpsGOD Member, Provider

    Looking forward

  • qpsqps Member, Provider
    edited September 2014

    MarkTurner said: Its because its probably a new range and Quickpacket has not requested Cogent or whoever their upstream is to add the prefix to their filter list.

    This is incorrect. Prefix is accessible from all of our upstream networks.

  • vpsGODvpsGOD Member, Provider

    Is thier any wrong in traceroute why its end on timedout

    Traceroute from MTS India
    Tracing route to 104.128.226.19 over a maximum of 30 hops

    1 160 ms 82 ms 102 ms 10.228.129.13
    2 135 ms 83 ms 212 ms 10.228.149.14
    3 127 ms 100 ms 100 ms 116.202.226.145
    4 93 ms 102 ms 72 ms 116.202.226.17
    5 85 ms 79 ms 85 ms aes-static-173.194.22.125.airtel.in [125.22.194.173]
    6 253 ms 227 ms 236 ms 182.79.248.234
    7 1694 ms 403 ms 547 ms linx.10ge.lon.bboi.net [195.66.224.233]
    8 335 ms 346 ms 349 ms ny60-vl14-lon-vl14.bboi.net [66.216.48.213]
    9 2474 ms 1581 ms 365 ms nj-ten2-1-ny60-ten1-4.bboi.net [66.216.1.106]
    10 355 ms 424 ms 325 ms ash-ten1-5-nj-ten2-2.bboi.net [66.216.1.161]
    11 357 ms 358 ms 366 ms atl-ten3-1-ash-ten3-1.bboi.net [66.216.1.157]
    12 362 ms 343 ms 326 ms 66.216.0.162
    13 330 ms 322 ms 328 ms core1-10gige.atl.hostus.us [199.101.98.90]
    14 334 ms 348 ms 336 ms 104.128.226.2
    15 * * * Request timed out.
    16 * * * Request timed out.
    17 *

    Traceroute from vodafone India
    Tracing route to 104.128.226.19 over a maximum of 30 hops

    1 2 ms 1 ms 1 ms 192.168.43.1
    2 54 ms 57 ms 57 ms 10.174.30.73
    3 78 ms 63 ms 57 ms 10.166.30.34
    4 * * * Request timed out.
    5 2166 ms 448 ms 1057 ms 10.166.30.20
    6 * * * Request timed out.
    7 * *

    Traceroute from NIC
    Tracing route to 104.128.226.19 over a maximum of 30 hops

    1 1 ms 1 ms 1 ms 172.18.0.1
    2 1 ms 1 ms 1 ms [[[masked]]].edu [172.16.0.1]
    3 82 ms 40 ms 32 ms 172.24.66.181
    4 171 ms 30 ms 28 ms 172.24.66.182
    5 * 26 ms * 218.248.235.162
    6 12 ms 14 ms 13 ms 59.163.201.149.static.chennai.vsnl.net.in [59.163.201.149]
    7 13 ms 13 ms 13 ms ix-4-2.tcore2.CXR-Chennai.as6453.net [180.87.37.1]
    8 267 ms 266 ms 266 ms if-6-2.tcore2.SVW-Singapore.as6453.net [180.87.37.14]
    9 263 ms * 271 ms if-2-2.tcore1.SVW-Singapore.as6453.net [180.87.12.1]
    10 270 ms 270 ms * if-6-2.tcore2.TV2-Tokyo.as6453.net [180.87.12.110]
    11 * 269 ms 266 ms if-2-2.tcore1.TV2-Tokyo.as6453.net [180.87.180.1]
    12 * 271 ms * if-9-2.tcore2.PDI-Palo-Alto.as6453.net [180.87.180.17]
    13 269 ms 268 ms 268 ms if-5-2.tcore2.SQN-San-Jose.as6453.net [64.86.21.1]
    14 265 ms 265 ms 266 ms if-1-2.tcore1.SQN-San-Jose.as6453.net [63.243.205.1]
    15 268 ms 268 ms 265 ms be6453.ccr21.sjc03.atlas.cogentco.com [154.54.12.141]
    16 265 ms 266 ms 266 ms be2000.ccr21.sjc01.atlas.cogentco.com [154.54.6.105]
    17 267 ms 268 ms 268 ms be2162.mpd21.lax01.atlas.cogentco.com [154.54.27.173]
    18 274 ms 274 ms 276 ms be2067.ccr21.iah01.atlas.cogentco.com [154.54.7.161]
    19 * 277 ms 277 ms be2172.ccr41.atl01.atlas.cogentco.com [154.54.29.17]
    20 289 ms 274 ms 274 ms 38.88.10.254
    21 281 ms 282 ms * core1-10gige.atl.hostus.us [199.101.98.90]
    22 278 ms 278 ms 279 ms 104.128.226.2
    23 * * * Request timed out.
    24 * *

  • vpsGODvpsGOD Member, Provider

    fixed.. Thanks for all your LET
    Lets @AlexanderM explain about the fix

  • $ ping 104.128.226.19
    PING 104.128.226.19 (104.128.226.19): 56 data bytes
    64 bytes from 104.128.226.19: icmp_seq=0 ttl=53 time=86.443 ms
    64 bytes from 104.128.226.19: icmp_seq=1 ttl=53 time=85.631 ms
    64 bytes from 104.128.226.19: icmp_seq=2 ttl=53 time=86.442 ms
    64 bytes from 104.128.226.19: icmp_seq=3 ttl=53 time=85.625 ms
    64 bytes from 104.128.226.19: icmp_seq=4 ttl=53 time=86.298 ms
    64 bytes from 104.128.226.19: icmp_seq=5 ttl=53 time=85.309 ms
    64 bytes from 104.128.226.19: icmp_seq=6 ttl=53 time=86.125 ms
    64 bytes from 104.128.226.19: icmp_seq=7 ttl=53 time=84.976 ms
    ^C
    --- 104.128.226.19 ping statistics ---
    8 packets transmitted, 8 packets received, 0.0% packet loss
    round-trip min/avg/max/stddev = 84.976/85.856/86.443/0.516 ms
    
Sign In or Register to comment.