During the time-window one of our Edge Routers will be rebooted. During the short reboot, we will be running in reduced capacity mode. No impact is expected.

We will perform maintenance on our Compute API. Customer workloads will not be affected but the API will be temporarily unavailable during a very short amount of time.

Snapshots will be disabled to allow the compute API maintenance. On-going snapshots will be canceled at the beginning of the compute API maintenance.

In the mentioned time window, our GEANT link provide is doing software maintenance on their equipment. A downtime of up to 1 hour can be expected. Some of the traffic might use different paths and latency increase is expected.

One of our upstream network providers will perform maintenance in de-fra-1.
During the maintenance the traffic will be re-routed through alternate provider.
No impact expected.

During the maintenance window we are going to perform a power remediation maintenance on some core network equipments, No impact is expected.

One of our upstream network providers will perform maintenance in ch-dk-2.
During the maintenance the traffic will be re-routed through alternate provider.
No impact expected.

One of our upstream network providers will perform maintenance in ch-gva-2.
During the maintenance the traffic will be re-routed through alternate provider.
No impact expected.

One of our upstream network providers will perform maintenance in %zone%.
During the maintenance the traffic will be re-routed through alternate provider.
No impact expected.

One of our upstream network providers will perform maintenance in %zone%.
During the maintenance the traffic will be re-routed through alternate provider.
No impact expected.

During this time window we will do maintenance on one of our Transit Uplink. No impact is expected.

During this time window we will do maintenance on one of our Transit Uplink. No impact is expected.

During this time window we will do maintenance on one of our Transit Uplink. No impact is expected.

During this time window we will do maintenance on one of our Transit Uplink. No impact is expected.

We are going to perform a power maintenance in one of our core infrastructure rack at CH-DK2. During the maintenance window the power redundancy will be reduced at N.

Our datacenter provider is going to conduct an emergency power maintenance at CH-GVA-2 to repair a failed switchboard. During the maintenance window the power redundancy will be reduced at N.

During the time-window one of our Edge Routers will be rebooted. During the short reboot, we will be running in reduced capacity mode. No impact is expected.

We will perform maintenance on our Compute API. Customer workloads will not be affected but a higher latency might be experienced.

One of our upstream network providers will perform maintenance in zrh1.
During the maintenance the traffic will be re-routed through alternate provider.
No impact expected.

One of our upstream network providers will perform an emergency maintenance in MUC1.
During the maintenance the traffic will be re-routed through alternate provider.
No impact expected.

We will perform maintenance on our Compute API. Customer workloads will not be affected but the API will be temporarily unavailable.

We will perform the migration of our DHCP server for Managed Private Networks.
No impact expected.

We are going to restart NLB underlying machines in ch-gva-2 in order to complete an upgrade procedure.
No impact is expected from a user point of view, but NLB instances will lose redundancy at some point during the maintenance time ...

We will perform maintenance for our secondary (out of band) network in DE-FRA-1. Customer workloads will not be affected.

We are going to restart NLB underlying machines in de-fra-1 in order to complete an upgrade procedure.
No impact is expected from a user point of view, but NLB instances will lose redundancy at some point during the maintenance time ...

Due to a database maintenance, the runstatus service will be temporarily unavailable.

One of our upstream network providers will perform maintenance in DE-FRA-1.
During the maintenance, the traffic will be re-routed through an alternate provider.
No impact is expected.

Between October 6th and October 13th, 2022, we are going to proceed with an upgrade of our object storage metadata store in our Geneva (ch-gva-2) location. This component holds object metadata and references to the underlying storage layer.

As part ...

We are scheduling a short-notice maintenance operation in our at-vie-1 Object Storage cluster. Storage and retrieval latencies may be impacted.

Between September 19th and September 23rd, 2022, we are going to proceed with an upgrade of our object storage metadata store in our Geneva (ch-gva-2) location. This component holds object metadata and references to the underlying storage layer.

As part ...

Between September 6, 2022 and September 8, 2022, we are going to proceed with an upgrade of the backend services supporting our Network Load Balancer offering.

