Optimal European DC?

Question

Data center

There is a need to rent 2-3 servers in European DCs with the most stable channel.
There is a sad experience with fastVPS at a DC in Falkestein, Germany, which have constant problems with Rostelecom traffic, and not only.
We need European servers that operate efficiently and stably under medium load conditions with domestic traffic and minimal ping.
+ stable and responsive tech. support
+ low ping
+ maximum uptime
Alternatively, load balancing between one Russian server and one or two European ones is possible.

Answer 1

Um, what are those problems? Hetzner has several data centers, perhaps your server just ended up in some one that Rostelecom does not like. Checked for luck, no losses:
traceroute 78.46.72.239
traceroute to 78.46.72.239 (78.46.72.239), 30 hops max, 60 byte packets
3 * mtk-105-lag-91.msk.ip.ncnet.ru (77.37.254.198 ) 10.053 ms 10.397 ms
4 m10-cr01-be4-91.msk.ip.ncnet.ru (77.37.254.197) 11.561 ms 11.954 ms 12.313 ms
5 ae-9.m10-ar4.msk.ip.rostelecom.ru (94.25 .14.17) 10.911 MS 12.683 MS 13.055 MS
6 188.254.78.123 (188.254.78.123) 54.531 MS 47.209 MS 95.167.95.39 (95.167.95.39) 48.239 MS
7 GW-RESTELECOM.Hetzner.de (213.1333.253) 45.415 MS 51.951 MS 45.745 ms
8 Core1.hetzner.de (213.239.245.6) 79.890 MS 79.877 MS 79.864 MS
9 Core22.hetzner.de (213.239.245.178) 79.761 MS 79.809 MS 79.796 MS
10 Juniper2.rz12.hetzner.de (213.239.245.118) 55.583 MS 64.217 ms 65.826 ms 11
hos-tr3.ex3k4.rz12.hetzner.de (213.239.228.197)
.your-server.de (78.46.72.239) 51.730 ms 68.988 ms 66.331 ms
And so, alas, you have to check everything. Here's a live web in Germany:
traceroute 46.165.221.209
traceroute to 46.165.221.209 (46.165.221.209), 30 hops max, 60 byte packets
3 * mtk-105-lag-91.msk.ip.ncnet.ru (77.37.254.198) 10.035ms 10.375ms
4 m10-cr01-be4-91.msk.ip.ncnet.ru (77.37.254.197) 13.261ms 13.263ms 13.254ms
5 ae-9.m10-ar4.msk.ip.rostelecom.ru (94.25.14.17) 13.215ms 13.207 ms 13.158 ms
6 xe-10-2-0.frkt-ar2.intl.ip.rostelecom.ru (87.226.133.242) 53.982 ms xe-10-2-2.frkt-ar2.intl.ip.rostelecom.ru (87.226.133.238) 44.426 ms 95.167.95.3 (95.167.95.3)
50.042
ms hv3.dtb.peering-inx.fra.leaseweb.net (46.165.255.159) 96.777ms
9 46.165.221.209 (46.165.221.209) 52.978ms xe-1-1-2.peering-inx.fra.leaseweb.net (46.165 .255.120) 73.330 ms 126.030 ms (here the server itself slows down, apparently under heavy traffic)
but Holland:
traceroute to 62.212.66.9 (62.212.66.9), 30 hops max, 60 byte packets
3 * mtk-105-lag-91.msk.ip.ncnet.ru (77.37.254.198) 10.097 ms 10.462 ms
4 -91.msk.ip.ncnet.ru (77.37.254.197) 11.460 ms 11.466 ms 11.790 ms
5
.95.3 (95.167.95.3) 57.510 ms xe-10-2-2.frkt-ar2.intl.ip.rostelecom.ru (87.226.133.238) 44.203 ms 188.254.78.149 (188.254.78.149) 51.510 8 ms
7 * * * 7 * * *
ms po80.sr2.evo.leaseweb.net (62.212.80.74) 60.272 ms 61.905 ms 59.760 ms
9 hosted-by.leaseweb.com (62.212.66.9) 71.695 ms ms hosted-by.leaseweb.com (62.212.66.9) 64.600 ms
and here is luxembourg:
traceroute 94.242.216.77
traceroute to 94.242.216.77 (94.242.216.77), 30 hops max, 60 byte packets
3 * mtk-105-lag-91.msk.ip.ncnet.ru (77.37.254.198) 10.359 ms 10.701 ms
4 m -cr01-be4-91.msk.ip.ncnet.ru (77.37.254.197) 11.245ms 11.665ms 12.689ms
5 ae-9.m10-ar4.msk.ip.rostelecom.ru (94.25.14.17) 12.148ms 13.075ms *
6 188.254.44.182 (188.254.44.182) 104.572 MS 95.167.95.3 (95.167.95.3) 54.234 MS 95.167.92.66 (95.167.92.66) 54.687 MS
7 79.133.94.218 (79.13.94.218) 49.560 MS 48.910 MS 53.421 MS
8 TE1 2.r2.lux.iptransit.com (199.59.206.130) 167.899 ms 167.968 ms te2-2.r2.lux.iptransit.com (204.26.60.46) 163.059
ms ) 84.960ms 60.133ms 64.183ms
10 ip-static-94-242-216-77.as5577.net (94.242.216.77) 63.292 ms 65.597 ms 60.084 ms

Answer 2

I can help with m10. This is the Rostelecom building in Moscow time.

Answer 3

serious dc?