From: Stanley Lieber <sl@stanleylieber.com>
To: 9front@9front.org
Subject: [9front] this will affect 9front.org sites
Date: Wed, 06 Nov 2024 11:53:00 -0500 [thread overview]
Message-ID: <166F62E2-90D4-4C00-8DF8-29EEAD070CAC@stanleylieber.com> (raw)
In-Reply-To: <01000193023ffc23-13a1e5ae-1acd-440a-9adf-d3e241e8ebc6-000000@email.amazonses.com>
-------- Original Message --------
From: RamNode <no-reply@ramnode.com>
Sent: November 6, 2024 11:12:48 AM EST
To: ramnode@stanleylieber.com
Subject: Ramnode - Datacenter Migration - Please Read
This email is to inform you of upcoming changes in our NYC datacenter.
After heavy consideration, we have decided to move to a different facility to service our NYC customers. Our current datacenter in this region, co-located with Telehouse International, is no longer able to accommodate our needs in terms of space and power. Additionally, upon renewal of our contract, we have been unable to negotiate affordable rates for this facility, as power costs and real estate in the Manhattan area have become increasingly more expensive, which may eventually cause us to have to increase the cost of our services. For these reasons, we have chosen to move to a nearby Tier 3 datacenter in Piscataway, NJ.
Our new datacenter provider will be Databank EWR2: https://www.databank.com/data-centers/new-jersey/piscataway/
As part of this move, our network traffic will be serviced by both Lumen and Zayo. We will also be upgrading our infrastructure to use new Arista devices to provide additional throughput up to 40Gb/s with additional redundancy that we were unable to implement in our NYC facility. These upgrades will directly facilitate our ability to implement new Cloud offerings, increase performance, and improve network availability.
It is important to understand that we will have to physically move all servers to the new location, which will cause unavoidable downtime. We have hired an experienced moving company to assist with the migration, and staff will be on-site to ensure the move goes as smoothly as possible. The migrations are scheduled to occur between 8PM and 2AM EST Wednesday through Friday, November 13-15th. You can find the planned move schedule at the below URL to determine when your server(s) will be affected.
https://mig.ewr.ramnode.com/
We greatly appreciate your patience while we work to improve our products and offerings. If you have any questions or concerns, please do not hestitate to contact us.
Regards,
RamNode
support@ramnode.com
parent reply other threads:[~2024-11-06 16:54 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <01000193023ffc23-13a1e5ae-1acd-440a-9adf-d3e241e8ebc6-000000@email.amazonses.com>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=166F62E2-90D4-4C00-8DF8-29EEAD070CAC@stanleylieber.com \
--to=sl@stanleylieber.com \
--cc=9front@9front.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).