Nocster ping ...

Portal Home > Knowledgebase > Articles Database > Nocster ping ...

Posted by rushik, 09-20-2004, 07:16 AM
Hi, I am from india, and not able to get the ping to nocster datacenters server. my ip is 66.197.186.40 .. there is some problem at the carrier at their side. please ping up someone and let me know. i checked that is working fine from usa based clients. regards
Posted by bigown, 09-20-2004, 07:17 AM
From Brazil too
Posted by robgct, 09-20-2004, 07:17 AM
Pinging 66.197.186.40 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Reply from 66.197.186.40: bytes=32 time=377ms TTL=49 Ping statistics for 66.197.186.40: Packets: Sent = 4, Received = 1, Lost = 3 (75% loss), Approximate round trip times in milli-seconds: Minimum = 377ms, Maximum = 377ms, Average = 377ms from Connecticut, east
Posted by dgram, 09-20-2004, 08:06 AM
Got 0% packetloss from Norway, Tx and Nj, must of been temporarily..
Posted by sirius, 09-20-2004, 09:48 AM
No problems here.... root@slinky [~]# ping www.nocster.com PING nocster.com (66.96.192.220) 56(84) bytes of data. 64 bytes from 6696192220.hostnoc.net (66.96.192.220): icmp_seq=0 ttl=54 time=42.4 ms 64 bytes from 6696192220.hostnoc.net (66.96.192.220): icmp_seq=1 ttl=54 time=42.4 ms 64 bytes from 6696192220.hostnoc.net (66.96.192.220): icmp_seq=2 ttl=54 time=42.3 ms 64 bytes from 6696192220.hostnoc.net (66.96.192.220): icmp_seq=3 ttl=54 time=42.3 ms 64 bytes from 6696192220.hostnoc.net (66.96.192.220): icmp_seq=4 ttl=54 time=42.1 ms 64 bytes from 6696192220.hostnoc.net (66.96.192.220): icmp_seq=5 ttl=54 time=42.1 ms 64 bytes from 6696192220.hostnoc.net (66.96.192.220): icmp_seq=6 ttl=54 time=42.5 ms 64 bytes from 6696192220.hostnoc.net (66.96.192.220): icmp_seq=7 ttl=54 time=42.4 ms 64 bytes from 6696192220.hostnoc.net (66.96.192.220): icmp_seq=8 ttl=54 time=42.0 ms 64 bytes from 6696192220.hostnoc.net (66.96.192.220): icmp_seq=9 ttl=54 time=41.9 ms --- nocster.com ping statistics --- 10 packets transmitted, 10 received, 0% packet loss, time 9094ms rtt min/avg/max/mdev = 41.970/42.281/42.581/0.322 ms, pipe 2
Posted by wheimeng, 09-20-2004, 10:51 AM
Reply from 66.197.186.40: bytes=32 time=334ms TTL=51 Reply from 66.197.186.40: bytes=32 time=332ms TTL=51 Reply from 66.197.186.40: bytes=32 time=331ms TTL=51 Looks good from Malaysia
Posted by viGeek, 09-20-2004, 11:10 AM
From New Jersey Pinging 66.197.186.40 with 32 bytes of data: Reply from 66.197.186.40: bytes=32 time=33ms TTL=49 Reply from 66.197.186.40: bytes=32 time=24ms TTL=49 Reply from 66.197.186.40: bytes=32 time=26ms TTL=49 Reply from 66.197.186.40: bytes=32 time=34ms TTL=49
Posted by rushik, 09-20-2004, 02:37 PM
Hi, I got reply via chat that i was a network problem with level3.net. and it was resolved in half an hour. but this shouldn;t happen again i suppose. thanks to all those who had replied and helped me. thanks.
Posted by kapot, 09-21-2004, 03:27 PM
21:23 from NL I have two servers, one UP and one DOWN Partial network outage sux
Posted by kapot, 09-21-2004, 03:30 PM
support.burst.net is also dead !
Posted by nemonoman, 09-21-2004, 06:12 PM
No luck pinging 65.75.163.220 Is this Managed problem or my problem?
Posted by AshleyMiller, 09-21-2004, 07:08 PM
I am able to ping to 65.75.163.220 just fine. Ash