XO and microsoft.com

Wed Apr 1 20:25:19 UTC 2009

(http://xostats.xo.com/cgi-bin/xostats/diagtool-pub) traceroute from their
Chicago node:
 traceroute 207.46.19.190

 Type escape sequence to abort.
 Tracing the route to 207.46.19.190
 * * *
   1 65.106.2.113 0 msec 0 msec 4 msec
   2 65.106.6.193 0 msec 0 msec 4 msec
   3 65.106.1.42 4 msec 0 msec 4 msec
   4   * * *

and from our location it seems to die there:

 1     1 ms     1 ms     1 ms  10.1.130.1
 2     2 ms     2 ms     1 ms  64.244.80.169
 3     6 ms     5 ms     5 ms  ip65-47-232-113.z232-47-65.customer.algx.net[65
47.232.113]
 4     5 ms     4 ms     5 ms  ge5-2-0-0.mar1.saltlake-ut.us.xo.net[207.88.83.
21]
 5    18 ms    17 ms    60 ms  p4-1-0-0.rar1.denver-co.us.xo.net[65.106.6.85]

 6    18 ms    18 ms    19 ms  p0-0-0d0.rar2.denver-co.us.xo.net[65.106.1.74]

 7    68 ms    50 ms   244 ms  p1-0-0.rar1.chicago-il.us.xo.net[65.106.0.26]
 8    41 ms    41 ms    41 ms  te-3-1-0.rar3.chicago-il.us.xo.net[65.106.1.42]

 9    41 ms    41 ms    41 ms  207.88.13.5.ptr.us.xo.net [207.88.13.5]
10     *        *        *     Request timed out.
11     *        *        *     Request timed out.
12     *        *        *     Request timed out.

On Wed, Apr 1, 2009 at 2:18 PM, ChrisSerafin <chris at chrisserafin.com> wrote:

> I had a ton of problems getting out to MSDN from our data center at
> Chicago/Equinix but our office connection on XO seemed to be fine
>
>
> Sergio D. wrote:
>
>> Anyone going out through XO having problems getting to microsoft.com?
>> This
>> seems to work out our other connections but not XO.
>> Thanks.
>>
>>  ------------------------------------------------------------------------
>>
>>
>> No virus found in this incoming message.
>> Checked by AVG - www.avg.com Version: 8.0.238 / Virus Database:
>> 270.11.35/2034 - Release Date: 04/01/09 06:06:00
>>
>>
>>
>
>

-- 
Sergio Danelli