OVH Travaux http://status.ovh.net/ Thu, 20 Jun 2013 11:32:36 +0200 Private Cloud:: FS#8824 — SSL Gateways update These maintenance works will affect the vClouds and vSpheres.

During the maintenance period we expect that vSphere access will be down for 5 minutes.

VMs will be not affected.]]> Task Type: Maintenance

Category: Backend / Core

Status: Finished


An SSL Gateways update will be carried out on the night of 19/06 and 20/06 at 23:30.
These maintenance works will affect the vClouds and vSpheres.

During the maintenance period we expect that vSphere access will be down for 5 minutes.

VMs will be not affected.

Comments:

Date: Thu, 20 Jun 2013 07:32:52 +0200

We started maintenance.

Date: Thu, 20 Jun 2013 07:33:41 +0200

Maintenance is in progress, everything is running smoothly. We have updated 45% of GW SSL.

Date: Thu, 20 Jun 2013 07:33:59 +0200

Maintenance is in progress, everything is running smoothly. We have updated 60% of GW SSL.

Date: Thu, 20 Jun 2013 07:34:18 +0200

Maintenance is in progress, everything is running smoothly. We have updated 80% of GW SSL.

Date: Thu, 20 Jun 2013 11:32:12 +0200

We are starting the BHS updates.

]]> Thu, 20 Jun 2013 11:32:36 +0200 http://status.ovh.net/?do=details&id=4895 http://status.ovh.net/?do=details&id=4895 Datacenter:: FS#8836 — Maintenance inverters UPS12 in progress]]> Task Type: Maintenance

Category: Roubaix 1

Status: In progress


We are currently carrying out preventative maintenance works on the inverters.
UPS12 in progress]]> Thu, 20 Jun 2013 11:30:19 +0200 http://status.ovh.net/?do=details&id=4906 http://status.ovh.net/?do=details&id=4906 Network:: FS#8835 — Fiber Roubaix <> TH2 All circuits are switched automatically to protection at 10:46 pm.]]> Task Type: Maintenance

Category: the whole network

Status: In progress


The fiber Roubaix &lt;&gt; TH2 is currently under maintenance (work on the cable planned).
All circuits are switched automatically to protection at 10:46 pm.]]> Wed, 19 Jun 2013 23:47:58 +0200 http://status.ovh.net/?do=details&id=4905 http://status.ovh.net/?do=details&id=4905 Dedicated servers:: FS#8810 — ftpback-rbx4-96.ovh.net Task Type: Incident

Category: Associated service

Status: Finished


The server is no longer accessible, we are rebooting it.

Comments:

Date: Mon, 17 Jun 2013 11:27:58 +0200

Several disks are showing signs of weakness on this server. In order to guarantee the security of your data, we are passing the server into read-only mode. We will return it to read-write mode once the situation has stablised.

]]> Wed, 19 Jun 2013 18:33:33 +0200 http://status.ovh.net/?do=details&id=4880 http://status.ovh.net/?do=details&id=4880 Network:: FS#8834 — NTT (AS2914) Paris between OVH and NTT at Paris TH2.]]> Task Type: Maintenance

Category: the whole network

Status: In progress


We are going to set up a 10G link
between OVH and NTT at Paris TH2.]]> Wed, 19 Jun 2013 17:31:51 +0200 http://status.ovh.net/?do=details&id=4904 http://status.ovh.net/?do=details&id=4904 Dedicated servers:: FS#8773 — Switch port The intervention will commence on Monday June 10th at 9:30am Montreal time (15:30 in FR).
A few seconds of downtime are expected on the servers connected to these switches that we intervene on.
We will start with the switch ports corresponding to the server range 192.95.24.0.1-48.]]> Task Type: Modernization

Category: Beauharnois

Status: Finished


We are going to update the Canada switch port configuration to reduce the impact of DoS attacks on the servers connected to these switches.
The intervention will commence on Monday June 10th at 9:30am Montreal time (15:30 in FR).
A few seconds of downtime are expected on the servers connected to these switches that we intervene on.
We will start with the switch ports corresponding to the server range 192.95.24.0.1-48.

Comments:

Date: Mon, 10 Jun 2013 15:55:49 +0200

We are starting the operation on switch connected to the servers range of ip 192.95.24.1-48.

Date: Mon, 10 Jun 2013 16:11:07 +0200

Done for today, we will continue with the rest of the 192.95.24.0/24 network at the same time tomorrow.

Date: Tue, 11 Jun 2013 15:39:08 +0200

We are starting again with the rest of network 192.95.24.0/24

Date: Tue, 11 Jun 2013 16:52:52 +0200

