OVHcloud Network Status
Current status
Legend
- Operational
- Degraded performance
- Partial Outage
- Major Outage
- Under maintenance
FS#10645 — Amsterdam <> Rotterdam
Incident
Report for Network & Infrastructure
Resolved
There is an incident on this section. We don't know if it's related to the outage of last week. The fibre optic is not cut but the signal is severely degraded and the link has become unusable. The circuits switched on the protection via London automatically.
Update(s):
Date: 2014-04-19 06:21:09 UTC
Corrections completed.
Date: 2014-04-17 14:54:59 UTC
The Rotterdam <> Amsterdam link is down again. A team has been sent to the site of the 2nd to set up a new section of the fibre.
As a reminder, there are currently 2 separate incidents on this section of cable. The first occurred last week and was repaired temporarily, and the second happened yesterday afternoon and is currently being repaired.
Date: 2014-04-17 08:04:31 UTC
Update from the cable maintainer:
The repair team found the area of where to break must be. In this area are road works (bicycle tunnel).
Following the drawing our fibers are directly underneath these works and the soil was freshly opened with an excavator.
Unfortunately all soil is now levelled and they cant find any fiber damage. Now they are looking for HH 12 to start measuring the distance by measure wheel.
When they get to the location where the break must be the excavator will start digging and hope to find the break shortly.
Date: 2014-04-17 08:03:17 UTC
The link is up again.
In contrast to the first hypothesis, the problem was not in the same location as last week. It was actually a sharp cut and some strands were more affected than others. We switched the Rotterdam > Amsterdam direction onto a fibre optic that was less affected by the issue and we were able to get the link back up. However, we are still relatively close to the operating limits de fonctionnement and action must be taken to permanently fix the issue.
Date: 2014-04-17 07:55:38 UTC
The problem seems to be linked to the temporary repair carried out last week following the cable being cut. There are still some works in this zone and the cable or one of the casings may have moved, adding some extra dBs on the link. We're working with Level3 on various avenues to resolve the issue until it can be permanently repaired.
Update(s):
Date: 2014-04-19 06:21:09 UTC
Corrections completed.
Date: 2014-04-17 14:54:59 UTC
The Rotterdam <> Amsterdam link is down again. A team has been sent to the site of the 2nd to set up a new section of the fibre.
As a reminder, there are currently 2 separate incidents on this section of cable. The first occurred last week and was repaired temporarily, and the second happened yesterday afternoon and is currently being repaired.
Date: 2014-04-17 08:04:31 UTC
Update from the cable maintainer:
The repair team found the area of where to break must be. In this area are road works (bicycle tunnel).
Following the drawing our fibers are directly underneath these works and the soil was freshly opened with an excavator.
Unfortunately all soil is now levelled and they cant find any fiber damage. Now they are looking for HH 12 to start measuring the distance by measure wheel.
When they get to the location where the break must be the excavator will start digging and hope to find the break shortly.
Date: 2014-04-17 08:03:17 UTC
The link is up again.
In contrast to the first hypothesis, the problem was not in the same location as last week. It was actually a sharp cut and some strands were more affected than others. We switched the Rotterdam > Amsterdam direction onto a fibre optic that was less affected by the issue and we were able to get the link back up. However, we are still relatively close to the operating limits de fonctionnement and action must be taken to permanently fix the issue.
Date: 2014-04-17 07:55:38 UTC
The problem seems to be linked to the temporary repair carried out last week following the cable being cut. There are still some works in this zone and the cable or one of the casings may have moved, adding some extra dBs on the link. We're working with Level3 on various avenues to resolve the issue until it can be permanently repaired.