During the maintenance window the object storage data from DK2 (Deltalis) datacenter will be migrated to ZH5 (Equinix). See https://www.exoscale.com/syslog/moving-zurich-dk2-zone/ for more information. The migration will be transparent and no impact is expected. The zone name will remain as CH-DK-2.
Related to the datacenter move https://www.exoscale.com/syslog/moving-zurich-dk2-zone/ we're going to migrate the snapshot storage system to the new Zurich datacenter. During the maintenance window new and restore snapshot functionality will not be available.
We're going to perform a maintenance on the compute API. No impact expected.
During the maintenance window all the instances from DK2 (Deltalis) datacenter will be migrated to ZH5 (Equinix). See https://www.exoscale.com/syslog/moving-zurich-dk2-zone/ for more information. The migration will be transparent for your instances. No impact is expected during the maintenance window. The zone ...
Due to migration from DK2 to ZRH1 planned next year, we need to test our migration scenario, including a network change. The change is to route DK2 traffic through ZRH1 during a few minutes. During the change, no impact is ...
We're going to perform an API maintenance. No impact is expected
We are upgrading the backbone of our network for increased performances in VIE1. No impact is expected as there is a 1+1 redundancy in place.
We're going to perform an API maintenance. During the window it will not be possible to start/stop/deploy instances from the API.
The internal network capacity for the GV2 site is being upgraded.
We are upgrading the backbone of our network for increased performances in GV2. No impact is expected as there is a 1+1 redundancy in place.
We're going to perform an API maintenance. No impact is expected.
We are going to perform a compute service upgrade. The API will stay operational but VM operations will be disabled (deploy, start, stop...).
We are upgrading the backbone of our network for increased performances in GV2. No impact is expected as there is a 1+1 redundancy in place.
To improve reliability, we will push a small network change on all sites (one after another). In some cases, a very short impact may happen (less than 10s).
Following our previous maintenance, we're required to perform an emergency maintenance to fix related issues. No impact is expected during this maintenance
We are upgrading the backbone of our network for increased performances in GV2. No impact is expected as there is a 1+1 redundancy in place.
We're going to perform an API maintenance. No impact is expected.
Configuration of our edge routers in GV2 needs to be updated. No impact is expected during the operation.
A routine network software update will be done in FRA1. No impact is expected.
A configuration change needs to be pushed for GV2. During the operation, very short traffic disruptions (less than one minute) may happen.
We need to operate an unscheduled maintenance on some network equipments.
We do not expect any outage during this operation.
To increase performance between zones, we execute the last step of the VPN upgrade.
To increase network performance and reliability, we are conducting the final steps of the cross-zone network equipments.
In order to bring new functionality and improve performance, we're performing a network maintenance on our hypervisor layer. No impact is expected during the maintenance window.
We're performing a short emergency maintenance on the compute API. During the window it will not be possible to start instances at GVA-2
To improve network performance between our zones, we are upgrading some network equipments. No impact planned. This maintenance is a re-schedule of the previous one.
During the maintenance window one of our upstream internet provider is going to perform a maintenance of its router. Traffic will be re-routed to alternate providers during the window.
To improve network performance between our zones, we are upgrading some network equipments. No impact planned.
We're going to perform a maintenance of our portal. During the maintenance window, our portal will be unavailable
We're going to perform an emergency maintenance on the compute API. During the window, the API may be briefly unavailable. It will also not be possible to start an instance on all zones.
We're going to perform a maintenance on the compute API at VIE1. During a short time frame, start and deploy of instances will not be available
To enhance the network performance between our zones, we are upgrading some network equipments.
A small network upgrade is scheduled for GV2, DK2, VIE1 and FRA1 to improve performance between the sites. No impact is expected.
A small network upgrade is scheduled for GV2, DK2, VIE1 and FRA1 to improve performance between the sites. No impact is expected.
A small network upgrade is scheduled for GV2, DK2, VIE1 and FRA1 to improve performance between the sites. No impact is expected.
One of our upstream internet provider informed us that they are going to perform an emergency maintenance to reload their router due to stability issue. During the maintenance traffic will be routed to alternate links. No impact is expected.
A small network upgrade is scheduled for GV2, DK2, VIE1 and FRA1 to improve performance between the sites. No impact is expected.
We're going to perform a maintenance on the compute API at GV2. During a short time frame, start and deploy of instances will not be available
During the maintenance we're going to perform a maintenance on one of our snapshot storage system. During the maintenance window, snapshot restore will not be available for a few minutes
During the maintenance we're going to perform a maintenance on one of our snapshot storage system. During the maintenance window, snapshot restore will not be available for a few minutes
During the maintenance window one of our upstream internet provider is going to perform a maintenance of its router. Traffic will be re-routed to alternate providers during the window.
During the maintenance we're going to perform a maintenance on one of our snapshot storage system. During the maintenance window, snapshot restore will not be available for a few minutes
During the maintenance window one of our upstream internet provider is going to perform a maintenance of its router. Traffic will be re-routed to alternate providers during the window.
During the maintenance window we are going to deploy the mitigation fixes that address the Meltdown AND Spectre known vulnerabilities.
No impact expected on running instances.
We are rolling out object storage to all customers
Our hypervisors will be rebooted to mitigate most variants of the Spectre and Meltdown vulnerabilities.
https://www.exoscale.ch/syslog/2018/01/04/spectre-and-meltdown/
Configuration of GV2 edge routers is modified to improve visibility on our network. The configuration change triggers a partial reboot of the routers. Traffic will be rerouted transparently to mitigate the impact. During the maintenance window, we expect less than ...
Configuration of DK2 edge routers is modified to improve visibility on our network. The configuration change triggers a partial reboot of the routers. Traffic will be rerouted transparently to mitigate the impact. During the maintenance window, we expect less than ...
Configuration of VIE1 edge routers is modified to improve visibility on our network. The configuration change triggers a partial reboot of the routers. Traffic will be rerouted transparently to mitigate the impact. During the maintenance window, we expect less than ...
We're are performing an unplanned maintenance on the snapshot system. During the window snapshot operations create and restore will not be available
During the maintenance window we're going to proceed with an upgrade of the object storage backend systems. Higher latency spikes and error rate may be expected.