Each customer NLB will go through a migration process. During this process:

* NLB ...

Between September 5th and September 16th, 2022, we are going to proceed with an upgrade of our object storage metadata store in our Zürich (ch-dk-2) location. This component holds object metadata and references to the underlying storage layer.

As part ...

Between August 22nd and September 2nd, 2022, we are going to proceed with an upgrade of our object storage metadata store in our Frankfurt and Vienna locations. This component holds object metadata and references to the underlying storage layer.

As ...

We will perform maintenance for our secondary (out of band) network in CH-GVA-2. Customer workloads will not be affected.

We will perform maintenance for our secondary (out of band) network in CH-GVA-2. Customer workloads will not be affected.

One of our upstream network providers will perform maintenance in DE-FRA-1, CH-GVA-2 and CH-DK-2.
Internet traffic will be re-routed through alternate provider during the maintenance and no service will be affected.

One of our upstream network providers will perform maintenance in AT-VIE-1.
Internet traffic will be re-routed through alternate provider during the maintenance and no service will be affected.

One of our upstream network providers will perform maintenance in DE-FRA-1, CH-GVA-2 and CH-DK-2.
Internet traffic will be re-routed through alternate provider during the maintenance and no service will be affected.

We will perform maintenance for our secondary (out of band) network in CH-ZRH-1 aka DK2. Customer workloads will not be affected.

Between July 4th and July 22, 2022, we are going to proceed with an upgrade of our object storage metadata store. This component holds object metadata and references to the underlying storage layer.

As part of this upgrade, your bucket(s) ...

We will be doing network maintenance that shouldn't have any customer impact, however we will be running with reduced redundancy for a short period of time.

We will be doing network maintenance that shouldn't have any customer impact, however we will be running with reduced redundancy for a short period of time.

We will perform maintenance for our secondary (out of band) network in AT-VIE-1. Customer workloads will not be affected.

We will perform maintenance for our secondary (out of band) network in BG-SOF-1. Customer workloads will not be affected.

We will perform maintenance for our secondary (out of band) network in BG-SOF-1. Customer workloads will not be affected.

One of our upstream network providers will perform maintenance in ch-gva-2.
During the maintenance the traffic will be re-routed through alternate provider.
No impact expected.

We will be conducting a network maintenance that should have no customer impact, however for a short period of time(up to 15 min) we will be running in reduced redundancy mode.

We are going to perform a maintenance on our Instance Pools service. Interactions with Instance Pools might not succeed.

We will perform maintenance for our secondary (out of band) network in DE-MUC-1. Customer workloads will not be affected.

We are going to perform a maintenance on our Instance Pools service. Interactions with Instance Pools might not succeed.

During the time window we will restart some services. No customer impact is expected.

One of our upstream provider will be performing maintenance in our DE-MUC-1 data center. This should have no impact on our services as we'll reroute the affected network traffic through our other providers.

One of our upstream network providers will perform maintenance in sof1.
During the maintenance the traffic will be re-routed through alternate provider.
No impact expected.

One of our upstream network providers will perform maintenance in gva2.
During the maintenance the traffic will be re-routed through alternate provider.
No impact expected.

One of our upstream network providers will perform maintenance in muc1.
During the maintenance the traffic will be re-routed through alternate provider.
No impact expected.

Our datacenter provider is going to perform a power maintenance. During the maintenance window the power redundancy of our equipments will be reduce to N for a maximum of 60 minutes per equipment. No impact is expected.

Our datacenter provider is going to perform a power maintenance. During the maintenance window the power redundancy of our equipments will be reduce to N for a maximum of 60 minutes per equipment. No impact is expected.

One of our upstream network providers will perform maintenance in CH-GVA-2
During the maintenance the traffic will be re-routed through alternate provider.
No impact expected.

During the window, a test of the redudant electrical system will take place. No customer impact is expected.

During the window, a test of the redudant electrical system will take place. No customer impact is expected.

