CH-ZRH-1: maintenance for secondary network
We will perform maintenance for our secondary (out of band) network in CH-ZRH-1 aka DK2. Customer workloads will not 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 15, 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 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.