said by Greg73:I am having tons of issues with packet loss and high latency ...
How have you determined that you have packet loss? Your trace is only demonstrating high latency.
Since I can trace to the same destination with roughly normal latency for my distance ...
C:\util\dig>tracert 50.120.254.18
Tracing route to 50.120.254.18 over a maximum of 30 hops
1 <1 ms <1 ms 2 ms Chihiro [192.168.102.1]
2 30 ms 31 ms 32 ms 173-228-7-1.dsl.static.sonic.net [173.228.7.1]
3 30 ms 32 ms 30 ms gig1-4.cr1.lsatca11.sonic.net [70.36.243.13]
4 30 ms 30 ms 31 ms 0.xe-5-1-0.gw.pao1.sonic.net [69.12.211.1]
5 32 ms 32 ms 31 ms xe-1-0-6.ar1.pao1.us.nlayer.net [69.22.130.85]
6 31 ms 30 ms 30 ms ae0-90g.cr1.pao1.us.nlayer.net [69.22.153.18]
7 31 ms 31 ms 73 ms pao.paix.frontiernet.net [198.32.176.27]
8 104 ms 115 ms 104 ms ae2---0.cor02.plal.ca.frontiernet.net [74.40.3.169]
9 106 ms 106 ms 119 ms ae1---0.cor01.slkc.ut.frontiernet.net [74.40.5.62]
10 107 ms 108 ms 106 ms ae3---0.cor02.chcg.il.frontiernet.net [74.40.5.57]
11 87 ms 88 ms 87 ms ge--7-0-0---0.car01.chcg.il.frontiernet.net [74.40.3.238]
12 105 ms 106 ms 105 ms 74.40.5.214
13 107 ms 106 ms 107 ms 74.44.241.82
14 117 ms 114 ms 114 ms 50.120.254.1
15 115 ms 115 ms 116 ms 50.120.254.18
Trace complete.
... I would concur that XO Communications is likely a bottleneck. But I don't know the relationship between them, so have no idea for contacts. Since you are not a direct customer of XO Communications, they likely don't want to talk with you; if Frontier is buying transit from XO, you would have to find a way to escalate from Frontier Tier 1 support.