east.tastyspleen.net (tourney4, et al.) was unexpectedly vaporized

[quadz]

Greetings,

So, the hosting company where t4 was located has deleted the entire datacenter where the server was hosted.

Response to my inquiry: "That device was hosted in our LDJ data center. That datancenter[sic] got closed last week. Hence, all devices associated to it were deleted."

As far as I can tell, this was done with no advance warning. (They claim they sent an email beforehand, but I see no record of it anywhere, including spam folders. I've got plenty of emails from them around that time saying things like, "The network team has informed us that network connectivity has been restored." But nothing whatsoever about them pulling the plug.)

Anyway... At this time, I have no immediate plans to seek other hosting. (Frankly I'm looking for ways to save money, so while this was unexpected, the $48/mo savings is not entirely unwelcome.)

[Sgt. Dick]

Thanks for all you have done and continue to do to keep this game alive 

[quadz]

Anyway... At this time, I have no immediate plans to seek other hosting

BTW, IF ANYONE has some sort of reliable east coast hosting that has game-quality pings and is maintained by someone other than fruitcakes who will delete datacenters at a whim ......

[haunted]

It would be nice if we found another reliable data center in nj because I think nj has the highest concentration of transatlantic fiber lines. Otherwise any reliable place would work. Baltimore/DC/Richmond area is probably 'midway' for east coast q2.

[claire]

My NJ server is housed with Choopa.net. They're probably out of your budget directly, but I'll look around to see if someone in their datacenter has cheaper servers.

I'm assuming you're looking for a dedicated server? If a KVM VPS would work buyvm.net is VERY good (in Choopa) and rather affordable.

For DC, I have a KVM directly with Leaseweb and they're awesome. I find that most euro players ping the best to DC. Players in NL can usually get low 80s.

For me (being in Upstate NY) I ping better to NJ, but not much:


C:\Users\joe>ping dc.packetflinger.com

Pinging dc.packetflinger.com [198.7.63.227] with 32 bytes of data:
Reply from 198.7.63.227: bytes=32 time=32ms TTL=53
Reply from 198.7.63.227: bytes=32 time=33ms TTL=53
Reply from 198.7.63.227: bytes=32 time=31ms TTL=53
Reply from 198.7.63.227: bytes=32 time=32ms TTL=53

Ping statistics for 198.7.63.227:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 31ms, Maximum = 33ms, Average = 32ms

C:\Users\joe>ping nj.packetflinger.com

Pinging nj.packetflinger.com [2605:6400:10:366::2] with 32 bytes of data:
Reply from 2605:6400:10:366::2: time=26ms
Reply from 2605:6400:10:366::2: time=26ms
Reply from 2605:6400:10:366::2: time=26ms
Reply from 2605:6400:10:366::2: time=26ms

Ping statistics for 2605:6400:10:366::2:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 26ms, Maximum = 26ms, Average = 26ms

And they seem like they're only really about 8ms apart:
[root@nj ~]# ping dc.packetflinger.com
PING dc.packetflinger.com (198.7.63.227) 56(84) bytes of data.
64 bytes from 198.7.63.227: icmp_seq=1 ttl=54 time=8.10 ms
64 bytes from 198.7.63.227: icmp_seq=2 ttl=54 time=7.88 ms
64 bytes from 198.7.63.227: icmp_seq=3 ttl=53 time=8.19 ms
64 bytes from 198.7.63.227: icmp_seq=4 ttl=54 time=8.00 ms
64 bytes from 198.7.63.227: icmp_seq=5 ttl=53 time=7.97 ms


I'm sad that T4 is gone, Kapolsky and I must have played thousands of duels on that server over the past few years.  It will be fondly remembered. 

[haunted]

Nice, but I'd bet an 84 hour week paycheck that people from Europe are usually pinging in the 80's to DC. If so(no way) then that's your place.