[COMPLETED] NYC location migration. (Scheduled)
- Priority - Medium
- Affecting Other - NYC1-NYC7
Hi, we are currently performing migration between 2 NY datacenters, the affected servers are:
NYC1, NYC2, NYC3, NYC4, NYC5, NYC6, NYC7.
All servers will be live migrated to our newest datacenter: Equinix NY2 (275 Hartz Way, Secaucus, NJ), which will offer more superior network connectivity, lower latency and higher uptime with fully redundant power and cooling compares with our current datacenter: VxChnge NJ1 (200b Meadowlands Parkway, Secaucus, NJ)
This migration will also allow us to install 40G internal networks between servers which offer higher transfer speed and less congestions!
It's expected that the migration will take 2-5 hours to be fully completed.
Even though all servers are live migrated (meaning your server software will still be running), migrated servers will not be accessible to internet until the migration completed as we need to migrate our subnets over from old to new datacenter. In case you need access to your server, please create a ticket on our panel and our staff will change your server IP to a new IP that will give your server access to our new network!
Further updates will be available below as we proceed with the migration.
[Update 1] At: 4 PM (GMT +7) 02/21/2021: we've started migration on NYC1 and NYC2, completion ETA: 1 hours 10 minutes. We will post further updates below.
[Update 2] At: 5:09 PM (GMT +7) 02/21/2021: NYC1 and NYC2 have been migrated, we've started migration on NYC3 and NYC4 just now, ETA: 1 hour 12 minutes.
[Update 3] At: 5:56 PM (GMT +7) 02/21/2021: NYC3 and NYC4 have been migrated, we've started migration on NYC5 and NYC6 just now.
[Update 4] At: 6:49 PM (GMT +7) 02/21/2021: NYC5 and NYC6 have been migrated, we've started migration on NYC7 just now.
[Update 4] At: 8:06 PM (GMT +7) 02/21/2021: NYC7 has been migrated, IP subnets have been reconfigured to our new network, all servers have been reinstated!
Thank you for your patience and understanding - we will do our very best to make sure the migration is smoothly done with minimal impact. If you have any questions, please hit up a ticket on our panel!
- Date - 02/21/2021 16:00 - 02/21/2021 20:06
- Last Updated - 02/21/2021 20:35
Internal Error (Investigating)
- Priority - High
- Affecting System - US and UK
We are currently experiencing a huge RDP bruteforcing/flooding attack that will prevent you from accessing your server. Our network admins is working on mitigating the attacks, however, the attacks is launched from a wide range of IPs that made it extremely difficult for us to block them all.
There are currently 2 ways to solve the issues:
- Install RDP protection tool to your server: https://rdpguard.com/ (for Windows 2012 and 2016 - free trial available) or https://github.com/neil-sabol/EZWinBan/releases/tag/v3.0.0 (for Windows 2016 - completely free and open sources). You can use the Console feature on our panel to access your server and install one of the above tools.
- Access the server via Console feature and change RDP port: Open Powershell and use the following commands:
New-NetFirewallRule -DisplayName "Custom RDP" -Direction Inbound –LocalPort [Your RDP Port] -Protocol TCP -Action Allow
Set-ItemProperty -Path 'HKLM:\System\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp' -name "PortNumber" -Value [Your RDP Port]
A restart is required for the new RDP port to take effect, once the server is restarted, you will need to use the new port to connect to your server, example: 220.127.116.11:9999 instead of 18.104.22.168
Thank you for your patience and understanding! If you have any further questions, please hit us up with a ticket!
- Date - 08/31/2020 05:06
- Last Updated - 01/03/2021 07:17