We are going to perform maintenance on one of our network edge routers in DE-MUC-1. Traffic will be rerouted to avoid customer impact.

During the specified timeframe we will be replacing two Top of Rack switches in CH-GVA-2. Traffic will be rerouted accordingly to avoid any impact for customers. Some latency can potentially occur.

One of our upstream network providers will perform maintenance in CH-GVA-2
During the maintenance the traffic will be re-routed through alternate provider.
No impact expected.

One of our upstream network providers will perform maintenance in CH-DK-2
During the maintenance the traffic will be re-routed through alternate provider.
No impact expected.

We are going to perform maintenance on one of our network edge routers in CH-GVA-2. Traffic will be rerouted to avoid customer impact. You might still experience increased latency during the specified timeframe.

Our DNS partner is going to perform a maintenance on their DNS API. During this window, we expect that the API will become briefly unavailable.

DNS resolution will not be affected during this window.

During the specified timeframe we will be replacing two Top of Rack switches in CH-GVA-2. Traffic will be rerouted accordingly to avoid any impact for customers. Some latency can potentially occur.

We are going to perform maintenance on one of our network edge routers in CH-GVA-2. Traffic will be rerouted to avoid customer impact. You might still experience increased latency during the specified timeframe.

During the maintenance we will proceed with TOR (Top of the rack) network switch upgrades at CH-GVA-2. No impact is expected.

Our DNS partner is going to perform a maintenance on their DNS API. During this window, we expect that the API will become briefly unavailable.

DNS resolution will not be affected during this window.

We're going to perform an emergency maintenance on our edge routers at CH-GVA-2. During the maintenance window traffic will be re-routed to the remaining edge router and internet transit providers. No impact is expected.

One of our upstream network providers will perform maintenance in DE-FRA-1
During the maintenance the traffic will be re-routed through alternate provider.
No impact expected.

We're going to perform an emergency maintenance on our Edge routers at CH-GVA-2. During the maintenance window traffic will be re-routed to the remaining Edge router and internet transit providers. Redundancy will be at N. No impact is expected.

One of our upstream network providers will perform maintenance in SOF1.
During the maintenance the traffic will be re-routed through alternate provider.
No impact expected.

One of our upstream network providers will perform maintenance in MUC1.
During the maintenance the traffic will be re-routed through alternate provider.
No impact expected.

One of our upstream network providers will perform maintenance in MUC1.
During the maintenance the traffic will be re-routed through alternate provider.
No impact expected.

We're going to perform a maintenance on the "Private Networks" system. During the maintenance window the "Private Networks" API will not be available.

We're going to perform a maintenance on our Edge network internet transit links. During the maintenance traffic will be re-routed to alternate transit providers. No impact is expected

We're going to perform a maintenance on our Edge network internet transit links. During the maintenance traffic will be re-routed to alternate transit providers. No impact is expected

Our partner is going to perform a scheduled maintenance on their DNS API. During that window record management will not be possible. DNS resolution will not be affected

One of our internet upstream network provider is going to perform a maintenance in BG-SOF-1.
During the maintenance the traffic will be re-routed to alternate provider. No impact expected.

We're going to perform a maintenance on the maintenance pool system. During the maintenance window instance pool API will not be available

We will be applying some configuration changes on one of our Edge routers. No impact is expected.

The Compute API will be unavailable for a scheduled maintenance

One of our upstream network providers will perform maintenance in ZRH1.
During the maintenance the traffic will be re-routed through alternate provider.
No impact expected.

During the window we will replace an equipment in our network. There should be no customer impact however some instances might encounter an increase in latency.

One of our internet upstream network provider is going to perform a maintenance on its routers in AT-VIE-1.
During the maintenance the traffic will be re-routed to alternate provider. No impact expected.

We will perform maintenance work on one of VIE1 core routers. There should be no customer impact as traffic will be rerouted.

We're investigating an increase in internet network latency at DE-MUC-1

We're going to perform a maintenance on the compute API. During the maintenance window a downtime of the API is expected for 5 to 10 minutes

