All systems are operational

About This Site

Maintenances and incidents regarding our services, networks and datacenters can be followed here.

Scheduled Maintenance
[DC3] Scheduled maintenance - air handling

Location : DC3 datacenter

What is done : As part of an annual checks, we will verify the air handling installations in the DC3 data center. This intervention take 4 days and will be supervised by our control office.

Impact : none, it is an electrical check

Start : 09-Nov-2020 0700Z 0900LT

Duration : 4 days

[DC5] Scheduled Maintenance - DC5 Electrical Inverters System Check

Location : DC5 datacenter

What is done : As part of an annual checks, we will verify the inverters of the electric chains in the DC5 data center. This intervention take 4 days and will be supervised by our control office.

Impact : none, it is an electrical check

Start : 10-Nov-2020
End : 13-Nov-2020

Duration : 4 days

Tuesday 10/11 Wednesday 12/11 morning Wednesday 12/11 afternoon Thursday 13/11

[DC3] Scheduled maintenance - electrical system check

Location : DC3 datacenter

What is done : As part of an annual checks, we will verify the electrical installations on all the electrical component in the DC3 data center. This intervention take 8 days and will be supervised by our control office.

Impact : none, it is an electrical check

Start : 16-Nov-2020 0630Z 0830LT

Duration : 1 week

[DC3] Scheduled maintenance - circulation pumps

Location : DC3 datacenter

What is done : As part of an annual checks, we will verify the circulation pumps installations in the DC3 data center. This intervention take 2 days and will be supervised by our control office.

Impact : none, it is an electrical check

Start : 18-Oct-2020 0700Z 0900LT

Duration : 2 days

[DC3] Scheduled Maintenance - DC3 Thermography

As part of an annual checks, we are going to carry out a thermography in the DC3 datacenter.

This intervention take 6 days and will be supervised by our control office.

Start : 23-Nov-2020 0730Z 0830LT

Duration : 6 days

[DC3] Pressurization maintenance

We will realized a pressurizationmaintenance on substation SSA, SSB and SSC.

  • Sub station C, 03/12-Sub station A & B, 02/12
  • Sub station A & B, 02/12

This maintenance will be carried by our maintainer under our permanent supervision.

Start: 2020-12-02 0830Z (0930LT)
End: 2020-12-03 1600Z (1700LT)
[DC5] Scheduled Maintenance - DC5 Power Generators Preventive Mechanical Maintenance

Location : DC5 datacenter

What is done : As part of an annual checks, we will verify the electrical installations on all the electrical component in the DC5 data center. This intervention take 8 days and will be supervised by our control office.

Impact : LOW Electrical Redundancy Loss

Start : 02Dec-2020
End : 04-Dec-2020

Duration : 3 days

Every evening, the generators on which maintenance are been performed will be put back into service. No group will remain out of service in the absence of the maintainer.

[DC3] Preventive maintenance of CRAC units

We will carry out the semi-annual preventive maintenance of CRAC units according to the schedule below.
CRAC units will be shut down one at a time, so as not to impact the cooling of halls.

Each IT zone has CRAC unit called «backup»: each CRAC unit is doubled.
Each MVLB hall has a main air hanling unit (AHU).

The maintenance will be done according to the following schedule:
• MLV​Bs: 09/12/2020 to 11/12/2020
• Operators halls: 04/12/2020
• IT halls n°4: 07/12/2020 and 10/12/2020
• IT halls n°3: 07/12/2020 and 09/12/2020
• IT halls n°2: 08/12/2020
• IT halls n°1: 08/12/2020

The maximum cut-off time per CRAC unit is otherwise defined at 1 hour.

Impact: Loss of cooling redundancy during the preventive maintenance operation of a CRAC unit (max 1h). No impact on the cooling of facilities.

Supervision of return and blowing temperatures during operation. Interventions mastered by the maintainer with the possibility of returning very quickly in initial configuration in the event of anomaly.

In the event of fault not immediately correctible and impacting the operation of the “backup” CRAC unit associated with the CRAC unit in maintenance, the maintainer will restart the CRAC unit in maintenance very quickly. If necessary, CRAC units adjacent to the faulty zone may be switched to degraded (forced) operation.

Start: 2020-12-04 0730Z (0830LT)
End: 2020-12-11 1730Z (1830LT)

Duration: 6 business days

Past Incidents

Thursday 29th October 2020

[DC5] Scheduled maintenance Room 1 - Racks A47, A48, A49, A50, A53, scheduled 1 day ago

A scheduled maintenance is planned in DC5 (Room 1 - A47, A48, A49, A50, A53) in order to optimize and upgrade our infrastructure.

It will be done gradually on the racks, in the same order as in the object of the maintenance.

As a result servers will lose their public network connectivity as our switches are being upgraded, but private network connectivity will still be functional. It will come back gradually following the scheduled upgrades. We estimate the downtime to be between 20 and 30 minutes.

Updates will be posted below as the maintenance is going on.

