Weird Savvis Routing

Has anyone else noticed some weird Savvis routing in the NY/NJ area since their maintenance on Friday night?

I'm in NY and a trace to the NJ1 datacenter in Jersey City NJ shows:

Code:
1 <1 ms <1 ms <1 ms 10.0.0.3
2 24 ms 23 ms 23 ms 10.32.37.1
3 26 ms 24 ms 23 ms at-3-1-1-1732.CORE-RTR1.NY325.verizon-gni.net [1
30.81.11.173]
4 24 ms 24 ms 24 ms 130.81.20.176
5 * 30 ms 30 ms 0.so-3-1-0.XT1.NYC9.ALTER.NET [152.63.10.37]
6 32 ms 75 ms 34 ms 0.so-4-2-0.XL3.NYC4.ALTER.NET [152.63.0.213]
7 32 ms 32 ms 32 ms 0.so-6-2-0.BR1.NYC4.ALTER.NET [152.63.3.149]
8 32 ms 32 ms 32 ms bcs1-so-5-1-0.NewYork.savvis.net [204.70.1.5]
9 34 ms 32 ms 32 ms cr1-pos-0-0-5-2.Washington.savvis.net [204.70.195.1]
10 32 ms 32 ms 32 ms 204.70.197.5
11 33 ms 33 ms 33 ms 204.70.197.14
12 33 ms 32 ms 32 ms hr2-tenge-13-2.Weehawkennj2.savvis.net [216.35.78.6]
13 32 ms 33 ms 32 ms 204.70.196.74
14 33 ms 33 ms 33 ms 204.70.196.78
15 32 ms 32 ms 32 ms bhr2-ge-5-0.JerseyCitynj1.savvis.net [204.70.196.86]
16 33 ms 32 ms 32 ms csr22-ve241.Jerseycitynj1.savvis.net [216.32.223.51]
Why are the packets going from NewYork to Washington to Weehawken and then to Jersey City? Also, what are those 4 unnamed nodes at 10,11, 13 and 14?

I'm also getting 200ms+ ping times and 13% loss to/from our offsite VPSs

Code:
640 packets transmitted, 554 received, 13% packet loss, time 639988ms
rtt min/avg/max/mdev = 192.275/198.945/227.685/3.173 ms, pipe 2

[root@offsite ~]# traceroute 216.32.223.51
1 eqash79.keepitsecure.net (69.65.111.117) 0.173 ms 0.125 ms 0.063 ms
2 r02.iad.defenderhosting.com (69.65.112.2) 3.440 ms 0.345 ms 0.290 ms
3 ge2-10.as.eqxashva.aleron.net (205.198.14.245) 0.473 ms 0.554 ms 0.482 ms
4 ber1-ge-8-10.virginiaequinix.savvis.net (208.173.52.105) 0.591 ms 0.567 ms 0.438 ms
5 cpr2-ge-5-0.virginiaequinix.savvis.net (204.70.193.101) 0.588 ms 0.606 ms *
6 bcs2-so-2-0-0.washington.savvis.net (204.70.193.153) 119.863 ms 3.639 ms 3.378 ms
7 cr1-tengig-0-7-0-0.Washington.savvis.net (204.70.196.105) 198.659 ms 201.783 ms *
8 bcs2-so-2-0-0.NewYork.savvis.net (204.70.192.2) 202.751 ms 195.501 ms *
9 * dcr3-ge-0-2-1.newyork.savvis.net (204.70.193.98) 201.978 ms 198.180 ms
10 204.70.197.5 (204.70.197.5) 7.627 ms 6.984 ms 6.196 ms
11 204.70.197.14 (204.70.197.14) 6.822 ms 6.534 ms 6.460 ms
MPLS Label=1640 CoS=5 TTL=1 S=0
12 hr2-tenge-13-2.Weehawkennj2.savvis.net (216.35.78.6) 6.752 ms 6.634 ms 6.509 ms
MPLS Label=66 CoS=5 TTL=1 S=0
13 204.70.196.74 (204.70.196.74) 7.550 ms 6.600 ms 6.479 ms
MPLS Label=339 CoS=5 TTL=1 S=0
14 204.70.196.78 (204.70.196.78) 6.607 ms 6.633 ms 6.482 ms
MPLS Label=339 CoS=5 TTL=1 S=0
15 bhr2-ge-5-0.JerseyCitynj1.savvis.net (204.70.196.86) 198.841 ms * 201.303 ms
16 csr22-ve241.Jerseycitynj1.savvis.net (216.32.223.51) 196.147 ms * 199.857 ms
The second trace shows that there is a path between New York and Weehawken without going through Washington, even though the first route went through Washington between NY and NJ. The only reason that I can think of is that someone in Washington wants to see the traffic (wink wink)?

I've contacted Savvis, but got the stock response "Savvis’ backbone routers forward traffic through the optimal logical path within our network. Although the physical path may seem odd occasionally, it is actually the optimal path."