Getting an ISP to fix its routes.

I have a problem with my ISP and routing packets heading to NYC to Virginia before towards Peer1. Im in northern new jersey, and I have seen them route crap to chicago before NAC-OCT. I'm pretty sure its PTD, but they play stupid when I send them emails. Check out these routes

From PTD -> Peer1
----------------------
traceroute to cobra.sonichosting.net (69.90.34.211), 30 hops max, 38 byte
packets
1 192.168.0.2 (192.168.0.2) 3.392 ms 3.297 ms 3.564 ms
2 arc3.spa.ptd.net (10.7.41.5) 37.542 ms 40.026 ms 39.710 ms
3 gateway-e0.spa.ptd.net (204.186.15.254) 39.695 ms 41.384 ms 40.968 ms
4 gateway-f8-0-0-002.sm.ptd.net (204.186.137.30) 39.728 ms 44.545 ms
44.987 ms
5 gateway2-atm5-0-0-317-sm22sm.sm.ptd.net (207.44.124.245) 40.183 ms
47.329 ms 47.509 ms
6 500.POS4-1.GW2.PHL6.ALTER.NET (157.130.43.33) 50.676 ms 50.956 ms
50.992 ms
7 152.63.42.254 (152.63.42.254) 63.161 ms 59.429 ms 53.725 ms
8 0.so-1-1-0.XL2.DCA6.ALTER.NET (152.63.35.122) 50.339 ms 47.633 ms
54.016 ms
9 POS7-0.BR4.DCA6.ALTER.NET (152.63.41.233) 48.636 ms 49.625 ms 47.967
ms
10 208.173.52.117 (208.173.52.117) 51.572 ms 50.175 ms 50.852 ms
11 dcr1-so-6-1-0.Washington.savvis.net (208.173.52.114) 84.935 ms 67.905
ms 64.615 ms
12 dcr1-loopback.NewYork.savvis.net (206.24.194.99) 66.753 ms 70.679 ms
67.580 ms
13 agr4-so-0-0-0.NewYork.savvis.net (206.24.207.62) 64.990 ms
agr4-so-6-0-0.NewYork.savvis.net (206.24.207.206) 66.331 ms
agr3-so-2-0-0.NewYork.savvis.net (206.24.207.186) 69.850 ms
14 acr1-loopback.NewYork.savvis.net (206.24.194.61) 67.233 ms 64.913 ms
74.902 ms
15 206.24.195.134 (206.24.195.134) 63.615 ms 63.313 ms 64.737 ms
16 GIG5-0.nyc-gsr-c.peer1.net (216.187.123.18) 67.007 ms 66.043 ms
65.960 ms
17 OC48POS0-0.nyc-gsr-d.peer1.net (216.187.123.2) 66.708 ms 63.504 ms
65.649 ms
18 nyc-fe3-3b.ne.peer1.net (65.39.204.230) 63.078 ms 65.818 ms 68.207 ms
19 nyc-fe3-3a.ne.peer1.net (65.39.204.238) 67.471 ms 71.243 ms 69.871 ms
20 cobra.sonichosting.net (69.90.34.211) 77.868 ms 75.821 ms 74.311 ms

Peer1->PTD
------------------
traceroute to 204.186.184.107 (204.186.184.107), 30 hops max, 38 byte
packets
1 216.187.123.177 (216.187.123.177) 0.586 ms 0.580 ms 0.542 ms
2 nyc-dis-2.ne.peer1.net (65.39.204.237) 0.951 ms 1.335 ms 0.692 ms
3 12.118.100.17 (12.118.100.17) 1.328 ms 1.239 ms 0.813 ms
4 tbr1-p013802.n54ny.ip.att.net (12.123.3.90) 1.954 ms 2.629 ms 2.517
ms
5 gar1-p310.nw2nj.ip.att.net (12.123.219.130) 2.378 ms 1.028 ms 1.495
ms
6 gateway2-pos1-1.str.ptd.net (12.119.12.70) 22.104 ms 22.524 ms 22.158
ms
7 gateway-atm9-0-0-329-sm2str2.sm.ptd.net (207.44.126.146) 26.358 ms
24.641 ms 26.501 ms
8 gateway-e7.spa.ptd.net (204.186.137.26) 27.583 ms 27.522 ms 27.878 ms
9 arc3-e1.spa.ptd.net (204.186.15.245) 28.142 ms 27.769 ms 29.875 ms
10 * * *


The amount of latency its adding is kind of absurd :/
Any ideas?

 

 

 

 

Top