Start : October 29th, 2020 - 05:00 UTC

Duration : 2 hours

29.10.2020 0700Z (0800LT)

The maintenance has been correctly and successfully performed.

Wednesday 28th October 2020

[DC5] Scheduled maintenance Room 1 - Racks A41, A42, A44, A45, A46, scheduled 2 days ago

A scheduled maintenance is planned in DC5 (Room 1 - A41, A42, A44, A45, A46) in order to optimize and upgrade our infrastructure.

It will be done gradually on the racks, in the same order as in the object of the maintenance.

As a result servers will lose their public network connectivity as our switches are being upgraded, but private network connectivity will still be functional. It will come back gradually following the scheduled upgrades. We estimate the downtime to be between 20 and 30 minutes.

Updates will be posted below as the maintenance is going on.

Start : October 28th, 2020 - 05:00 UTC

Duration : 2 hours

Wednesday 21st October 2020

[DC5] Scheduled maintenance Room 1 - Racks A33, A34, A36, A37, A40, scheduled 1 week ago

A scheduled maintenance is planned in DC5 (Room 1 - A33, A34, A36, A37, A40) in order to optimize and upgrade our infrastructure.

It will be done gradually on the racks, in the same order as in the object of the maintenance.

As a result servers will lose their public network connectivity as our switches are being upgraded, but private network connectivity will still be functional. It will come back gradually following the scheduled upgrades. We estimate the downtime to be between 20 and 30 minutes.

Updates will be posted below as the maintenance is going on.

Start : October 21st, 2020 - 05:00 UTC

Duration : 2 hours

Sunday 11th October 2020

No incidents reported

Saturday 10th October 2020

IPv6 issues

IPv6 connectivity is currently facing an issue related to our DHCP servers in Paris for Dédibox. The issue has been escalated to our local team.

===================

10.10.20 1900Z (2100LT)

Issue has been resolved by our team. Please contact us if you still encounter issues with IPv6.

10.10.20 1730Z (1930LT)

Issue has been escalated to local team

Instances DEV1 hypervisor down

We currently are experiencing an issue with a specific hypervisor hosting DEV1 instances.
Instances on it are either unreachable or stuck in a transient state.

As of now, we do not have a quick solution to release/archive volumes to our distant storage in order to allow users to restart their instances on another physical node.
We will update this status as soon as we have additional details.

===================

10/10/20 1630Z (1830LT)

Issue has been fixed, hypervisor is now available again.

10/10/20 0930Z (1130LT)

Issue has been escalated to product team.
We will share additional details as soon as possible.

Friday 9th October 2020

No incidents reported

Thursday 8th October 2020

No incidents reported

Wednesday 7th October 2020

DC5 Network [DC5 Network] Room 1Rack A27

RPN device in room 1 rack A27 has been detected as not operational at 0501Z and regained function at 0507Z.

===================

07/10/20 0501Z (0701LT)

RPN device anomaly detected

07/10/20 0507Z (0707LT)

Issue has been solved by the local team

Tuesday 6th October 2020

SAN [SAN] RPN SAN HA reboot

We have found an issue on one of the server of a SAN HA (san-ssd-2.rpn.online.net) that requires an emergency reboot to apply a fix.

As this is HA, there will only be a micro cut as we switch to another server and the SAN HA will be available again.

Do not hesitate to contact us should you experience any issue longer than that.

DC5 Load shaving tests

[Load shaving tests]

As part of the load shaving commissioning onthe Datacenter, we will proceed to a test of operation on Low voltage master boards LT1.1 and LT1.2.The operation includes the sending of a load shaving order from the energy providerand the transfer of loads of LVMB LT1.1 and LT1.2 to generators.Our staffwill be mobilized for the perfect workflowof the operations

Location : DC5

Impact : This intervention does not present any particular risk of service interruption and will be processed on worked hours.

Start : 06-Oct-2020 0800Z 100LT
End : 06-Oct-2020 1200Z 1400LT

Duration : 4 hours

Hosting [WEBHOSTING] Hardware issue

We are currently facing an hardware issue with our webhosting plateform, causing some websites unavailable
The root cause has been identified.
We will update this status as soon as we have more information to share.

===================

06/10/2020 0700Z (0900LT)

The product team has identified the root cause and working on a fix

Monday 5th October 2020

[Webhosting] FTP Access unavailable

We are currently experiencing issues with our webhosting FTP access. Some FTP accounts might be unreachable for the time being. We are currently investigating on the situation.

===================

11.05.2020 0500Z (0700LT)
10.05.2020 1945Z (2145LT)

Issue has been escalated to local team

Instances [ELEMENTS] Paris- Hyperviseur Unreachable

We have identified a hardware issue with one of our hypervisor. Impacted instances are unreachable, administrative actions (stop, reboot, etc) are not properly executed, resulting in the instance getting stuck.

===================

10.05.20 0800Z (1000LT)

Issue has been fixed

10.05.20 0530Z (0730LT)

Issue has been escalated to our local team