Custom domain IP changes make posterous faster or slower?

The new rackspace hosted posterous blogs are supposed to be quicker in loading up for web visitors

Ping and traceroute show an interesting latency story when viewing posterous custom domains from Australia.  

OLD IP Ping

Ping statistics for 209.20.70.130:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 261ms, Maximum = 268ms, Average = 263ms

NEW IP Ping

Ping statistics for 184.106.20.102:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 281ms, Maximum = 293ms, Average = 287ms

OLD IP Tracert
Tracing route to 209-20-70-130.slicehost.net [209.20.70.130]
over a maximum of 30 hops:
  1    19 ms    19 ms    19 ms  nexthop.wa.iinet.net.au [203.215.5.244]
  2    35 ms    18 ms    22 ms  te7-1.per-qv1-bdr2.iinet.net.au [203.215.4.36]
  3    75 ms    71 ms    70 ms  xe-3-3-0-0.syd-mas-core1.iinet.net.au [203.215.20.68]
  4    78 ms    78 ms    83 ms  34023.sydp06.cu.reach.com [134.159.160.57]
  5   222 ms   221 ms   293 ms  i-0-0-2-0.paix-core01.bx.reach.com [202.84.140.106]
  6   215 ms   218 ms   218 ms  i-1-2.paix01.bi.reach.com [202.84.251.74]
  7   213 ms   208 ms   209 ms  te4-5.mpd01.sjc04.atlas.cogentco.com [154.54.11.157]
  8   214 ms   223 ms   214 ms  te0-0-0-6.mpd21.sfo01.atlas.cogentco.com [154.54.2.165]
  9   229 ms   217 ms   214 ms  te0-2-0-0.ccr22.sfo01.atlas.cogentco.com [154.54.42.57]
 10   280 ms   254 ms   253 ms  te0-1-0-2.ccr22.mci01.atlas.cogentco.com [154.54.30.70]
 11   263 ms   258 ms   259 ms  te4-3.ccr01.stl03.atlas.cogentco.com [154.54.28.30]
 12   259 ms   279 ms   260 ms  vl3502.na31.b016110-1.stl03.atlas.cogentco.com [66.28.5.58]
 13   258 ms   257 ms   259 ms  38.104.162.58
 14   258 ms   261 ms   257 ms  209-20-79-17.slicehost.net [209.20.79.17]
 15   261 ms   266 ms   263 ms  209-20-70-130.slicehost.net [209.20.70.130]

NEW IP Tracert

Tracing route to custom.posterous.com [184.106.20.102]

over a maximum of 30 hops:

  1    52 ms    32 ms    41 ms  nexthop.wa.iinet.net.au [203.215.XXX.XXX]

  2    36 ms    47 ms    40 ms  te7-1.per-qv1-bdr1.iinet.net.au [203.215.4.18]

  3    71 ms    74 ms   117 ms  xe-3-3-0-0.syd-ult-core1.iinet.net.au [203.215.20.6]

  4    96 ms    97 ms    71 ms  xe-0-1-2-0.syd-mas-core1.iinet.net.au [203.215.20.111]

  5    77 ms    73 ms    74 ms  34023.sydp06.cu.reach.com [134.159.160.57]

  6   225 ms   260 ms   227 ms  i-0-5-0-0.tlot-core01.bx.reach.com [202.84.140.102]

  7   253 ms   246 ms   256 ms  i-2-5.tlot03.bi.reach.com [202.84.251.242]

  8   244 ms   285 ms   248 ms  xe-11-2-0.edge1.losangeles6.level3.net [4.68.62.9]

  9   245 ms   243 ms   258 ms  vlan90.csw4.losangeles1.level3.net [4.69.144.254]

 10     *        *        *     Request timed out.

 11   252 ms   270 ms   257 ms  ae-3-3.ebr3.dallas1.level3.net [4.69.132.78]

 12   251 ms   253 ms   398 ms  4.69.151.169

 13   254 ms   314 ms   258 ms  ae-91-91.ebr1.dallas1.level3.net [4.69.151.162]

 14   316 ms   339 ms   286 ms  ae-14-14.ebr2.chicago2.level3.net [4.69.151.117]

 15   410 ms   285 ms   322 ms  ae-2-52.edge1.chicago2.level3.net [4.69.138.162]

 16   304 ms   303 ms   279 ms  rackspace-m.edge1.chicago2.level3.net [4.71.248.54]

 17   325 ms   308 ms   312 ms  vlan902.guard-6504.ord1.rackspace.net [173.203.0.93]

 18   314 ms   292 ms     *     vlan901.core1.ord1.rackspace.net [173.203.0.62]

 19   286 ms   417 ms   280 ms  173.203.0.217

 20   303 ms   290 ms   287 ms  custom.posterous.com [184.106.20.102]

 

 

Posted

0 comments

Leave a comment...