Before anyone says it; yes I've done the search..I know all about what has happened to FDC recently.


What I'd like to hear is how their colocation plans are right now. I see un-metered shared 100mbit connection...I can't possibly imagine that being very reliable.

I could be wrong though; does anyone have a server hosted with them on this plan? How are the response times and such on the connection? Would you host a small number of clients on such a connection?

Also, are they back to using Cogent again? I did a traceroute on the server they have adveritised as "one of our customers bandwidth meter" on their website but it traces to cogent. Is FDC using cogent again and possibly falsely claiming to be offering un-metered non-cogent bandwidth; or did this person leave FDC and they simply haven't taken that link off their site?



1 Telecom9-FastEthernet12-18.gw.psu.edu (146.186.23.193) 1.358 ms 1.181 ms 1.164 ms
2 Telecom1-ATM3-1.18.gw.psu.edu (172.30.15.181) 1.427 ms 1.377 ms 1.433 ms
3 bar-psu-i1-so-4-2-0-1.psc.net (192.88.115.189) 4.950 ms 4.815 ms 4.891 ms
4 minime.psc.net (192.88.115.5) 5.182 ms 5.295 ms 5.681 ms
5 pos4-1-1-0.a01.pitbpa05.us.ra.verio.net (199.239.216.13) 5.454 ms 5.218 ms 5.292 ms
6 p4-2-1-0.r02.mclnva02.us.bb.verio.net (129.250.16.90) 10.623 ms 11.062 ms 10.552 ms
7 p16-7-0-0.r01.mclnva02.us.bb.verio.net (129.250.5.11) 11.267 ms 11.017 ms 11.116 ms
8 p16-0-1-0.r21.asbnva01.us.bb.verio.net (129.250.2.181) 12.112 ms 12.082 ms 11.812 ms
9 p16-7-0-0.r01.asbnva01.us.bb.verio.net (129.250.5.20) 12.204 ms 11.773 ms 11.915 ms
10 p9-0.pr01.iad01.atlas.psi.net (154.54.10.25) 11.536 ms 11.611 ms 11.598 ms
11 p1-0.core01.dca01.atlas.cogentco.com (154.54.2.197) 12.887 ms 12.538 ms 12.806 ms
12 p15-0.core02.dca01.atlas.cogentco.com (66.28.4.22) 13.127 ms 13.562 ms 13.143 ms
13 p6-0.core01.jfk02.atlas.cogentco.com (66.28.4.82) 129.484 ms 85.789 ms 104.489 ms
14 p15-0.core02.jfk02.atlas.cogentco.com (66.28.4.14) 19.349 ms 18.784 ms 18.668 ms
15 p14-0.core02.ord01.atlas.cogentco.com (66.28.4.86) 134.711 ms 230.595 ms 244.118 ms
16 g50.ba02.b000268-0.ord01.atlas.cogentco.com (66.28.66.78) 53.847 ms 54.059 ms 53.991 ms
17 amaroq.org (66.28.242.252) 165.278 ms 159.193 ms 170.245 ms

I think that a section of their lines were not shut down... or something like that :confused:

Or cogent has reissued the IP to someone else. They usally reissue them fast.

I'm currently getting some packet loss, ugh... I thought this was done away with when Yipes was brought in.


Packets: Sent = 100, Received = 83, Lost = 17 (17% loss),
Approximate round trip times in milli-seconds:
Minimum = 60ms, Maximum = 160ms, Average = 70ms

The "client" that has the bandwidth meter was up 100% during the FDC Cogent downtime, so I'm not sure it is really an FDC client.

The rwhois on that IP shows:

org-name Arrow Futures and Options
street-address 141 W Jackson Blvd Ste. 3805
city Chicago
state IL
postal-code 60604


Maybe that's FDC's new partnership (the multiple companies getting a new DC as partners)?


- Matt

That part of their network was setup before they became FDCservers, so it's registered under a different business name. Cogent never shut it down as they didn't know (and by the look of it still don't know) that those IP's are actually FDCservers.

Amaroq is a client, he signed up with them about 2 days before I did when kingcomp first started dedicated hosting. Unlike Amaroq, I left as I got sick of the bad service. I realised it was time to stop looking for the cheapest solution and look for more realistic offers.

Originally posted by mainarea
The "client" that has the bandwidth meter was up 100% during the FDC Cogent downtime, so I'm not sure it is really an FDC client.


As Tazzman said, it is indeed a box located (well, colocated) at FDC.