Re: [cobalt-users] Problems w/ Cobaltracks.com

["Adam Holt" <mediadezines@xxxxxxxxxxxxx>]

I queried Cobalt racks as to why their site works when mine doesn't, they
told me that their site as well as a small handfull of others are in the old
data center, and so they are seperated.  So I wrote them back and told them
to put me in the old data center so that I could have the reliability that
they have.

They have yet to write me back in regards to the matter.

----- Original Message -----
From: "LightSpeedServers.Net" <admin@xxxxxxxxxxxxxxxxxxxxx>
To: <cobalt-users@xxxxxxxxxxxxxxx>
Sent: Saturday, December 02, 2000 10:44 AM
Subject: [cobalt-users] Problems w/ Cobaltracks.com


> Hey, guess what!  I too have had no end of problems with this company.
The
> connection time gets so bad I cannot connect to my server at least 2 to 3
> times a day.  Each time it lasts about 20 minutes.  And then 1 to 2 times
a
> month they have everything go to heck for almost a full day.  Look at the
> prior posts, they had the same issue occur last month!!
>
> My server was up and running for a bit this morning then things went to
hell
> for about a half hour.  Some of you probably will get a laugh out of the
> traceroute.  I have included it at the bottom of this.  Sort of reminds me
> of that old bugs bunny show w/ the cartoon character George who always
said
> "Which way do I go, which way do I go".  As you can see from the
traceroute
> it has no clue where it was going!
>
> Anyway, what I have been in the process of doing is to purchase my own
> server, and lease the line itself at a real collocation facility.  The no
> thrills type, where you are just renting space and a connection, and where
I
> myself have 24/7 access!  That way I maintain the highest level possible
of
> control at all steps of the way.
>
> Currently, I am looking at a 728kbs dedicated leased line.  Considering I
> only will have 2 servers which do not use that much BW I expect this
should
> work out nicely for me as it will provide much more reliable bandwidth
> during peak.  Less bottleneck caused by sticking hundreds of servers on a
> line already at capacity!!  Lets face it, you can have a DS-3 or higher,
but
> if you overload it with hundreds of servers, its simply is not going to
work
> very well.  A slower line with only a few servers is much better.
>
> If anyone is interested in sharing the cost of a leased line, please
contact
> me.  If a few of us get together we can get a 10 mbs connection w/o a
> problem!!  Currently, the cost I am getting is about 1.50 to 2.00 per GB
> transfer, $100 per 256 IPs, and $25.00 per 1U of rack space.  Oh, and I
> tested a server on their network for 3 days straight w/ no downtime!!
>
> And one final thought.  Cobalttracks.com knows the value of uptime on a
> website.  Have you ever noticed that their server never goes down.  Next
> time your connection goes to hell, check out their site.  They made sure
to
> route theirs seperately.  That tells me something about their company, it
> should tell you something as well!
>
> Thank you,
>
> Michael T. Ross
> admin@xxxxxxxxxxxxxxxxxxxxx
>
> 1 10.33.56.1 *  10 12 9 10
> 2 24.95.225.134 HE7-Central-GSR-P00.cfl.rr.com  23 6 13 50
> 3 24.95.225.18 HE6-Central-GSRA-P20.cfl.rr.com  13 8 12 19
> 4 24.95.225.113 HE5-Central-GSRA-P40.cfl.rr.com  13 7 7 25
> 5 24.95.226.106 HE5-Central-GSRC-P20.cfl.rr.com  10 10 13 7
> 6 24.94.158.74 TPA-ERL-GSRC-P40.cfl.rr.com  24 21 12 39
> 7 208.172.67.129 acr1-serial2-1-0-0.Atlantaald.cw.net  33 39 27 33
> 8 206.24.226.61 acr1-loopback.Washingtondck.cw.net  50 47 44 60
> 9 206.24.226.8 bar3-loopback.Washingtondck.cw.net  62 45 67 74
> 10 208.173.0.122 visual-link-internet.Washingtondck.cw.net  126 146 121
110
> 11 208.173.0.121 bar3-serial4-0-0-9-0.Washingtondck.cw.net  149 114 107
227
> 12 208.155.65.163   538 637 558 418
> 13 208.155.65.167   201 168 171 264
> 14 208.173.0.118 visual-link-internet.Washingtondck.cw.net  397 453 491
246
> 15 208.173.0.121 bar3-serial4-0-0-9-0.Washingtondck.cw.net  344 275 241
515
> 16 208.173.0.114 visual-link-internet.Washingtondck.cw.net  618 994 462
397
> 17 208.173.0.121 bar3-serial4-0-0-9-0.Washingtondck.cw.net  382 481 370
296
> 18 208.173.0.118 visual-link-internet.Washingtondck.cw.net  944 910 1045
878
> 19 208.173.0.121 bar3-serial4-0-0-9-0.Washingtondck.cw.net  802 821 736
850
> 20 208.173.0.110 visual-link-internet.Washingtondck.cw.net  1092 1433 1019
> 824
> 21 208.173.0.121 bar3-serial4-0-0-9-0.Washingtondck.cw.net  812 899 620
918
> 22 208.173.0.110 visual-link-internet.Washingtondck.cw.net  1339 1311 740
> 1967
> 23 208.173.0.121 bar3-serial4-0-0-9-0.Washingtondck.cw.net  1112 797 936
> 1604
> 24 208.173.0.118 visual-link-internet.Washingtondck.cw.net  1562 1602 1542
> 1542
> 25 208.173.0.121 bar3-serial4-0-0-9-0.Washingtondck.cw.net  1130 1285 1288
> 818
> 26 208.173.0.118 visual-link-internet.Washingtondck.cw.net  1596 1845 1475
> 1469
> 27 208.173.0.121 bar3-serial4-0-0-9-0.Washingtondck.cw.net  1628 * 1782
1475
> 28 208.173.0.110 visual-link-internet.Washingtondck.cw.net  1636 * 1631
1642
> 29 208.173.0.121 bar3-serial4-0-0-9-0.Washingtondck.cw.net  1491 * 1713
1269
> 30 208.173.0.110 visual-link-internet.Washingtondck.cw.net  1660 * 1660 *
>
> _______________________________________________
> cobalt-users mailing list
> cobalt-users@xxxxxxxxxxxxxxx
> To Subscribe or Unsubscribe, please go to:
> http://list.cobalt.com/mailman/listinfo/cobalt-users
>