After 15 years of stable service in Paris 3rd arrondissement, xDSL for 5 years suffers multiple outages. From January 2025 to August 2026, there have been 6 total outages i.e. 55 days ‘down’ for 535 ‘up’, resulting in an availability of only 90% over 590 days. Apart from total outages, the xDSL link was sometimes very poor: pings up to 2 seconds with 50% loss.
The last 2 outages (26 days in June 2025 and 11 days in November 2025) were caused by cuts in the nearby Orange copper line [for example in November at 85 meters] of the DSLAM/Central Office; they were resolved by rotating the remaining pairs in a heavily degraded copper line.
Since July 30, the xDSL service is down: there is no internet, no phone, and no monitoring/security. In my ‘Ticket’, I beg OVH to ask Orange to perform [1] a synchronization test of the DSLAM [2] a ping of the DTI [3] a TDR to locate the fault. Do you have any advice for me?
Unfortunately, we won’t be able to do anything about this outage issue here. I invite you, just like @Gaston, to contact Telecom support at 1007 or via live chat through your customer portal.
The live chat is available 24/7.
The phone line is open Monday to Friday from 8 a.m. to 6 p.m.
My intention was not to criticize OVH: I have the utmost respect for this company and the Klaba family. I only wanted to draw the attention of the OVH‑xDSL community to the degradation — over the past 5 years — of the Orange copper network (‘Orange Copper Plant’) used by OVH‑xDSL for the last mile. In my case, located in the 3rd arrondissement in Paris, the line is 1000 meters long, and was typically interrupted in the first 100 meters from the DSLAM/Central Office.
I had created 2 tickets: the first at the end of July while there was still connectivity but erratic speeds; the second on July 30 after the total outage detected by OVH monitoring ‘Your public IP address XXX.XXX.XXX.XXX is currently not reachable from our monitoring servers as of Thursday, July 30, 2026 at 12:54.’. (Parenthetically: congratulations to OVH for this very effective monitoring).
This last ticket generated a large number of back‑and‑forth messages with OVH support, and quite a bit of frustration. I have just received on August 14 at 7:43 a notice from OVH ‘A local loop intervention has been triggered. Except in exceptional cases, the technician will not need to go to your client’s site. A technician will intervene in the first available slot.’. Thank you to OVH support, and I hope this will resolve the issue (‘I keep my fingers crossed’) and restore connectivity.
Hello OVH,
Probably as a result of the intervention on the Local Loop, connectivity was restored this morning at 10:10 [Paris time] : I received the message‘[OVH-FAI] [UP] Monitoring of your Internet access XXXXXXXXXX : Your public IP address XXX.XXX.XXX.XXX is reachable again from our monitoring servers as of Monday, August 17, 2026 at 10:10.’.
Unfortunately, the connectivity seems to have disappeared a few minutes later: the ping’s to XXX.XXX.XXX.XXX have been failing since. OVH Monitoring has not yet reported ‘[OVH-FAI][DOWN] .
Finally today 19 Aug. at 0:34 I got my 1st successful Ping in 20 days, and I keep my fingers crossed. OVH Monitoring flagged the line as [UP] on Aug. 17 at 10:10, but none of my constant pings could go thought until 2 days later. Between these days 17 and 19, OVH Monitoring did not flag the line as [DOWN] even though the Line was down per my Pings. It tells me that OVH Monitoring is either not working, or badly configured or disabled.