An emergency reboot is required on one of our routers in MUC1. During the reboot traffic will be re-routed to other routers so no impact is expected.

An reboot is required on one of our routers in MUC1. During the reboot traffic will be re-routed to other routers so no impact is expected.

An emergency reboot is required on one of our routers in MUC1. During the reboot traffic will be re-routed to other routers so no impact is expected.

We're going to conduct a maintenance on the compute API. No impact expected

During the window we will upgrade some equipment in our network. There should be no customer impact however some instances might encounter an increase in latency.

During the window we will upgrade some equipment in our network. There should be no customer impact however some instances might encounter an increase in latency.

During the window we will upgrade some equipment in our network. There should be no customer impact however some instances might encounter an increase in latency.

During the window we will upgrade some equipment in our network. There should be no customer impact however some instances might encounter an increase in latency.

During the window we will upgrade some equipment in our network. There should be no customer impact however some instances might encounter an increase in latency.

During the window we will upgrade some equipment in our network. There should be no customer impact however some instances might encounter an increase in latency.

During the window we will upgrade some equipment in our network. There should be no customer impact however some instances might encounter an increase in latency.

During the window we will upgrade some equipment in our network. There should be no customer impact however some instances might encounter an increase in latency.

During the window we will upgrade some equipment in our network. There should be no customer impact however some instances might encounter an increase in latency.

During the window we will upgrade some equipment in our network. There should be no customer impact however some instances might encounter an increase in latency.

During the window we will upgrade some equipment in our network. There should be no customer impact however some instances might encounter an increase in latency.

During the window we will upgrade some equipment in our network. There should be no customer impact however some instances might encounter an increase in latency.

We need to perform an emergency maintenance on our backbone switches in CH-DK-2

During the window we will upgrade some equipment in our network. There should be no customer impact however some instances might encounter an increase in latency.

During the window we will upgrade some equipment in our network. There should be no customer impact however some instances might encounter an increase in latency.

During the window we will upgrade some equipment in our network. There should be no customer impact however some instances might encounter an increase in latency.

During the window we will upgrade some equipment in our network. There should be no customer impact however some instances might encounter an increase in latency.

During the window we will upgrade some equipment in our network. There should be no customer impact however some instances might encounter an increase in latency.

During the window we will upgrade some equipment in our network. There should be no customer impact however some instances might encounter an increase in latency.

During the window we will upgrade some equipment in our network. There should be no customer impact however some instances might encounter an increase in latency.

One of our internet upstream network provider is going to perform a maintenance on its routers in AT-VIE-1.
During the maintenance the traffic will be re-routed to alternate provider. No impact expected.

During the window we will upgrade some equipment in our network. No impact is expected as traffic is re-routed.

During the window we will upgrade some equipment in our network. No impact is expected as traffic is re-routed.

During the window we will upgrade some equipment in our network. No impact is expected as traffic is re-routed.

During the window we will upgrade some equipment in our network. No impact is expected as traffic is re-routed.

We're going to perform a maintenance on the snapshot infrastructure.
Snapshot operations may be unavailable during the maintenance.

The maintenance will be done in all zones (ch-gva-2, ch-dk-2, at-vie-1, de-fra-1, bg-sof-1, de-muc-1)

During the window we will upgrade some equipment in our network. No impact is expected as traffic is re-routed.

During the window we will upgrade some equipment in our network. No impact is expected as traffic is re-routed.

During the window we will upgrade some equipment in our network. No impact is expected as traffic is re-routed.

During the window we will upgrade some equipment in our network. No impact is expected as traffic is re-routed.

During the window we will upgrade some equipment in our network. No impact is expected as traffic is re-routed.

During the window we will upgrade some equipment in our network. No impact is expected as traffic is re-routed.

During the window we will restart the routing daemon on some equipment. No impact is expected as traffic is re-routed.

During the maintenance you may experience few minutes of disruption of these services:

- Manage Privnets
- Instance pools
- Templates Register

We're going to perform a maintenance on the compute API.
We don't expect any downtime during the maintenance window but in some cases, a very short impact may happen (few seconds).

