Now is down again? I'm planing to take their service but I see that during the one week they two times down. What's is going on at fdcservers.net?

They are not down now

Now is UP but was via satlink:

/home/oles> traceroute 66.28.242.136
traceroute to 66.28.242.136 (66.28.242.136), 64 hops max, 40 byte packets
1 R1.UAR.NET (193.124.228.33) 1.003 ms 1.266 ms 0.925 ms
2 RA-2M-R1.UAR.Net (194.44.212.194) 2.747 ms 9.427 ms 12.405 ms
3 RC-RA.UAR.Net (194.44.212.242) 9.178 ms 215.741 ms 10.488 ms
4 RB-RC.UAR.Net (194.44.212.246) 30.046 ms 20.525 ms 49.125 ms
5 sw-319-demark.esico.net (217.196.175.205) 28.655 ms 196.875 ms 21.851 ms
6 lucky-scpc-in.esico.net (217.196.175.20) 577.470 ms 568.524 ms 586.457 ms
7 v17-car-sto-fe1-0-7.global-ip.net (194.52.4.89) 749.757 ms 599.515 ms 1073.951 ms
8 v10-bar-sto-fe0-0-0.global-ip.net (194.52.1.98) 577.383 ms 739.419 ms 583.778 ms
9 P2-0.STHBB1.Stockholm.opentransit.net (193.251.248.37) 601.738 ms 577.729 ms 612.557 ms
10 P10-0.COPBB1.Copenhagen.opentransit.net (193.251.240.153) 603.480 ms 629.561 ms 623.079 ms
11 P0-0.COPBB2.Copenhagen.opentransit.net (193.251.240.82) 617.389 ms 613.172 ms 598.940 ms
12 P3-0.FFTBB1.Frankfurt.opentransit.net (193.251.242.45) 597.582 ms 623.279 ms 624.220 ms
13 P6-0.FFTBB2.Frankfurt.opentransit.net (193.251.154.233) 618.110 ms 698.626 ms 631.233 ms
14 P2-0.BAGCR1.Bagnolet.opentransit.net (193.251.154.209) 655.031 ms 660.869 ms 712.501 ms
15 P3-0.BAGCR3.Bagnolet.opentransit.net (193.251.241.110) 676.459 ms 611.387 ms 630.166 ms
16 So3-0-0.TELBB1.Telehouse.opentransit.net (193.251.241.173) 632.758 ms 705.936 ms 1502.660 ms
17 pos0-0.mpr1.cdg4.fr.mfnx.net (208.184.210.233) 684.944 ms 671.740 ms 635.828 ms
18 208-184-231-57.above.net (208.184.231.57) 628.136 ms 1070.299 ms 665.491 ms
19 so-6-2-0.cr1.lga1.us.mfnx.net (216.200.254.77) 705.432 ms 673.554 ms 684.204 ms
20 so-0-0-0.cr1.lga2.us.mfnx.net (208.185.0.246) 706.020 ms 715.144 ms 709.280 ms
21 core1-lga2-oc48.lga4.above.net (64.124.232.6) 751.266 ms 678.609 ms 685.913 ms
22 64.124.51.186.cogentco.com (64.124.51.186) 695.976 ms 752.157 ms 695.993 ms
23 p15-0.core02.jfk02.atlas.cogentco.com (66.28.4.14) 692.572 ms 696.355 ms 677.498 ms
24 p14-0.core02.ord01.atlas.cogentco.com (66.28.4.86) 707.601 ms 714.845 ms 719.066 ms
25 g50.ba02.b000268-0.ord01.atlas.cogentco.com (66.28.66.78) 739.942 ms Datacenter.demarc.cogentco.com (66.28.21.82) 735.399 ms 754.836 ms
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
31 * * *
32 * * *
33 * * *
34 *^C

www.fdcservers.net' was found in 15 hops (TTL=47). But, problems starting at hop 14 in network "Cogent Communications" are causing IP packets to be dropped.


Roundtrip time to www.fdcservers.net, average = 162ms, min = 158ms, max = 166ms

At that time i tried three LookingGlasses in USA - they also can't see www.fdcservers.net !
DNS server at 66.28.242.136 do not answer also.

Looks okay now... maybe they got it fixed?

Owen

It's seems that guys at FDCservers.net do something with THEIR servers for few minutes and I hit this moment :-)
So everything is clear. Just in case. PLS tell me few IP's which is hosted at FDC to rectify whereis problem next time (I hope it will not happend)

Mid last week for 8 hours, one Cogent hop was really lagging.

On Thursday or Friday, I got an email stating that they are implementing a new electric backup system and that my ip block was going down for 30 min. Once it came back up, I noticed the routes between my server and my university changed to a much better routes. After all that, it has been smooth sailing.