Hi Corey,
Just a trace from my side, and all seems ok for all sites under discussion (ICMP and UDP - to check the reverse path, use 44.182.21.1). Is it possible that you have different routing/rules on incoming and outgoing connections? Connection tracking could ensure proper responses but initial requests from your side could fail.
Marius, YO2LOJ
C:\Users\Marius>tracert n3fe.ampr.org Tracing route to n3fe.ampr.org [44.56.6.1] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 44.182.20.254 2 160 ms 158 ms 167 ms n3fe.ampr.org [44.56.6.1] Trace complete.
C:\Users\Marius>tracert 44.137.0.1 Tracing route to gw-44-137.ampr.org [44.137.0.1] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 44.182.20.254 2 42 ms 41 ms 42 ms gw-44-137.ampr.org [44.137.0.1] Trace complete.
C:\Users\Marius>tracert 44.137.41.97 Tracing route to linux.pe1chl.ampr.org [44.137.41.97] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 44.182.20.254 2 42 ms 42 ms 42 ms gw-44-137.ampr.org [44.137.0.1] 3 51 ms 51 ms 51 ms pi9noz.pi1utr.ampr.org [44.137.60.2] 4 53 ms 53 ms 53 ms gw.pe1chl.ampr.org [44.137.41.110] 5 52 ms 53 ms 52 ms linux.pe1chl.ampr.org [44.137.41.97] Trace complete.
C:\Users\Marius>tracert 44.88.0.9 Tracing route to n1uro.ampr.org [44.88.0.9] over a maximum of 30 hops: 1 <1 ms 1 ms <1 ms 44.182.20.254 2 158 ms 159 ms 159 ms gw.ct.ampr.org [44.88.0.1] 3 160 ms 159 ms 171 ms n1uro.ampr.org [44.88.0.9] Trace complete.