During the window we will upgrade an equipment in our network. No impact is expected as traffic is re-routed.

We're going to perform a maintenance on the compute API in CH-DK-2.
During the maintenance you may experience few minutes of disruption of these services:

- Manage Privnets
- Instance pools
- Templates Register

We're going to perform a maintenance on the compute API in DE-FRA-1.
During the maintenance you may experience few minutes of disruption of these services:

- Manage Privnets
- Instance pools
- Templates Register

During the window we will upgrade an equipment in our network. No impact is expected as traffic is re-routed.

During the window we will replace an equipment in our network. No impact is expected as traffic is re-routed.

During the window we will do some network changes. No impact is expected.

One of our internet upstream network provider is going to perform a maintenance on its routers in MUC-1. During the maintenance the traffic will be re-routed to alternate provider. No impact expected.

During the window we will do some minor network changes. No impact is expected.

During the window we will do some minor network changes. No impact is expected.

During the window we will do some minor network changes. No impact is expected.

We're going to perform a maintenance on the compute API.
We don't expect any downtime during the maintenance window but in some cases, a very short impact may happen (few seconds)

During the maintenance window we are going to upgrade the software running on one of our equipment. No impact is expected.

We will perform a maintenance on the Object Storage in VIE1. We don't expect any downtime during the maintenance window but in some cases, you might experience a brief network latency spike.

During the maintenance window we are going to upgrade the software running on one of our equipment. No impact is expected.

During the maintenance window we are going to upgrade the software running on one of our equipment. No impact is expected.

During the maintenance window we are going to make some configuration changes. No impact is expected.

One of our internet upstream network provider is going to perform a maintenance on its routers in BG-SOF-1. During the maintenance the traffic will be re-routed to alternate provider. No impact expected.

During the maintenance window we are going to make some configuration changes. No impact is expected.

During the maintenance window we are going to make some configuration changes. No impact is expected.

During the maintenance window we are going to make some configuration changes. No impact is expected.

We're going to perform a maintenance on the compute API.
The private network and network interface API will be unavailable during the maintenance.

During the window we will do some minor network changes. No impact is expected.

During the maintenance window we are going to upgrade our edge network equipment to provide capacity, performance and scalability improvements. There will be two short network cuts for a couple of seconds until the traffic is re-routed and during the ...

During the maintenance window we are going to upgrade our edge network equipment to provide capacity, performance and scalability improvements. There will be two short network cuts for a couple of seconds until the traffic is re-routed for some customers.

During the window we are going to restart a routing service.
No impact is expected, however redundancy will be reduced during the maintenance.

We're conducting an emergency maintenance on the compute API. Less than 5 minutes downtime is expected

During the maintenance window we are going to upgrade our core network backbone to provide capacity, performance and scalability improvements. No impact is expected, however redundancy will be reduced during the maintenance.

We're going to perform a maintenance on the compute API.
We don't expect any downtime during the maintenance window but in some cases, a very short impact may happen (less than 10s)

We're going to perform a maintenance on the compute API. The private network and network interface API will be unavailable during the maintenance. You will also not be able to deploy new virtual machines attached to private networks.

During the window we are going to restart a routing service. There will be a short service cut (up to 1 min) only for the customers using the Private Connect service in Vienna.

We're going to perform a preventive network maintenance at CH-DK-2 to replace potential faulty hardware. No impact is expected.

During the maintenance window we're going to perform an upgrade of our backbone switches. No impact is expected.

We're going to perform a maintenance on the compute API. No impact expected.

During the window we are going to do a hardware and software upgrade of a part of our network infrastructure. No impact is expected.

During the window we are going to upgrade the storage SSDs firmware of part of our hypervisor fleet. No impact is expected.

During the window we are going to upgrade the storage SSDs firmware of part of our hypervisor fleet. No impact is expected.

During the window we are going to upgrade the storage SSDs firmware of part of our hypervisor fleet. No impact is expected.

