Fdcservers trouble?

Portal Home > Knowledgebase > Industry Announcements > Web Hosting Main Forums > Providers and Network Outages and Updates > Fdcservers trouble?

Posted by Etian, 08-17-2011, 01:21 PM
Beginning last night 6pm pacific time, I could not reach their website or either of my servers from home or from my server at Liquidweb. At 4am, I could reach them through my server at liquidweb, but still not from home. I can traceroute from my server to home, but a traceroute from home to my servers or to www.fdcservers.net fizzles out at:
sjo-bb1-link.telia.net

Is the trouble with my home ISP (qwest) or with fdcservers?
Posted by ayksolutions, 08-17-2011, 02:10 PM
I can confirm this. I'm not able to reach their site from TimeWarner in NY.
Posted by jonabyte, 08-17-2011, 02:43 PM
loads fine for me in EST
Posted by tumble, 08-17-2011, 03:09 PM
Tracing from so Cali via Time Warner:
C:\Users\Admin>tracert www.fdcservers.net

Tracing route to www.fdcservers.net [66.90.66.155]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 9 ms 8 ms 9 ms cpe-76-172-0-1.socal.res.rr.com [76.172.0.1]
3 7 ms 9 ms 9 ms 76.167.25.61
4 14 ms 23 ms 23 ms tge0-8-0-10.vnnyca2-cr02-socal.rr.com [72.129.13
.200]
5 20 ms 23 ms 23 ms 72.129.13.2
6 12 ms 16 ms 15 ms 107.14.17.134
7 14 ms 11 ms 12 ms ae-1-0.pr0.lax10.tbone.rr.com [66.109.6.131]
8 16 ms 15 ms 15 ms be-10-303-pe01.600wseventh.ca.ibone.comcast.net
[66.208.233.109]
9 14 ms 11 ms 12 ms pos-2-0-0-0-cr01.losangeles.ca.ibone.comcast.net
[68.86.86.57]
10 46 ms 47 ms 50 ms pos-0-13-0-0-cr01.dallas.tx.ibone.comcast.net [6
8.86.85.146]
11 63 ms 60 ms 62 ms pos-2-11-0-0-cr01.denver.co.ibone.comcast.net [6
8.86.87.29]
12 78 ms 79 ms 79 ms pos-0-11-0-0-cr01.chicago.il.ibone.comcast.net [
68.86.86.185]
13 75 ms 77 ms 76 ms pos-1-4-0-0-cr01.350ecermak.il.ibone.comcast.net
[68.86.88.34]
14 80 ms 78 ms 78 ms pos-1-5-0-0-pe01.350ecermak.il.ibone.comcast.net
[68.86.87.126]
15 77 ms 76 ms 75 ms comcast02.chi.fdcservers.net [75.149.229.82]
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * *

From servers at webnx:

traceroute to www.fdcservers.net (66.90.66.155), 30 hops max, 40 byte packets
1 67-220-212-33.hosted.static.webnx.com (67.220.212.33) 0.825 ms 0.793 ms 0.803 ms
2 67-220-192-105.hosted.static.webnx.com (67.220.192.105) 0.768 ms 0.772 ms 0.770 ms
3 ge9-27.br01.lax05.pccwbtn.net (63.218.42.193) 1.719 ms 1.723 ms 1.720 ms
4 comcast.Tenge13-3.br02.sjo01.pccwbtn.net (63.218.179.26) 13.680 ms 13.681 ms 13.679 ms
5 pos-2-4-0-0-cr01.sanjose.ca.ibone.comcast.net (68.86.87.9) 11.656 ms 11.662 ms 11.661 ms
6 pos-0-12-0-0-cr01.denver.co.ibone.comcast.net (68.86.85.121) 52.614 ms 52.638 ms 52.631 ms
7 pos-0-13-0-0-cr01.chicago.il.ibone.comcast.net (68.86.85.245) 78.591 ms 78.592 ms 78.589 ms
8 pos-1-8-0-0-cr01.350ecermak.il.ibone.comcast.net (68.86.88.50) 78.665 ms 78.627 ms 78.609 ms
9 pos-1-4-0-0-pe01.350ecermak.il.ibone.comcast.net (68.86.86.162) 79.579 ms 79.579 ms 79.575 ms
10 comcast02.chi.fdcservers.net (75.149.229.82) 68.553 ms 68.595 ms 68.570 ms
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
Posted by ayksolutions, 08-17-2011, 04:04 PM
Yeah, not sure what to say. My pings reach them ok, but seems like there may be an issue there.
Posted by webhostmaniac, 08-17-2011, 05:12 PM
I am not sure if this is related but I currently face packet loss issues with fdc as well.

