BGP path prepend
You should monitor and manage better your BGP announcements so that routing should stay at least on the same continent, example of bad routing bellow:
from a US VPS:
traceroute 176.124.112.100
traceroute to 176.124.112.100 (176.124.112.100), 30 hops max, 60 byte packets
1 192.241.137.1 (192.241.137.1) 0.252 ms 0.257 ms 0.267 ms
2 xe-10-3-3-100.edge3.Newark1.Level3.net (4.28.6.69) 1.664 ms 69.55.60.18 (69.55.60.18) 0.199 ms 0.194 ms
3 nyk-b6-link.telia.net (62.115.34.13) 0.621 ms ae-31-51.ebr1.Newark1.Level3.net (4.69.156.30) 1.502 ms 1.499 ms
4 nyk-bb2-link.telia.net (80.91.254.37) 1.367 ms ae-2-2.ebr1.NewYork1.Level3.net (4.69.132.97) 1.478 ms nyk-bb2-link.telia.net (213.155.133.12) 1.306 ms
5 ae-92-92.csw4.NewYork1.Level3.net (4.69.148.46) 1.345 ms ae-72-72.csw2.NewYork1.Level3.net (4.69.148.38) 1.380 ms nyk-b3-link.telia.net (80.239.147.138) 1.284 ms
6 tmobile-ic-302276-war-b1.c.telia.net (213.248.83.118) 4.211 ms ae-2-70.edge8.NewYork1.Level3.net (4.69.155.79) 1.456 ms ae-3-80.edge8.NewYork1.Level3.net (4.69.155.143) 1.412 ms
7 AS5580.edge3.NewYork1.Level3.net (4.31.24.118) 3.752 ms eth4-3.core1.nyc1.us.atrato.net (78.152.44.201) 1.235 ms AS5580.edge3.NewYork1.Level3.net (4.31.24.118) 1.660 ms
8 eth1-5.core1.lon1.uk.atrato.net (78.152.44.134) 76.830 ms 76.810 ms eth4-3.core1.nyc1.us.atrato.net (78.152.44.201) 1.547 ms
9 eth1-5.core1.lon1.uk.atrato.net (78.152.44.134) 76.718 ms eth1-1.r1.lon2.uk.atrato.net (78.152.44.163) 96.431 ms eth1-5.core1.lon1.uk.atrato.net (78.152.44.134) 76.868 ms
10 78.152.49.70 (78.152.49.70) 84.308 ms eth1-1.r1.lon2.uk.atrato.net (78.152.44.163) 96.376 ms 96.330 ms
11 78.152.49.70 (78.152.49.70) 84.426 ms anycast-uk.moschner.biz (176.58.88.146) 84.672 ms 78.152.49.70 (78.152.49.70) 84.606 ms
12 anycast-uk.moschner.biz (176.58.88.146) 84.618 ms ns1.r4ns.com (176.124.112.100) 74.341 ms 74.301 ms
from a German VPS:
traceroute 176.124.112.100
traceroute to 176.124.112.100 (176.124.112.100), 30 hops max, 60 byte packets
1 enableVPS.com (78.46.49.211) 0.037 ms 0.015 ms 0.014 ms
2 hos-tr3.juniper2.rz11.hetzner.de (213.239.228.65) 0.174 ms 0.155 ms hos-tr4.juniper2.rz11.hetzner.de (213.239.228.97) 0.191 ms
3 core21.hetzner.de (213.239.245.73) 0.204 ms core22.hetzner.de (213.239.245.113) 0.260 ms core21.hetzner.de (213.239.245.73) 0.247 ms
4 core1.hetzner.de (213.239.245.177) 4.803 ms core22.hetzner.de (213.239.245.162) 0.248 ms 0.246 ms
5 juniper1.ffm.hetzner.de (213.239.245.5) 4.852 ms core1.hetzner.de (213.239.245.177) 4.834 ms 4.833 ms
6 dec-ix-c01.wvfiber.net (80.81.192.220) 6.401 ms juniper1.ffm.hetzner.de (213.239.245.5) 4.881 ms 4.879 ms
7 ams-ten1-4-fra-ten2-1.bboi.net (66.216.50.57) 29.732 ms dec-ix-c01.wvfiber.net (80.81.192.220) 6.294 ms 6.615 ms
8 ams-ten1-4-fra-ten2-1.bboi.net (66.216.50.57) 29.673 ms ny60-vl2-ams-vl2.bboi.net (66.216.48.217) 108.555 ms ams-ten1-4-fra-ten2-1.bboi.net (66.216.50.57) 28.789 ms
9 66.216.1.150 (66.216.1.150) 127.656 ms 127.973 ms 127.549 ms
10 66.216.1.150 (66.216.1.150) 127.846 ms 127.815 ms lv-ten1-3-chi-ten1-6.bboi.net (64.127.128.130) 171.990 ms
11 la-ten1-3-lv-ten1-3.bboi.net (66.186.192.21) 177.896 ms 177.871 ms *
12 66.186.197.174 (66.186.197.174) 177.845 ms 177.569 ms 177.556 ms
13 colo-lax6 (96.44.180.102) 177.538 ms 177.797 ms 66.186.197.174 (66.186.197.174) 177.467 ms
14 colo-lax6 (96.44.180.102) 177.627 ms 177.649 ms 177.546 ms
15 lax-qn-gw.as36236.net (72.11.150.122) 177.461 ms 177.444 ms 177.509 ms
16 ns1.r4ns.com (176.124.112.100) 176.572 ms 176.333 ms 208.111.40.5 (208.111.40.5) 176.381 ms
Have a nice day.

-
The issue with NS1 and Layer3 in US is solved now. We are working on the Hetzner routing issue