High latency from France

Hello,
I found that recently, the latency from France is much higher than usual despite being routed correctly to CDG. Ping to 1.0.0.1 is 47-ish, while ping to 8.8.8.8 or 8.8.4.4 is only 17-18 ms:
Diagnostic results

Server: one.one.one.one
Address: 1.1.1.1
Non-authoritative answer:
id.server text = “CDG”
Server: one.one.one.one
Address: 1.0.0.1
Non-authoritative answer:
id.server text = “CDG”

Pinging 1.0.0.1 with 32 bytes of data:
Reply from 1.0.0.1: bytes=32 time=47ms TTL=55
Reply from 1.0.0.1: bytes=32 time=46ms TTL=55
Reply from 1.0.0.1: bytes=32 time=47ms TTL=55
Reply from 1.0.0.1: bytes=32 time=46ms TTL=55
Ping statistics for 1.0.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 46ms, Maximum = 47ms, Average = 46ms

Tracing route to one.one.one.one [1.0.0.1]
over a maximum of 30 hops:
1 3 ms 2 ms 2 ms LIVEBOX [192.168.1.1]
2 7 ms 7 ms 7 ms 80.10.236.57
3 10 ms 10 ms 11 ms lag-105.ncpoi102.poitiers.francetelecom.net [193.249.214.134]
4 10 ms 10 ms 10 ms ae41-0.nipoi202.poitiers.francetelecom.net [81.253.130.6]
5 18 ms 22 ms 18 ms 193.252.137.14
6 17 ms 18 ms 17 ms plra.opentransit.net [193.251.151.171]
7 47 ms 46 ms 46 ms ae-26.r04.parsfr01.fr.bb.gin.ntt.net [129.250.66.141]
8 46 ms 46 ms 47 ms ae-3.r03.parsfr02.fr.bb.gin.ntt.net [129.250.5.39]
9 47 ms 157 ms 140 ms 185.84.18.174
10 46 ms 45 ms 47 ms one.one.one.one [1.0.0.1]

Here is ping to Google DNS:

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=18ms TTL=54
Reply from 8.8.8.8: bytes=32 time=18ms TTL=54
Reply from 8.8.8.8: bytes=32 time=18ms TTL=54
Reply from 8.8.8.8: bytes=32 time=18ms TTL=54
Ping statistics for 8.8.8.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 18ms, Maximum = 18ms, Average = 18ms

I’m on Orange (with a Livebox 4) so ping to 1.1.1.1 is like 2-3 ms, but I think it just pings to the modem (this is a known issue of Orange with their Livebox 4). Here is the tracert results just for information (but it has nothing to do with the high latency to 1.0.0.1):

Tracing route to one.one.one.one [1.1.1.1]
over a maximum of 30 hops:
1 3 ms 2 ms 2 ms one.one.one.one [1.1.1.1]
Trace complete.