FW: Savvis broken link / underperforming between DC and Atlanta?

Wed Nov 16 05:21:05 UTC 2011

All:

I did not see a reply to this.  Anyone else having a problem on this link?

Lorell

From: Lorell Hathcock [mailto:lorell at hathcock.org] 
Sent: Friday, November 11, 2011 9:10 AM
To: nanog at nanog.org
Subject: Savvis broken link / underperforming between DC and Atlanta?

Any one else seeing this?

This was done yesterday from Hawaii.

tracert speedtest.saas.infor.com

  3     5 ms     5 ms     4 ms  ip64-75-240-210.aloha.net [64.75.240.210]

  4     5 ms     5 ms     5 ms  hnl-edge-02.inet.qwest.net [67.129.94.69]

  5     *        *        *     Request timed out.

  6    56 ms    56 ms    56 ms  63-235-40-18.dia.static.qwest.net
[63.235.40.18]

  7    58 ms    58 ms    59 ms  cr1-tenge-0-3-5-0.sanfrancisco.savvis.net
[204.70.200.198]

  8   138 ms   138 ms   138 ms  cr1-bundle-pos2.Washington.savvis.net
[204.70.200.90]

  9   135 ms   136 ms   136 ms  hr1-tengig-2-0-0.sterling2dc2.savvis.net
[204.70.197.74]

10   139 ms   136 ms   137 ms  165.193.78.106

11     *        *        *     Request timed out.

12     *        *        *     Request timed out.

13     *        *        *     Request timed out.

But from Houston it was fine yesterday.   It took a different route.

Today I have the same problem from Houston.

tracert speedtest.saas.infor.com

  4     2 ms     2 ms     2 ms  te4-1.3509.ccr01.iah02.atlas.cogentco.com
[66.28.6.21]

  5     3 ms     2 ms     2 ms  te0-2-0-4.ccr21.iah01.atlas.cogentco.com
[154.54.3.149]

  6     9 ms    10 ms     8 ms  te0-1-0-5.ccr21.dfw01.atlas.cogentco.com
[154.54.2.225]

  7     8 ms     8 ms     8 ms  te7-3.mpd01.dfw03.atlas.cogentco.com
[154.54.6.66]

  8    15 ms     8 ms    12 ms  aer1-ge-4-2.dallasequinix.savvis.net
[208.175.175.5]

  9    17 ms     8 ms    15 ms  204.70.207.182

10    10 ms     9 ms    10 ms  cr1-tengig0-7-5-0.Dallas.savvis.net
[204.70.200.170]

11    37 ms    37 ms    37 ms  cr1-tengig-0-7-0-0.Washington.savvis.net
[204.70.196.105]

12    36 ms    36 ms    36 ms  hr1-tengig-2-0-0.sterling2dc2.savvis.net
[204.70.197.74]

13    37 ms    36 ms    37 ms  165.193.78.106

14     *        *        *     Request timed out.

15     *        *        *     Request timed out.

16     *        *        *     Request timed out.

This the end IP address is in Rackspace in Atlanta I am told.  Known issues
out there?  Any de-peering going on?  Or is this just a firewall or private
IP space that is not responding to traceroute information requests?

Thanks for any help,

Lorell Hathcock