All systems are operational

About This Site

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

Scheduled Maintenance
AMS - Upgrade IP transit

We will perform maintenance on our AMS Network. Maintenance window is from 20th August 2019 at 09:30 pm UTC to 20th August 2019 at 11:00 am UTC.

Impact : No impact is expected.

Start : 20-Aug-2019 0730Z 0930LT
END : 20-Aug-2019 0930Z 1130LT
DC3 - Semi-Annual Refrigeration Units Maintenance

We will do the semi-annual maintenance of the chillers.

The operation will have no impact on your equipments housed in our DC

START: Friday 23-Aug-2019 0600Z 0800LT

END: Tueday 03-Sept-2019 1530Z 1730LT

RPN AMS1/DC3

Preventive maintenance over the RPN network between AMS1 and DC3

Network supplier must perform maintenance on his Network. Maintenance window is from September 13, 2019 at 11:00 pm UTC to September 14th, 2019 at 6:00 am UTC. The expected Impact length is 19 hours at the maximum, during the maintenance window

Impact : Downtime on the RPN network between AMS1 and DC3

Start : 13-Sept-2019 2100Z 2300LT

It will last : 19 hours

DC3 - Annual maintenance of UPS

We will do the annual maintenance of the inverters of electrical chains A, B, C and D.

The operation will have no impact on your equipments housed in our DC

START: Monday 16-Sept-2019 0630Z 0830LT Electrical chain A

END: Friday 20-Sept-2019 1530Z 1730LT

RPN AMS1/DC3

Upgrade over the RPN network between AMS1 and DC3

Network supplier must perform maintenance on his Network. Maintenance window is from October 26th, 2019 at 10:00 pm UTC to October 27th, 2019 at 4:00 am UTC. The expected Impact length is 6 hours at the maximum, during the maintenance window

Impact : Downtime on the rpn network between AMS1 and DC3

Start : 26-Oct-2018 2200Z 0000LT

It will last : 6 hours

Past Incidents

Monday 4th February 2019

[RPN] Switch firmware updates, scheduled 6 months ago

[RPN] Switch firmware updates

Starting on February 4th 2019 we will start updating our RPN switch's firmwares. We will update 6 switches each day. As they will be rebooted, a downtime will happen. This will impact only the RPN network, not the public network. A support ticket will be opened in your account to tell you which server is impacted.

The update is a bugfix and adds the possibility to modify VLAN IDs on all RPNv2 groups.

The planning can be found on this link: https://bugs.online.net/index.php?do=details&task_id=1398

Start : 4-Feb-2019 0500Z 0600LT

Duration : 120 minutes

Thursday 31st January 2019

DC3 Electrical outage in S45 - D18

We had an electrical outage around 1700Z in DC3, room 4-5, rack D18.
Issue has now been fixed and services should be back up.

We will keep monitoring electrical stability on this particular rack.

If you are still facing specific issues, please contact our support team by ticket.

Compute Nodes PDS stability issue

We are currently experiencing performance issues on our Persistant Data Store.
As a results, some internal tasks might take longer than usual, and fail in some cases (for example, instance start/stop processes).

We are doing our best to get it fixed as soon as possible.

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

31/01/19 1730Z (1830LT)

Root cause has been identified, PDS are stable again and we are progressively relaunching internal tasks to avoid congestion.
We will update this status when situation is completely back to normal.

31/01/19 2210Z (2310LT)

Issue is fixed, situation is now completely back to normal

Console Identified billing disruption / Perturbation de la procédure de facturation identifiée

We are noticing disruptions on unpaid workflow of Compute instances in December.
Our teams are fully focused on getting it fixed as soon as possible.
Impacted users will directly receive more information by email.


Une perturbation a été détectée dans le traitement des impayés des instances Compute du mois de décembre.
Nos équipes sont entièrement mobilisées pour rétablir la situation.
Nous vous tiendrons informés des évolutions.
Les utilisateurs concernés recevront directement des informations complémentaires par email.

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

23.01.19 0614Z (0714LT)

Impacted customers have been contacted directly by email.
Issue has been resolved, feel free to contact our support team if you have any particular question.

DC3 [DC3] Accident in Room: 4 4-6, Rack: F12.

Hello,

We encountered an issue with switch in DC3, Room: 4 4-6, Rack: F12. Multiple servers may not be available cause of lost connection. We apologise for an inconvenience.

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

01.02.19 0935Z (1035LT)

Our network team fixed the issue and the rack is now available again. If you don't have access to your server yet, do not hesitate to check through KVM or perform a reboot in order to restart the services.

01.02.19 0045Z (0145LT)

Switch was replaced, however further steps have to be performed by our engineers to totally restore connection and make all impacted servers functional again.

31.01.19 0000Z (0100LT)

Issue was escalated to responsible team.

Wednesday 30th January 2019

No incidents reported

Tuesday 29th January 2019

No incidents reported

Monday 28th January 2019

Compute Nodes Servers' tasks getting stuck

Our teams noticed multiple nodes stuck on internal tasks (reboot, stopping, archiving...).
We are currently focused on getting it solved as fast as possible, and will update this status as soon as we have additional details to share.

We are truly sorry for any inconvenience caused.

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

28/01/19 1830Z (1930LT)

The issue has been resolved and servers are now starting/archiving as expected.

28/01/19 1530Z (1630LT)

The product team has identified the root cause and is working on a fix.
We do not have a precise ETA yet, but will update this status asap.

Sunday 27th January 2019

No incidents reported

Saturday 26th January 2019

No incidents reported

Friday 25th January 2019

No incidents reported