We are deploying the Intel MDS vulnerabilities mitigation. No impact is expected for your instances. All zones are concerned.

More information may be found here: https://www.exoscale.com/syslog/mds-zombieload-ridl-fallout/

We are deploying the Intel MDS vulnerabilities mitigation. No impact is expected for your instances. All zones are concerned.

More information may be found here: https://www.exoscale.com/syslog/mds-zombieload-ridl-fallout/

We are deploying the Intel MDS vulnerabilities mitigation. No impact is expected for your instances. All zones are concerned.

More information may be found here: https://www.exoscale.com/syslog/mds-zombieload-ridl-fallout/

We are deploying the Intel MDS vulnerabilities mitigation. No impact is expected for your instances. All zones are concerned.

More information may be found here: https://www.exoscale.com/syslog/mds-zombieload-ridl-fallout/

We are deploying the Intel MDS vulnerabilities mitigation. No impact is expected for your instances. All zones are concerned.

More information may be found here: https://www.exoscale.com/syslog/mds-zombieload-ridl-fallout/

We are deploying the Intel MDS vulnerabilities mitigation. No impact is expected for your instances. All zones are concerned.

More information may be found here: https://www.exoscale.com/syslog/mds-zombieload-ridl-fallout/

During the maintenance window we are going to upgrade our core network backbone to provide capacity, performance and scalability improvements. No impact is expected, however redundancy will be reduced during the maintenance.

During the window we are going to upgrade the storage SSDs firmware of part of our hypervisor fleet. No impact is expected.

During the window we are going to upgrade the storage SSDs firmware of part of our hypervisor fleet. No impact is expected.

During the window we are going to upgrade the storage SSDs firmware of part of our hypervisor fleet. No impact is expected.

During the window we are going to upgrade the storage SSDs firmware of part of our hypervisor fleet. No impact is expected.

During the window we are going to upgrade the storage SSDs firmware of a part of our hypervisor fleet. No impact is expected.

During the window we are going to upgrade the storage SSDs firmware of a part of our hypervisor fleet. No impact is expected.

We're going to perform a preventive power maintenance on few hypervisors in CH-DK-2.
No impact is expected during the maintenance window but we will briefly loose power redundancy.

We're going to perform a maintenance on the compute API. No impact expected.

We're going to conduct a maintenance on each zone of our Object Storage platform.
We don't expect any downtime during the maintenance window but in some cases, you might experience a brief network latency spike.

We are upgrading one pair of switches.
No impact is expected.

One of our internet upstream network provider is going to perform a maintenance on its routers in CH-DK-2. During the maintenance the traffic will be re-routed to alternate provider. No impact expected.

We're going to conduct a series of maintenance to fix a potential overheating issue on the hardware running the object storage. During the maintenance, the number of available read replica may be reduced up to 1 for objects hosted on ...

During the maintenance window we're going to physically install new core network equipments. No impact is expected during the maintenance.

A maintenance operation on the Exoscale compute remote console will be performed. During the operation, access to the compute instances remote console will be disabled – your compute instances will not be affected.

We're going to conduct a series of maintenance to fix a potential overheating issue on the hardware running the object storage. During the maintenance, the number of available read replica may be reduced up to 1 for objects hosted on ...

We're going to conduct a series of maintenance to fix a potential overheating issue on the hardware running the object storage. During the maintenance, the number of available read replica may be reduced up to 1 for objects hosted on ...

We're going to conduct a series of maintenance to fix a potential overheating issue on the hardware running the object storage. During the maintenance, the number of available read replica may be reduced up to 1 for objects hosted on ...

We're going to perform a corrective maintenance on a few object storage back-end systems. No impact is expected during the maintenance window.

We're going to conduct a series of maintenance to fix a potential overheating issue on the hardware running the object storage. During the maintenance, the number of available read replica may be reduced up to 1 for objects hosted on ...

One of our internet upstream network provider is going to perform a maintenance on its routers in DE-FRA-1. During the maintenance the traffic will be re-routed to alternate provider. No impact expected.

