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.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Does it pingable from your location
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
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.
http://www.just-ping.com
I can reach it just fine, from inside and outside the US.
Wait, are you using HostUS?
@AlexanderM
@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
or use looking glass: https://www.google.com/search?q=looking+glass+ping&ie=utf-8
pingable
Pingable from our servers in the Netherlands:
UK, NL, SE, US and FR
@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
This is france:
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?
My france ping.. packet loss
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
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
Thats the issue.. Lets me wait what my provider going to say
@ windytime90 - Thanks for vietnam update ..
Pingable Jakarta, Indonesia
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.
@Noerman - Thanks for update
Result screens of above links- Let check later
http://s29.postimg.org/od1v4h22v/1410275596723.png
http://s29.postimg.org/wu1dfe6rr/1410275632172.png
Piscataway, New Jersey:
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):
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
@MarkTurner - It may be.. thanks
@GreenHostBox - Thanks Looks good inside USA
looking some one in india, pakistan,srilanka to provide result
Could you PM me your ticket please @suraj4u
Thanks
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
Looking forward
This is incorrect. Prefix is accessible from all of our upstream networks.
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
Traceroute from vodafone India
Tracing route to 104.128.226.19 over a maximum of 30 hops
Traceroute from NIC
Tracing route to 104.128.226.19 over a maximum of 30 hops
fixed.. Thanks for all your LET
Lets @AlexanderM explain about the fix