Some systems are experiencing issues

Past Incidents

17th July 2018

No incidents reported

16th July 2018

Planned Network Maintenance - NYC Chelsea Data Center - Core Switch Maintenance, scheduled 1 day ago

Our network team will be performing maintenance on the core switches in our NYC Chelsea data center. The scope of the project is to replace our existing core switches with new ones in order to increase capacity and improve network stability. Maintenance will be conducted in three parts between the hours of 00:00 and 06:00 (EDT), local time to our New York data center, on July 16th, 17th and 18th 2018.


Part 1

Date of Maintenance: 2018-07-16

Time of Maintenance: 00:00 - 06:00 EDT (04:00 – 10:00 UTC)

Location of Maintenance: New York, NY

Reason for Maintenance: Deployment of new core switches to increase capacity and improve network stability.

Expected Impact: There is no expected impact in this maintenance window. New equipment will be installed but will not be in line for production traffic.


Part 2

Date of Maintenance: 2018-07-17

Time of Maintenance: 00:00 - 06:00 EDT (04:00 – 10:00 UTC)

Location of Maintenance: New York, NY

Reason for Maintenance: Deployment of new core switches to increase capacity and improve network stability.

Expected Impact: There will be instances where the network will be running at a reduced capacity and may include packet loss while new equipment is brought in line for production traffic.


Part 3

Date of Maintenance: 2018-07-18

Time of Maintenance: 00:00 - 06:00 EDT (04:00 – 10:00 UTC)

Location of Maintenance: New York, NY

Reason for Maintenance: Deployment of new core switches to increase capacity and improve network stability.

Expected Impact: There is no expected impact in this maintenance window. Decommissioned legacy equipment will be removed from the network racks during this maintenance period.


As always, if at any time you have questions or concerns please contact our technical support staff. Our expert staff is available 24 hours a day as a resource for your account. Feel free to submit a ticket from within your account or create a chat at: https://www.vps.net/support/#contact

If you have any questions or concerns, please contact support@VPS.NET

PLANNED MAINTENANCE: POSSIBLE SERVICE DISRUPTION in SNG01 on July 27, 2018 at 2200 SGT (UTC +8)

Start Date: Friday 27-Jul-2018 14:00 UTC End Date: Saturday 28-Jul-2018 00:00 UTC Duration: 10 hours Event Type: Planned Event

Your account is at risk for a service disruption due to a maintenance event that will reroute current network traffic from Master Backend Router (MBR01) to Master Backend Router (MBR02) to decommission MBR01. This is a continuation of the maintenance on July 13, 2018 (Event ID 59794703).

This effort will ensure continued security and availability of the production network. During this maintenance, there may be delays in server provisioning, access to backend services such a storage and some OS updates may occur.

We will take every effort to prevent any downtime. Given the nature of the work and the device, we recommend that all customers to create a backup of the data on their Virtual Server Instances as a precaution, as delays in traffic beyond only a few seconds could cause servers to go read-only.

Network Engineers will be migrating services from MBR01 to MBR02(a)(b) in six units of work. We have all MSS(s) segmented in four groups.

  1. Migrate MBR02(a)(b) and the ASS(s) and MSS(s) below the routers to spanning-tree domain as MBR01-MST
  2. Straddle Group 1 between MBR01 and MBR02(a)(b) and for each MSS in Group 1 configure new port-channel to MBR02(a)(b) and establish connectivity, shut the link of MBR01 and migrate to MBR02(a)(b)
  3. Straddle Group 2 between MBR01 and MBR02(a)(b) and for each MSS in Group 2 configure new port-channel to MBR02(a)(b) and establish connectivity, shut the link of MBR01 and migrate to MBR02(a)(b)
  4. Straddle Group 3 between MBR01 and MBR02(a)(b) and for each MSS in Group 3 configure new port-channel to MBR02(a)(b) and establish connectivity, shut the link of MBR01 and migrate to MBR02(a)(b)
  5. Straddle Group 4 between MBR01 and MBR02(a)(b) and for each MSS in Group 4 configure new port-channel to MBR02(a)(b) and establish connectivity, shut the link of MBR01 and migrate to MBR02(a)(b)
  6. Decommission MBR01

Customers can expect to receive a reminder notification no later than 24 hours in advance and one update no later than 1 hour before the maintenance window is open.

We anticipate the maintenance to take up to 10 hours.

This will be updated at the completion of each phase and at the completion of the maintenance.

Please follow normal procedures for notifications of an outage and reference this post. Network Engineering along with Engineers from Compute and Storage will monitor this event and be available for assistance if needed.

15th July 2018

No incidents reported

14th July 2018

No incidents reported

13th July 2018

No incidents reported

12th July 2018

PLANNED MAINTENANCE: POSSIBLE SERVICE DISRUPTION in SNG01 on July 13, 2018 at 22:00 SGT (UTC/GMT +8)

Start Date: Friday 13-Jul-2018 14:00 UTC End Date: Friday 13-Jul-2018 20:00 UTC Duration: 6 hours Event Type: Planned Event

Accounts will be at risk for a service disruption due to a maintenance event that will reroute current network traffic from Master Backend Router (MBR01) to Master Backend Router (MBR02) to decommission MBR01. This effort will ensure continued security and availability of the production network. During this maintenance, there may be delays in server provisioning and access to backend services such a storage, OS updates, and customer VPNs may be unavailable.

We will take every effort to prevent any downtime. Given the nature of the work and the device, we request all customers to create a backup of all data on their Virtual Server Instances as a precaution, as delays in traffic beyond only a few seconds, could cause servers to go read-only.

Network Engineers will be migrating services from MBR01 to MBR02(a)(b) in six units of work. We have all MSS(s) segmented in four groups.

  1. Migrate MBR02(a)(b) and the ASS(s) and MSS(s) below the routers to spanning-tree domain as MBR01-MST
  2. Straddle Group 1 between MBR01 and MBR02(a)(b) and for each MSS in Group 1 configure new port-channel to MBR02(a)(b) and establish connectivity, shut the link of MBR01 and migrate to MBR02(a)(b)
  3. Straddle Group 2 between MBR01 and MBR02(a)(b) and for each MSS in Group 2 configure new port-channel to MBR02(a)(b) and establish connectivity, shut the link of MBR01 and migrate to MBR02(a)(b)
  4. Straddle Group 3 between MBR01 and MBR02(a)(b) and for each MSS in Group 3 configure new port-channel to MBR02(a)(b) and establish connectivity, shut the link of MBR01 and migrate to MBR02(a)(b)
  5. Straddle Group 4 between MBR01 and MBR02(a)(b) and for each MSS in Group 4 configure new port-channel to MBR02(a)(b) and establish connectivity, shut the link of MBR01 and migrate to MBR02(a)(b)
  6. Decommission MBR01

Customers can expect to receive a reminder notification no later than 24 hours in advance and one update no later than 1 hour before the maintenance window is open. We anticipate maintenance to take up to 6 hours. The ticket will be updated once at the completion of the maintenance.

Please follow normal procedures for notifications of an outage and reference this ticket. Network Engineering along with Engineers from Compute and Storage will monitor this event and be available for assistance, if needed.

/ Event Updates /

  • As of Thursday 12-Jul-2018 17:25 UTC This maintenance remains on track to begin 2:00 pm Greenwich Mean Time (UTC +0), Friday, July 13, 2018.

  • As of Thursday 07-Jun-2018 20:41 UTC The maintenance scheduled for June 22 has been rescheduled to July 13 due to a conflict with a previously scheduled maintenance. We apologize for any inconvenience this may cause.

11th July 2018

No incidents reported