We're going to conduct a series of maintenance to fix a potential overheating issue on the hardware running the object storage. During the maintenance, the number of available read replica may be reduced up to 1 for objects hosted on ...

One of our internet upstream network provider is going to perform a maintenance on its routers in CH-GVA-2. During the maintenance the traffic will be re-routed to alternate provider. No impact expected.

We're going to conduct a series of maintenance to fix a potential overheating issue on the hardware running the object storage. During the maintenance, the number of available read replica may be reduced up to 1 for objects hosted on ...

One of our internet upstream network provider is going to perform a maintenance on its routers in DE-FRA-1. During the maintenance the traffic will be re-routed to alternate provider. No impact expected.

We're going to perform a maintenance of our API to improve performance and reliability. We expect an API downtime for a maximum of 15 minutes.

If you have any questions or concerns, please reach out to us by opening up ...

We're going to perform a maintenance on the compute API. No impact expected.

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.

GV2 edge routers are being upgraded for better performance. During the maintenance window, we expect less than a minute of instability (random packet loss).

DK2 edge routers are being upgraded for better performance. During the maintenance window, we expect less than a minute of instability (random packet loss).

We're going to perform a maintenance on the snapshots system at GV2. During the maintenance window snapshot operations (create-restore) will not be available.

Related to the outage we experienced at DK2 https://status.exoscale.ch/incidents/fa3fdc52-e6af-4d7a-88e3-b5dfeb612b75/

We're going to perform a maintenance to upgrade the power distribution units (PDU) that were impacted by the outage.

During the maintenance window, our physical hosts will loose briefly their power ...

We're going to proceed with a short compute API maintenance. During the maintenance window, the API will be unavailable for around 5 minutes. Running instances will not be affected.

A scheduled network upgrade is planned for GV2. During the maintenance, each hypervisor will be briefly disconnected from the network and reconnected a few seconds later. During this small window, the running instances won't be able to use the network. ...

A scheduled network upgrade is planned for DK2. During the maintenance, each hypervisor will be briefly disconnected from the network and reconnected a few seconds later. During this small window, the running instances won't be able to use the network. ...

We're going to proceed with a short compute API maintenance. During the maintenance window, the API will be unavailable for around 3 minutes. Running instances will not be affected.

We're going to proceed with a short compute API maintenance. During the maintenance window, the API will be unavailable. Running instances will not be affected.

We're going to proceed with a short compute API maintenance. During the maintenance window, the API will be unavailable. Running instances will not be affected.

We're going to perform a maintenance of the snapshot storage system at DK2. During the maintenance window, snapshot creation and restore will be unavailable

We're performing an unscheduled maintenance of the snapshot storage system at DK2. During the maintenance window, snapshot creation and restore will be unavailable

In order to improve our DK2 network capacity and reliability, we are going to perform a maintenance on our core switching network systems. During the maintenance, our DK2 hypervisors will be migrated to new Core network switching devices.

Impact: ...

n order to improve our DK2 network capacity and reliability, we are going to perform a maintenance on our core switching network systems. During the maintenance, our DK2 hypervisors will be migrated to new Core network switching devices.

Impact: ...

In order to improve our GV2 network capacity and reliability, we are going to perform a maintenance on our core switching network systems. During the maintenance, our GV2 hypervisors will be migrated to new Core network switching devices.

Impact: ...

In order to improve our DK2 network capacity and reliability, we are going to perform a maintenance on our core switching network systems. During the maintenance, our DK2 hypervisors will be migrated to new Core network switching devices.

Impact: ...

During the maintenance our Datacenter provider is going to upgrade power feeds of one our network equipments rack. No impact is expected as all our equipments are designed with power redundancy.

In order to improve our GV2 network capacity and reliability, we are going to perform a maintenance on our core switching network systems. During the maintenance, our GV2 hypervisors will be migrated to new Core network switching devices.

Impact: ...

In order to improve our GV2 network capacity and reliability, we are going to perform a maintenance on our core switching network systems. During the maintenance, our GV2 hypervisors will be migrated to new Core network switching devices.

