OVH Travaux http://status.ovh.net/ Wed, 19 Jun 2013 13:40:51 +0200 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: Maintenance

Category: com

Status: Planned


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 13:40:51 +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 ADSL / SDSL:: FS#8826 — Optic loop Hauts-de-Seine (92) Securitisation played its part and the issue has been resolved.
However, an optical signal is damaged, a team is on site to check the
connectors and connections and we have also opened a ticket with the fibre operator.
]]> Task Type: Incident

Category: Backend / Core

Status: Finished


There was an outage of a few seconds on the NRA optic loop in the 92 area.
Securitisation played its part and the issue has been resolved.
However, an optical signal is damaged, a team is on site to check the
connectors and connections and we have also opened a ticket with the fibre operator.

Comments:

Date: Tue, 18 Jun 2013 18:53:22 +0200

We have verfied the optic positions on sites DEF92 and de NAN92, the problem is not on the part that we are responsible for. We have relaunched the optic operator, and a team is on the way in order to carry out some reflectometry test on the fibre optics.

Date: Wed, 19 Jun 2013 11:33:23 +0200

The operator has found the problem on the fibre optic and is starting the works.

Date: Wed, 19 Jun 2013 13:27:00 +0200

Operation terminated, the fibre has been repaired. Securitisation is fully operational again.

]]> Wed, 19 Jun 2013 13:31:17 +0200 http://status.ovh.net/?do=details&id=4896 http://status.ovh.net/?do=details&id=4896 Network:: FS#8805 — bhs-1/2-6k Task Type: Incident

Category: the whole network

Status: Finished


We have an issue with this on these routers which is affecting BHS routing. We are looking into the cause of the problem.

Comments:

Date: Thu, 13 Jun 2013 14:43:43 +0200

The CPU on the 2 routers was found to be very high for a period of 30-40min between 10:20 and 11:00 UTC. Routing towards dedicated servers in BHS1 was affected during this period. This problem is linked to manipulations that were taking place at the time on the switch uplinks of the network 192.95.32. We are verifying the logs but it seems that a L2 loop had formed for a few seconds, which destablised the routers.

]]> Wed, 19 Jun 2013 13:30:40 +0200 http://status.ovh.net/?do=details&id=4875 http://status.ovh.net/?do=details&id=4875 Network:: FS#8828 — LDN/NWK
Traffic is being routed through 10 other transatlantic 10G circuits.

We are contacting our supplier.]]> Task Type: Incident

Category: the whole network

Status: Planned


We currently have 6*10G down between Londres and Newark.

Traffic is being routed through 10 other transatlantic 10G circuits.

We are contacting our supplier.

Comments:

Date: Wed, 19 Jun 2013 13:29:36 +0200

Our supplier has informed us that maintenance works are being carried on their transmission equipment. The circuits will be back up on 23-06-2013 at 23:00:00 GMT.

]]> Wed, 19 Jun 2013 13:29:36 +0200 http://status.ovh.net/?do=details&id=4898 http://status.ovh.net/?do=details&id=4898 Network:: FS#8820 — n5 BHS homogeniser the OVH network infrastructures.]]> Task Type: Maintenance

Category: Beauharnois

Status: Finished


We are going to modify the uplinks configuration in order to
homogeniser the OVH network infrastructures.]]> Wed, 19 Jun 2013 13:06:14 +0200 http://status.ovh.net/?do=details&id=4890 http://status.ovh.net/?do=details&id=4890 Dedicated servers:: FS#8831 — Nas HA 10.16.100.69 Task Type: Maintenance

Category: Associated service

Status: Planned


We have to intervene on the backup pool, we are switching the service onto the slave node.]]> Wed, 19 Jun 2013 11:35:20 +0200 http://status.ovh.net/?do=details&id=4901 http://status.ovh.net/?do=details&id=4901 Dedicated servers:: FS#8802 — nas6.storage.ovh.net Task Type: Incident

Category: Associated service

Status: Finished


The server is unavailable, an intervention is in progress.

Comments:

Date: Thu, 13 Jun 2013 11:09:15 +0200

The service is up again. We are investigating the cause of the failure.

Date: Thu, 13 Jun 2013 12:47:13 +0200

The server is unstable, we are preparing a spare.

Date: Thu, 13 Jun 2013 12:47:50 +0200

The server has been replaced and is operational.

]]> Wed, 19 Jun 2013 11:33:57 +0200 http://status.ovh.net/?do=details&id=4872 http://status.ovh.net/?do=details&id=4872 Network:: FS#8794 — UPC (AS6830) Frankfurt OVH and UPC in Frankfurt, DE.]]> Task Type: Modernization

Category: the whole network

Status: Finished


We are going to set up a 30G link between
OVH and UPC in Frankfurt, DE.

Comments:

Date: Wed, 19 Jun 2013 08:37:29 +0200

It is on prod.

]]> Wed, 19 Jun 2013 08:37:38 +0200 http://status.ovh.net/?do=details&id=4864 http://status.ovh.net/?do=details&id=4864 VoIP:: FS#8830 — Codecs Some modules are on a blocked status.]]> Task Type: Maintenance

Category: Backend / Core

Status: Finished


We reload the DSP voice compression on phone cards.
Some modules are on a blocked status.

Comments:

Date: Wed, 19 Jun 2013 08:33:52 +0200

Reloading all cards was properly done.

]]> Wed, 19 Jun 2013 08:34:34 +0200 http://status.ovh.net/?do=details&id=4900 http://status.ovh.net/?do=details&id=4900