Done for today, we will continue at the same time tomorrow with the following networks: 192.95.25.0/24 192.95.26.0/24 192.95.27.0/24

Date: Wed, 12 Jun 2013 16:34:54 +0200

Today we are moving onto: 192.95.25.0/24 192.95.26.0/24 192.95.27.0/24

Date: Wed, 12 Jun 2013 18:16:47 +0200

Done, we will move onto the following networks tomorrow from 3pm: 198.27.64.0/24 198.27.65.0/24 198.27.66.0/24 198.27.67.0/24 198.27.68.0/24 198.27.69.0/24 198.27.70.0/24 198.27.71.0/24

Date: Thu, 13 Jun 2013 15:57:32 +0200

We are starting on: 198.27.64.0/24 198.27.65.0/24 198.27.66.0/24 198.27.67.0/24 198.27.68.0/24 198.27.69.0/24 198.27.70.0/24 198.27.71.0/24

Date: Thu, 13 Jun 2013 16:12:33 +0200

Done: 198.27.64.0/24 198.27.65.0/24 198.27.66.0/24 Doing: 198.27.67.0/24 198.27.68.0/24 198.27.69.0/24

Date: Thu, 13 Jun 2013 17:31:16 +0200

Done: 198.27.67.0/24 198.27.68.0/24 198.27.69.0/24 Doing: 198.27.70.0/24 198.27.71.0/24

Date: Fri, 14 Jun 2013 00:15:12 +0200

Done: 198.27.70.0/24 198.27.71.0/24 Done for today, we'll resume on Monday.

Date: Tue, 18 Jun 2013 12:40:46 +0200

We finally resume this afternoon from 15:00, with the following networks: 192.95.29.0/24 192.95.30.0/24 192.95.31.0/24 142.4.208.0/24 142.4.209.0/24 198.100.145.0/24 198.100.146.0/24 198.100.147.0/24 198.100.148.0/24 198.100.149.0/24

Date: Tue, 18 Jun 2013 15:05:54 +0200

doing: 192.95.29.0/24 192.95.30.0/24 192.95.31.0/24 142.4.208.0/24 142.4.209.0/24

Date: Tue, 18 Jun 2013 16:37:45 +0200

doing: 192.95.29.0/24 192.95.30.0/24 192.95.31.0/24 142.4.208.0/24 142.4.209.0/24

Date: Tue, 18 Jun 2013 17:27:52 +0200

done: 192.95.29.0/24 192.95.30.0/24 192.95.31.0/24 142.4.208.0/24 142.4.209.0/24 doing: 198.100.145.0/24 198.100.146.0/24 198.100.147.0/24 198.100.148.0/24 198.100.149.0/24

Date: Tue, 18 Jun 2013 18:49:57 +0200

We will continue tomorrow from 10:00 French time, with the following networks: 198.27.80.0/24 198.27.81.0/24 198.27.82.0/24 198.27.83.0/24 198.245.49.0/24 198.245.50.0/24 198.245.51.0/24 198.245.60.0/24 198.245.61.0/24 198.245.62.0/24 198.245.63.0/24 142.4.210.0/24 142.4.211.0/24 142.4.212.0/24 142.4.213.0/24 142.4.214.0/24 142.4.215.0/24 198.100.144.0/24

Date: Wed, 19 Jun 2013 09:56:34 +0200

doing: 198.27.80.0/24 198.27.81.0/24 198.27.82.0/24 198.27.83.0/24

Date: Wed, 19 Jun 2013 11:31:41 +0200

done: 198.27.80.0/24 198.27.81.0/24 198.27.82.0/24 198.27.83.0/24 doing: 198.245.49.0/24 198.245.50.0/24 198.245.51.0/24 198.100.144.0/24

Date: Wed, 19 Jun 2013 13:32:14 +0200

done: 198.245.49.0/24 198.245.50.0/24 198.245.51.0/24 198.100.144.0/24 We will continue this pm

Date: Wed, 19 Jun 2013 15:49:50 +0200

doing: 198.245.60.0/24 198.245.61.0/24 198.245.62.0/24 198.245.63.0/24 142.4.210.0/24

Date: Wed, 19 Jun 2013 16:55:36 +0200

done: 198.245.60.0/24 198.245.61.0/24 198.245.62.0/24 198.245.63.0/24 142.4.210.0/24 doing: 142.4.211.0/24 142.4.212.0/24 142.4.213.0/24 142.4.214.0/24 142.4.215.0/24

Date: Wed, 19 Jun 2013 16:59:21 +0200

