OVHcloud Network Status
Current status
Legend
- Operational
- Degraded performance
- Partial Outage
- Major Outage
- Under maintenance
FS#11865 — p19-72-a10 -- p19-77-a10
Scheduled Maintenance
Report for Network & Infrastructure
Completed
Following an unsuitability in network equipment on the front end of
shared hosting, manager and ovh sites. * we were
forced to restart both machines.
Update(s):
Date: 2014-10-22 19:38:48 UTC
The problem came from an involuntary adjacency on a clan whose traffic was not meant for shared hosting.
The route on the switch was double (once each), around one application out of two arrived at destination. The other's access was rejected, which explains the sites sporadic errors on shared hosting.
The situation is restored and the service is operational again.
Date: 2014-10-22 15:30:03 UTC
We see frequent changes of states (flaps) in the
internal network monitoring equipment.
This is resulting in sporadic delays being seed on
all clusters.
We are continuing our diagnostic.
Date: 2014-10-22 10:45:24 UTC
Cluster002 has also been rerouted, the situation is stabilizing.
Date: 2014-10-22 10:34:46 UTC
cluster002 is also affected, we will intervene.
Date: 2014-10-22 10:34:13 UTC
The reboot was made, we continue to experience difficulties accessing cluster006.
This one was rerouted to another entry point of the network.
Date: 2014-10-22 10:33:08 UTC
We will begin by p19-77-a10.
shared hosting, manager and ovh sites. * we were
forced to restart both machines.
Update(s):
Date: 2014-10-22 19:38:48 UTC
The problem came from an involuntary adjacency on a clan whose traffic was not meant for shared hosting.
The route on the switch was double (once each), around one application out of two arrived at destination. The other's access was rejected, which explains the sites sporadic errors on shared hosting.
The situation is restored and the service is operational again.
Date: 2014-10-22 15:30:03 UTC
We see frequent changes of states (flaps) in the
internal network monitoring equipment.
This is resulting in sporadic delays being seed on
all clusters.
We are continuing our diagnostic.
Date: 2014-10-22 10:45:24 UTC
Cluster002 has also been rerouted, the situation is stabilizing.
Date: 2014-10-22 10:34:46 UTC
cluster002 is also affected, we will intervene.
Date: 2014-10-22 10:34:13 UTC
The reboot was made, we continue to experience difficulties accessing cluster006.
This one was rerouted to another entry point of the network.
Date: 2014-10-22 10:33:08 UTC
We will begin by p19-77-a10.