Linode is a foreign VPS service provider with a good reputation. The host is based on the KVM architecture and supports hourly billing. The data centers include Tokyo, Singapore, Fremont, Atlanta, Dallas, and London, UK, Frankfurt, Germany, etc. Among them, Tokyo, Japan has been coexisting with JP1 and JP2 for a long time. Since Linode launched JP2 in 2016, newly opened Japan has been in JP2. I just received the Tokyo 1 DecommissioningNotification email from Linode.
Original message:
Hello,
We hope you're doing well! We are reaching out to inform you that on June 8th, 2019, we will begin migrating Linodes from our Tokyo 1 data center to our Tokyo 2 data center. Here's a summary of how this will affect you:
- Your IPs will change and you can view your new IPs from the Remote Access tab of your Linode's Dashboard within the Classic Manager[1].
- Your migration dates and times are available in the Classic Manager and they cannot be delayed. You can start your migration early by clicking on the “Enter the Migration Queue NOW” button on the Linode's Dashboard.
- Your existing Backups will be deleted. New Backups will be taken in Tokyo 2 .
- Your Linode(s) will experience downtime of 5-10 minutes per GB of data.
- Your Linode(s) will not be upgraded as part of this migration. You are free to upgrade your Linode( s) once they have migrated to our Tokyo 2 data center.
We are migrating Linodes out of our Tokyo 1 data center in advance of the data center being decommissioned. To help ease this transition, we've applied a credit to your account equal to one month of service for each of your Tokyo 1 Linodes. We strongly recommend you review our Tokyo 2 Migration doc[2] to help you prepare for this transition.
When your Linode(s) migrates, it will be cleanly shut down and migrated to our Tokyo 2 data center. If you initiated the migration manually, your Linode(s) will be returned to its previous state (running or powered off). You can monitor your position in the migration queue from your Linode's Dashboard.
Please do not hesitate to contact us if you have any questions or concerns.
Kind Regards,
Linode
We hope you're doing well! We are reaching out to inform you that on June 8th, 2019, we will begin migrating Linodes from our Tokyo 1 data center to our Tokyo 2 data center. Here's a summary of how this will affect you:
- Your IPs will change and you can view your new IPs from the Remote Access tab of your Linode's Dashboard within the Classic Manager[1].
- Your migration dates and times are available in the Classic Manager and they cannot be delayed. You can start your migration early by clicking on the “Enter the Migration Queue NOW” button on the Linode's Dashboard.
- Your existing Backups will be deleted. New Backups will be taken in Tokyo 2 .
- Your Linode(s) will experience downtime of 5-10 minutes per GB of data.
- Your Linode(s) will not be upgraded as part of this migration. You are free to upgrade your Linode( s) once they have migrated to our Tokyo 2 data center.
We are migrating Linodes out of our Tokyo 1 data center in advance of the data center being decommissioned. To help ease this transition, we've applied a credit to your account equal to one month of service for each of your Tokyo 1 Linodes. We strongly recommend you review our Tokyo 2 Migration doc[2] to help you prepare for this transition.
When your Linode(s) migrates, it will be cleanly shut down and migrated to our Tokyo 2 data center. If you initiated the migration manually, your Linode(s) will be returned to its previous state (running or powered off). You can monitor your position in the migration queue from your Linode's Dashboard.
Please do not hesitate to contact us if you have any questions or concerns.
Kind Regards,
Linode
It seems that many people still have Linode's JP1, and they also have a good VPS, but they have not upgraded it. Now it is confirmed that it is really going to be cancelled. My local test JP1 network is slightly better than JP2. You can refer to the test IP :
JP1 speedtest.tokyo.linode.com 106.187.96.148 JP2 speedtest.tokyo2.linode.com 139.162.65.36
postid
4988