...
11 49 ms 49 ms 49 ms dcr2-so-1-3-0.dallas.savvis.net [204.70.192.250]
12 49 ms 49 ms 49 ms cr2-tengige0-7-5-0.dallas.savvis.net [204.70.196.29]
13 49 ms 49 ms 49 ms dpr1-ge-4-0-0.dallasequinix.savvis.net [204.70.196.30]
14 49 ms 52 ms 49 ms aer1-ge-3-4.dallasequinix.savvis.net [204.70.194.34 ]
15 44 ms 43 ms 43 ms ge4-17.cer02.dal01.dallas-border.com [208.175.175.58]
16 46 ms 43 ms 44 ms po54.fcr02.dal01.dallas-datacenter.com [66.228.118.174]
17 43 ms 45 ms 43 ms 75.126.252.86-static.reverse.softlayer.com [75.126.252.86]
but when accessing from one of our remote offices these are the results:
...
7 236 ms 242 ms 236 ms p64-1-0-0.r21.dllstx09.us.bb.gin.ntt.net [ 129.250.3.153]
8 239 ms 239 ms 240 ms po-3.r03.dllstx09.us.bb.gin.ntt.net [129.250.4.182]
9 242 ms 240 ms 249 ms te7-1.cer01.dal01.dallas-border.com [157.238.228.10]
10 343 ms 465 ms 323 ms po53.fcr02.dal01.dallas-datacenter.com [66.228.118.166]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
Any thoughts as to why this is happening? At first we thought this was the local providers issue, but as you can see we are getting into Dallas without issue. Things seem to stop in the Dallas Data Center.