done: 142.4.211.0/24 142.4.212.0/24 142.4.213.0/24 142.4.214.0/24 142.4.215.0/24 all deployments are finished

]]> Wed, 19 Jun 2013 16:59:34 +0200 http://status.ovh.net/?do=details&id=4842 http://status.ovh.net/?do=details&id=4842 Network:: FS#8833 — hold-queue bhs-1/2-6k Task Type: Modernization

Category: Beauharnois

Status: In progress


We are changing the hold-queue setting on bhs-1/2-6k in order to make the configuration uniform with the other DC routers.]]> Wed, 19 Jun 2013 16:57:39 +0200 http://status.ovh.net/?do=details&id=4903 http://status.ovh.net/?do=details&id=4903 Private Cloud:: FS#8803 — Veeam beta deployment Installation and configuration of Veeam will not affect production:
- A virtual machine will be deployed on your Pcc automatically.
- Once this machine is deployed and configured, you can take advantage of the offer via the &quot;Backup Management&quot; tab in the datacentre and the &quot;Backup Management&quot; option in the virtual machine contextual menu. A relaunch of the client vSphere will be required.]]> Task Type: Modernization

Category: Backend / Core

Status: Finished


We are launching automatic installation of Veeam beta for those who have requested it on the mailing list.
Installation and configuration of Veeam will not affect production:
- A virtual machine will be deployed on your Pcc automatically.
- Once this machine is deployed and configured, you can take advantage of the offer via the &quot;Backup Management&quot; tab in the datacentre and the &quot;Backup Management&quot; option in the virtual machine contextual menu. A relaunch of the client vSphere will be required.

Comments:

Date: Wed, 19 Jun 2013 16:53:43 +0200

All deployments are now finished.

]]> Wed, 19 Jun 2013 16:53:48 +0200 http://status.ovh.net/?do=details&id=4873 http://status.ovh.net/?do=details&id=4873 Domain names:: FS#8832 — ns.kimsufi.com sdns1.ovh This could generate latency in receiving the zone by secondary DNS.

We are investigating it now to find out the cause of the problem.]]> Task Type: Modernization

Category: DNS Servers

Status: In progress


We have noticed that there is currently a large number of zone transfers pending.
This could generate latency in receiving the zone by secondary DNS.

We are investigating it now to find out the cause of the problem.]]> Wed, 19 Jun 2013 15:49:16 +0200 http://status.ovh.net/?do=details&id=4902 http://status.ovh.net/?do=details&id=4902 Network:: FS#8819 — anti-spam network The idea is to duplicate all the traffic created by customers, going out
through port 25 (smtp) on an anti-spam network, and then to analyse the sample of
emails leaving our network in real time by IP, in order to control
whether the IP sends spam or not.
If we detect an IP that does send spam, the aim is to be able to block the
flow of (only) port 25, in less than 5 seconds after spam is first detected.
All this without affecting the service performance for the customers
that do not spam.

In actual fact, we have far too many spam issues and it isn't enough to shutdown the
servers a few hours after having detected the spam. It's too late.
It must be done in real time and must be able to block the flow in a matter of
seconds. So we are thinking of how to successfully cleanse our network of spammers
(who can order servers like everyone else, in just a few minutes)
]]> Task Type: Maintenance

Category: the whole network

Status: In progress


We are carrying out setup tests on the duplication of outgoing email flow.
The idea is to duplicate all the traffic created by customers, going out
through port 25 (smtp) on an anti-spam network, and then to analyse the sample of
emails leaving our network in real time by IP, in order to control
whether the IP sends spam or not.
If we detect an IP that does send spam, the aim is to be able to block the
flow of (only) port 25, in less than 5 seconds after spam is first detected.
All this without affecting the service performance for the customers
that do not spam.

In actual fact, we have far too many spam issues and it isn't enough to shutdown the
servers a few hours after having detected the spam. It's too late.
It must be done in real time and must be able to block the flow in a matter of
seconds. So we are thinking of how to successfully cleanse our network of spammers
(who can order servers like everyone else, in just a few minutes)

Comments:

Date: Mon, 17 Jun 2013 16:26:39 +0200

The duplication of outgoing smtp flow has been set up. We have 2.5Gbps to analyse in real time.

Date: Wed, 19 Jun 2013 13:37:18 +0200

We are thinking of launching the R&D in a few days, the time it will take to build the server powerful enough to perform all analysis operations locally, then extracting only the stats on the amount of spam by IP.

]]> Wed, 19 Jun 2013 13:33:32 +0200 http://status.ovh.net/?do=details&id=4889 http://status.ovh.net/?do=details&id=4889