Beating a dead horse? Nocster down again?

Portal Home > Knowledgebase > Articles Database > Beating a dead horse? Nocster down again?

Posted by sysc, 11-22-2003, 06:28 AM
Oh man.... topic says it all
Posted by sysc, 11-22-2003, 06:30 AM
From the UK Pinging 64.191.61.1 with 32 bytes of data: Request timed out. Request timed out. Reply from 64.191.61.1: bytes=32 time=290ms TTL=235 Reply from 64.191.61.1: bytes=32 time=341ms TTL=235 Ping statistics for 64.191.61.1: Packets: Sent = 4, Received = 2, Lost = 2 (50% loss), Approximate round trip times in milli-seconds: Minimum = 290ms, Maximum = 341ms, Average = 315ms From Tempe Arizona PING 64.191.61.1 (64.191.61.1) 56(84) bytes of data. 64 bytes from 64.191.61.1: icmp_seq=1 ttl=247 time=258 ms 64 bytes from 64.191.61.1: icmp_seq=2 ttl=247 time=256 ms 64 bytes from 64.191.61.1: icmp_seq=3 ttl=247 time=257 ms 64 bytes from 64.191.61.1: icmp_seq=4 ttl=247 time=256 ms 64 bytes from 64.191.61.1: icmp_seq=5 ttl=247 time=259 ms 64 bytes from 64.191.61.1: icmp_seq=6 ttl=247 time=256 ms 64 bytes from 64.191.61.1: icmp_seq=7 ttl=247 time=259 ms 64 bytes from 64.191.61.1: icmp_seq=8 ttl=247 time=258 ms 64 bytes from 64.191.61.1: icmp_seq=9 ttl=247 time=257 ms 64 bytes from 64.191.61.1: icmp_seq=10 ttl=247 time=256 ms 64 bytes from 64.191.61.1: icmp_seq=11 ttl=247 time=325 ms 64 bytes from 64.191.61.1: icmp_seq=12 ttl=247 time=257 ms 64 bytes from 64.191.61.1: icmp_seq=13 ttl=247 time=257 ms 64 bytes from 64.191.61.1: icmp_seq=14 ttl=247 time=257 ms 64 bytes from 64.191.61.1: icmp_seq=15 ttl=247 time=257 ms 64 bytes from 64.191.61.1: icmp_seq=16 ttl=247 time=258 ms 64 bytes from 64.191.61.1: icmp_seq=17 ttl=247 time=257 ms 64 bytes from 64.191.61.1: icmp_seq=18 ttl=247 time=259 ms 64 bytes from 64.191.61.1: icmp_seq=19 ttl=247 time=258 ms 64 bytes from 64.191.61.1: icmp_seq=20 ttl=247 time=258 ms 64 bytes from 64.191.61.1: icmp_seq=21 ttl=247 time=259 ms 64 bytes from 64.191.61.1: icmp_seq=22 ttl=247 time=260 ms 64 bytes from 64.191.61.1: icmp_seq=23 ttl=247 time=260 ms 64 bytes from 64.191.61.1: icmp_seq=24 ttl=247 time=259 ms 64 bytes from 64.191.61.1: icmp_seq=25 ttl=247 time=308 ms 64 bytes from 64.191.61.1: icmp_seq=26 ttl=247 time=259 ms 64 bytes from 64.191.61.1: icmp_seq=27 ttl=247 time=257 ms 64 bytes from 64.191.61.1: icmp_seq=28 ttl=247 time=259 ms --- 64.191.61.1 ping statistics --- 29 packets transmitted, 28 received, 3% packet loss, time 28241ms rtt min/avg/max/mdev = 256.141/262.535/325.415/15.322 ms From Irvine CA # ping 64.191.61.1 PING 64.191.61.1 (64.191.61.1): 56 data bytes ^C --- 64.191.61.1 ping statistics --- 43 packets transmitted, 0 packets received, 100% packet loss Last edited by sysc; 11-22-2003 at 06:37 AM.
Posted by sysc, 11-22-2003, 06:40 AM
and all is normal..........but for how long.
Posted by Defcon|Rich, 11-22-2003, 07:03 AM
you seem surprized....
Posted by Mrdredd, 11-22-2003, 07:07 AM

Posted by bhaputi, 11-22-2003, 07:07 AM
If you notice any issues at all, a traceroute is the best thing to post to help us narrow it down.
Posted by sysc, 11-22-2003, 07:14 AM
What get's me is, you guys say you monitor the network and all servers on the network. But today is a prime example of how you dont. I called up and told them, they said they wernt aware of any problems. Then called again 5 mins later and the same person said he had gotten a few calls and have someone working on it. You guys should be the first to see this kind of problem.
Posted by bhaputi, 11-22-2003, 10:26 AM
Keep in mind that the person answering the phone is not the same person that monitors the network. Generally, when our networking group sees an issue, we notify support ASAP, but our customers sometimes beat us to the punch. I was aware of the minor issue this morning, and talked to support about it - probably not until after customers had already called though.
Posted by r5x, 11-22-2003, 10:31 AM
Whats up this time Dan?