http://www.webhostingtalk.com/showthread.php?t=1074745
Posted by node, 08-17-2011, 05:55 PM
Site loads fine and 2 of my servers in Chicago also do.
Posted by ripken204, 08-17-2011, 07:54 PM
I have Road Runner in Rochester NY and I have been unable to connect since yesterday as well.

What's odd is that it is just Road Runner. 3G and Frontier DSL work just fine. ping times are 800+ ms

this is to my server

Quote:

1 192.168.0.1 (192.168.0.1) 0.411 ms 0.796 ms 0.943 ms
2 10.240.192.1 (10.240.192.1) 8.331 ms 8.468 ms 8.460 ms
3 gig9-21.rochnyeq-rtr002.wny.northeast.rr.com (24.93.12.5) 8.818 ms 8.954 ms 8.945 ms
4 rdc-72-230-153-135.wny.northeast.rr.com (72.230.153.135) 39.990 ms 40.111 ms 40.102 ms
5 rdc-72-230-153-243.wny.northeast.rr.com (72.230.153.243) 12.980 ms 13.102 ms 13.237 ms
6 107.14.19.28 (107.14.19.28) 27.044 ms ae-3-0.cr0.chi10.tbone.rr.com (66.109.6.72) 21.968 ms 22.882 ms
7 ae-0-0.pr0.chi10.tbone.rr.com (66.109.6.153) 23.010 ms 23.001 ms 23.186 ms
8 te-1-14-0-0-pe01.350ecermak.il.ibone.comcast.net (75.149.230.201) 23.381 ms te-1-12-0-1-pe01.350ecermak.il.ibone.comcast.net (75.149.230.69) 24.714 ms 24.571 ms
9 * * *
10 vds118243.fdcservers.net (66.90.118.243) 37.480 ms 37.312 ms 40.593 ms
11 . (XXXXXXXXXX) 1159.732 ms 1159.872 ms 1158.405 ms

Posted by Etian, 08-18-2011, 08:56 AM
It is resolved now, AFAIK. I received no reply to emails to support, nor is there any mention in their forum. Last night I got this from my ISP:
--------
Hello,

Thank you for contacting Qwest, now CenturyLink.

I was also unable to access www.fdcservers.net from a CenturyLink connection, here is the copy of the trace route from that connection:

traceroute to www.fdcservers.net (66.90.66.155), 30 hops max, 40 byte packets
1 67.41.36.190 (67.41.36.190) 1.265 ms 2.005 ms 2.744 ms
2 boid-dsl-gw04-196.boid.qwest.net (184.99.64.196) 35.639 ms 36.529 ms 37.053 ms
3 boid-agw1.inet.qwest.net (184.99.65.25) 38.655 ms 39.173 ms 39.680 ms
4 sjp-brdr-04.inet.qwest.net (67.14.34.38) 71.892 ms 72.616 ms 73.133 ms
5 sjo-bb1-link.telia.net (213.248.87.49) 73.647 ms 74.156 ms 75.227 ms
6 chi-bb1-link.telia.net (213.248.80.24) 108.051 ms 94.112 ms 93.133 ms
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

I then tried to access that site from a no CenturyLink connection and also was unable to reach the site. Here is the result of that failed trace route:

TraceRoute to 66.90.66.155 [www.fdcservers.net]

Hop (ms) (ms) (ms) IP Address Host name
1 0 0 0 206.123.64.154 -
2 0 0 0 173.219.246.92 173-219-246-92-link.sta.suddenlink.net
3 33 34 38 173.219.254.168 173-219-254-168-link.tex.sta.suddenlink.net
4 29 30 29 66.76.232.17 66-76-232-17.tyrd.suddenlink.net
5 29 29 29 66.76.232.10 chicosrc01-10gex2-1.tex.sta.suddenlink.net
6 29 29 29 206.223.119.65 eqx-ibx.fdcservers.net
7 30 30 30 66.90.127.177 66.90.127.177
8 Timed out Timed out Timed out -
9 Timed out Timed out Timed out -
10 Timed out Timed out Timed out -
11 Timed out Timed out Timed out -
Posted by ripken204, 08-18-2011, 09:50 AM
this morning (before 8am EST) it was still not working for me.
I am on a different ISP now and it works fine.
Posted by ayksolutions, 08-18-2011, 11:22 AM
I believe there is still an issue with roadrunner. Their networking dept mentioned this. It's still an issue for me.
Posted by sneezes, 08-18-2011, 03:25 PM
This may be resolved. I have a server with FDC and I've been notified now by several TWC/RR customers that they are able to access my server again today.
Posted by ripken204, 08-18-2011, 05:39 PM
still down for me
Posted by blenard, 08-18-2011, 08:11 PM
me too from several locations
Posted by ripken204, 08-18-2011, 09:45 PM
ok, it works now. time to cancel my service...
Posted by strat, 08-22-2011, 02:07 PM
anyone else down in denver now??

edit: looks like its back.