For as long as I've been with OVH (more than a couple months) there hasn't been any downtime at all until yesterday. Guess the car accident didn't happen in Canada.
May, partial outage, 2 of 3 fibers cut when car hit a pole (the initial reports of a rodent doing it proved to be untrue... ): http://status.ovh.net/?do=details&id=9603
When that fiber cut hit they said the new fiber capacity would be online by September
There is currently a very delicate situation at our datacentre in BHS. We have 4 optical fiber cables that connect the datacenter to the world.1) BHS to Montreal via the North. The link is up and we have 3 pairs of optical fiber cables: to Montreal, New York (600G capacity) and to level 3 (which provides 200G capacity to New York)2) 2) BHS to Montreal via the South. The link is not yet up. Construction of the connection is delayed in the Indian reserve. We will have 3 pairs of optical fiber cables by July 20153) BHS to New York via the South. This link is not yet up either. It takes a particularly long time to get approval to perform work on the Canada/USA border: 3 years. The go-live date: September 20154) A backup of the MTL/BHS backup is UP, but with low capacity (10G).
May, partial outage, 2 of 3 fibers cut when car hit a pole (the initial reports of a rodent doing it proved to be untrue... ): http://status.ovh.net/?do=details&id=9603
When that fiber cut hit they said the new fiber capacity would be online by September
There is currently a very delicate situation at our datacentre in BHS. We have 4 optical fiber cables that connect the datacenter to the world.1) BHS to Montreal via the North. The link is up and we have 3 pairs of optical fiber cables: to Montreal, New York (600G capacity) and to level 3 (which provides 200G capacity to New York)2) 2) BHS to Montreal via the South. The link is not yet up. Construction of the connection is delayed in the Indian reserve. We will have 3 pairs of optical fiber cables by July 20153) BHS to New York via the South. This link is not yet up either. It takes a particularly long time to get approval to perform work on the Canada/USA border: 3 years. The go-live date: September 20154) A backup of the MTL/BHS backup is UP, but with low capacity (10G).
Partial is a relative term. All of the OVH customers I talked to at the time (50+-member Skype chats, forums, IRC) were offline (or at least very highly unstable) for the vast majority of the day.
I guess it didn't effect every server in BHS, then? I've been there since January of this year with no downtime until yesterday, and apparently even that wasn't very severe. Uptime monitoring shows zero downtime throughout the day except for the aforementioned few minutes, which were the result of a 'http/https' test to a specific site. Continuous pings to the host nodes from 7 different confirmation servers claim 100% uptime. I slept through most of it, but didn't wake up to any complaints. I'm guessing the packet loss, once again, only effected certain/specific locations around the world.
Thursday, 28 May 2015, 03:30AM
It's an incident with the cable but not a clear cut. Several fibers are affected but not the whole cable. The problem could be caused by a rodent.