Packet Loss and higher ping for Sofia, Bulgaria - (SOF)

Hello,

I am noticing higher pings from the 1.1.1.1 DNS Resolver and some packet loss while the location for “Sofia, Bulgaria - (SOF)” is being re-routed.

Is there any way to know when “Sofia, Bulgaria - (SOF)” will be in status Operational or if there is any maintenance going there?

Note: I asked few other people and they can confirm that the issue occurs but on some other providers in Sofia/Bulgaria works kinda ok with around 10ms.

Here are some quick MTR, tracepath and ping outputs:

2022-10-15T15:28:33+0300
Keys: Help Display mode Restart statistics Order of fields quit
Packets Pings
Host Loss% Snt Last Avg Best Wrst StDev

  1. OpenWrt.lan 0.0% 36 2.0 2.3 1.4 5.0 0.7
  2. 192.168.100.1 8.3% 36 4.7 4.0 2.0 5.5 0.9
  3. 78-83-112-2.spectrumnet.bg 0.0% 36 9.7 6.8 3.5 17.6 3.1
  4. (waiting for reply)
  5. sfia-b2-link.ip.twelve99.net 54.3% 36 7.0 5.9 4.3 7.0 0.9
  6. win-bb4-link.ip.twelve99.net 0.0% 36 23.3 21.7 19.5 24.4 1.1
  7. win-b2-link.ip.twelve99.net 2.9% 35 23.0 23.2 22.4 23.8 0.4
  8. cloudflare-svc070292-ic356168.ip.twelve99-cust.net 2.9% 35 20.0 24.0 20.0 41.4 6.3
  9. one.one.one.one 2.9% 35 19.4 20.1 19.3 21.0 0.5

tracepath:

❯ tracepath 1.1.1.1
1?: [LOCALHOST] pmtu 1500
1: OpenWrt.lan 4.700ms
1: OpenWrt.lan 1.524ms
2: 192.168.100.1 2.832ms
3: no reply
4: no reply
5: sfia-b2-link.ip.twelve99.net 5.119ms
6: win-bb3-link.ip.twelve99.net 25.400ms
7: win-b2-link.ip.twelve99.net 25.282ms
8: no reply
9: no reply
10: no reply
11: no reply
12: no reply
13: no reply
14: no reply
15: no reply

ping:

❯ ping 1.1.1.1
PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
64 bytes from 1.1.1.1: icmp_seq=1 ttl=57 time=20.4 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=57 time=21.1 ms
64 bytes from 1.1.1.1: icmp_seq=3 ttl=57 time=20.9 ms
64 bytes from 1.1.1.1: icmp_seq=4 ttl=57 time=21.3 ms
64 bytes from 1.1.1.1: icmp_seq=5 ttl=57 time=19.3 ms
64 bytes from 1.1.1.1: icmp_seq=6 ttl=57 time=19.7 ms
64 bytes from 1.1.1.1: icmp_seq=7 ttl=57 time=22.0 ms
64 bytes from 1.1.1.1: icmp_seq=8 ttl=57 time=20.5 ms
64 bytes from 1.1.1.1: icmp_seq=9 ttl=57 time=21.3 ms
64 bytes from 1.1.1.1: icmp_seq=10 ttl=57 time=21.7 ms
64 bytes from 1.1.1.1: icmp_seq=11 ttl=57 time=19.9 ms
64 bytes from 1.1.1.1: icmp_seq=12 ttl=57 time=22.1 ms

The issue was resolved on 2022-10-21 around 16:20 UTC+3.

Thanks Cloudflare team!