Impact: ...

We're currently facing an issue with our power feeds at DK2. The power feeds are going to be replaced during the maintenance. Currently and during the maintenance, our compute and storage equipements will no longer be power redundant. No impact ...

During this scheduled maintenance we're going to upgrade the capacity of one of our links with our internet upstream providers. This specific link will be disabled and the internet traffic will be redirected to an alternate link. The link switch ...

During this maintenance we're going to perform a minor version upgrade of our object storage backend. There will be no impact to the service.

We're going to perform a network maintenance at GV2. During this maintenance, our core routing systems will be migrated to new hardware devices. We expect a very short (up to 5 seconds) interruption during the switch, which should be transparent ...

We're going to perform an emergency related to incident https://status.exoscale.ch/incidents/30487f5b-fab2-444f-9d5f-762836679b04/ Our internet edge routers are going to be migrated to new hardware devices. We expect a very short (up to 5 seconds) interruption during the switch, which should be transparent ...

Our fiber network provider is going to perform a short notice maintenance on one of our internet upstream fiber link in the CH-DK-2 zone. During the maintenance, this specific link will be disabled and internet traffic will be redirected to ...

One of our upstream internet transit provider is going to relocate our connections to a new router. During the maintenance, this specific link will be disabled and internet traffic will be redirected to an alternative link. The link switch will ...

Our upstream provider is still reporting an issue with one of our internet link which is showing errors. Additional cleaning and measurements are required to troubleshoot the issue. During the maintenance, this specific link will be disabled and internet traffic ...

Our upstream provider is reporting an issue with one of our internet link which is showing errors. An optical connectors cleaning will be performed. During the maintenance, this specific link will be disabled and internet traffic will be redirected to ...

We're going to perform an overnight (CET) data optimization maintenance on our Object storage cluster. During the maintenance window, higher than usual API response timel may be expected

Our datacenter provider is going to perform a maintenance on one of our internet upstream fiber link in the CH-DK-2 zone. During the maintenance, this specific link will be disabled and internet traffic will be redirected to an alternative link. ...

One of our upstream internet transit provider is going to relocate our connections to a new router. During the maintenance, this specific link will be disabled and internet traffic will be redirected to an alternative link. The link switch will ...

We're going to perform an object storage network overhaul In order to improve it's reliability and redundancy. No impact is expected during the maintenance window.

Our datacenter provider is going to perform a maintenance on one of our internet upstream fiber link in the CH-DK-2 zone. During the maintenance, this specific link will be disabled and internet traffic will be redirected to an alternative link. ...

We're going to perform an object storage network overhaul In order to improve it's reliability and redundancy. No impact is expected during the maintenance window.

Our ISP will perform a maintenance in order to upgrade one of their router. The internet connection from GV2 and communication with DK-2 will be degraded few minutes (flapping).

Our datacenter provider is going to perform a maintenance on one of our internet upstream fiber link in the CH-DK-2 zone. During the maintenance, this specific link will be disabled and internet traffic will be redirected to an alternative link. ...

Routine fiber network infrastructure upgrade in CH-DK-2. No availability impact expected.

We're going to perform a planned maintenance on our Apps repository endpoint (app.exo.io). All applications will remain available and reachable, however it won't be possible to push new code for a short time during the maintenance window. Other Exoscale services ...

One of our upstreams is upgrading its router. The traffic will be transparently switched to other upstreams during the operation. No impact is planned.

We're going to perform a planned maintenance on our Cloud controller system. All systems will remain available and reachable, however a delay may occur during the maintenance window when creating new instances.

We're going to perform a network maintenance on the Object storage networking. During this maintenance, a brief outage will occur but should not be more than 60s

Scheduled maintenance on Exoscale Managed Cloud Infrastructure @22:00 during approximately two hours

Beginning a scheduled maintenance. Open cloud compute web portal & API will be unavailable for approximately 15min

We are investigating network connectivity issues

Starting a non impacting managed cloud compute scheduled maintenance