some feedback on your network peering; it sucks donkey balls. its been like this for atleast the last 9 months if not alot longer

I normally ride the XO backbone which keeps me under 50-60 ping to central servers and 80-90 to west coast servers

Code:
C:\Users\bluree>tracert 69.147.242.84

Tracing route to 69.147.242.84.rdns.ubiquityservers.com [69.147.242.84]
over a maximum of 30 hops:

  1     5 ms     7 ms     8 ms  10.125.192.1
  2     7 ms     7 ms     7 ms  core1-cs.myacc.net [24.233.167.61]
  3     9 ms    13 ms     9 ms  gige-g2-1.core1.mia1.he.net [216.66.23.21]
  4    14 ms    17 ms    17 ms  ge0-2.cr01.mia01.mzima.net [198.32.124.89]
  5    46 ms    52 ms    53 ms  te2-1.cr1.dal1.us.packetexchange.net [69.174.120
.41]
  6    85 ms    88 ms    89 ms  te1-0.cr1.chi1.us.packetexchange.net [69.174.120
.13]
  7    97 ms    87 ms    92 ms  edge1.chi2.ubiquityservers.com [72.37.148.138]
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.

========

C:\Users\bluree>tracert 69.147.242.84

Tracing route to 69.147.242.84.rdns.ubiquityservers.com [69.147.242.84]
over a maximum of 30 hops:

  1     6 ms     7 ms     7 ms  10.125.192.1
  2    19 ms     6 ms     7 ms  core1-cs.myacc.net [24.233.167.61]
  3     9 ms    10 ms     7 ms  gige-g2-1.core1.mia1.he.net [216.66.23.21]
  4    34 ms    18 ms    16 ms  ge0-2.cr01.mia01.mzima.net [198.32.124.89]
  5    54 ms    53 ms    53 ms  te2-1.cr1.dal1.us.packetexchange.net [69.174.12
.41]
  6    85 ms    87 ms    89 ms  te1-0.cr1.chi1.us.packetexchange.net [69.174.12
.13]
  7   202 ms    98 ms    88 ms  edge1.chi2.ubiquityservers.com [72.37.148.138]
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.

hops are all clean till i jump on the packetexchange network inwhich my response times jump nearly 40 from mia to PN then another 30 WITHIN the same facility