Since the other thread was hijacked....


Are they down again?

traceroute 66.227.104.10



3 130.152.180.21 2.681 ms isi-1-lngw2-atm.ln.net [AS226] Los Nettos origin AS
4 198.172.117.161 9.037 ms ge-2-3-0.a02.lsanca02.us.ra.verio.net [AS2914] Verio
5 129.250.29.136 9.914 ms xe-1-0-0.r21.lsanca01.us.bb.verio.net [AS2914] Verio
6 129.250.2.187 13.251 ms p16-1-1-0.r21.snjsca04.us.bb.verio.net [AS2914] Verio
7 129.250.2.198 11.765 ms p16-1-1-2.r21.plalca01.us.bb.verio.net [AS2914] Verio
8 129.250.3.85 11.821 ms p16-1-0-0.r00.plalca01.us.bb.verio.net [AS2914] Verio
9 198.32.176.139 12.940 ms sntcca2lce1.wcg.net (Fake rDNS)
10 64.200.210.177 12.448 ms sntcca2lce1-oc48.wcg.net (DNS error) [AS7911] Williams Communications, Inc
11 64.200.240.93 82.692 ms chcgil1wcx3-oc48.wcg.net (DNS error) [AS7911] Williams Communications, Inc
12 64.200.103.70 81.862 ms chcgil1wcx1-oc48.wcg.net (DNS error) [AS7911] Williams Communications, Inc
13 64.200.247.66 82.398 ms chcgil1wcx1-yipescommunications.wcg.net (DNS error) [AS7911] Williams Communications, Inc
14 209.120.155.11 82.464 ms DNS error [AS6517] Yipes Communications Inc.
15 *

i dunno man

it appears to be the server itself, not yipes nor fdc... :P contact support n have them reboot it (*giggles*)... :D

Yipes and Cogent are two companies that I really don't care too much for..

Seems fine from my server

traceroute to 66.227.104.10 (66.227.104.10), 64 hops max, 44 byte packets
1 sc-mcl1-br1-g4-0 (209.50.224.1) 0.655 ms 0.428 ms 0.440 ms
2 res1-avici1-g1-5-7.gnaps.net (199.232.56.121) 1.229 ms 2.890 ms 1.625 ms
3 WASHDC5LCE1.3.0.wcg.net (206.223.115.83) 1.269 ms 1.448 ms 1.349 ms
4 hrndva1wcx3-oc48.wcg.net (64.200.95.117) 1.428 ms 1.259 ms 1.143 ms
5 hrndva1wcx2-oc48.wcg.net (64.200.95.77) 32.495 ms 32.362 ms 32.492 ms
6 nycmny2wcx2-oc48.wcg.net (64.200.240.45) 32.172 ms 32.374 ms 32.543 ms
7 nycmny2wcx3-oc48.wcg.net (64.200.87.78) 32.363 ms 32.240 ms 32.263 ms
8 chcgil1wcx3-oc48.wcg.net (64.200.240.37) 32.132 ms 32.368 ms 32.325 ms
9 chcgil1wcx1-oc48.wcg.net (64.200.103.70) 32.181 ms 32.056 ms 32.575 ms
10 chcgil1wcx1-yipescommunications.wcg.net (64.200.247.66) 32.402 ms 32.957 ms 32.518 ms
11 209.120.155.11 (209.120.155.11) 37.310 ms 35.589 ms 38.830 ms
12 66.227.104.10 (66.227.104.10) 47.922 ms 32.763 ms 33.046 ms

Originally posted by netdude
i dunno man

it appears to be the server itself, not yipes nor fdc... :P contact support n have them reboot it (*giggles*)... :D

Whats wrong with yipes? I have found them to be much more reliable than your normal telco idiots

We as well would be very interested in know why you do not care for Yipes, we have had amazing uptime with them. The only problem that has ever come up was a peering issue with AT&T that was out of their hands...

Yipes thats really fast..
Do they count these downtimes in there 99.9999% uptime gaurantee

:D

Anything over 10% they count.. They have a very good SLA

Originally posted by webreseller
Anything over 10% they count.. They have a very good SLA

They have very good SLA time. What does "Anything over 10% the count".

Does that mean that they count anything over 10% packet loss as down time?