Mailing List Archive

On Jun 11, 2009, at 9:34 AM, Hugo Salgado wrote:

> It seems that http://technet.microsoft.com is unreachable from
> several places. Here it resolves to technet.microsoft.akadns.net
> (64.4.11.252), but doesn't answer ping's nor telnet to port 80.
>
> I've tried using several looking glasses, but only
> "downforeveryoneorjustme.com" seems to reach it.
>
> Hugo

Reachable here in Lincoln, Neb. with no issues. I'm thinking
akadns.net is probably Akamai DNS?


-Andy

I'm on AT&T DSL in California - I can access the front page.

Also checked from work - U-Verse & a TelePacific T1 line both can access it.

It could have just been down temporarily.
--------------------------------------------------------------------------------------------------------------------------------------
<EoM>
Thanks,
Andrew T. Davis


On Thu, Jun 11, 2009 at 7:34 AM, Hugo Salgado <hsalgado at nic.cl> wrote:

> It seems that http://technet.microsoft.com is unreachable from
> several places. Here it resolves to technet.microsoft.akadns.net
> (64.4.11.252), but doesn't answer ping's nor telnet to port 80.
>
> I've tried using several looking glasses, but only
> "downforeveryoneorjustme.com" seems to reach it.
>
> Hugo
> _______________________________________________
> outages mailing list
> outages at outages.org
> https://puck.nether.net/mailman/listinfo/outages
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/outages/attachments/20090611/3e9a61b6/attachment.html>

-----Original Message-----
From: outages-bounces@outages.org [mailto:outages-bounces@outages.org]
On Behalf Of Hugo Salgado
Sent: Thursday, June 11, 2009 10:35 AM
To: outages at outages.org
Subject: [outages] technet.microsoft.com

> It seems that http://technet.microsoft.com is unreachable from
> several places. Here it resolves to technet.microsoft.akadns.net
> (64.4.11.252), but doesn't answer ping's nor telnet to port 80.
>
> I've tried using several looking glasses, but only
> "downforeveryoneorjustme.com" seems to reach it.

HTTP looking glass or pings? I have yet to see a Microsoft server that
responds to ICMP. Only reliable method I've found is something like
tcptraceroute.

Working fine here: (am able to view website)

Selected device eth0, address 205.189.48.18, port 2236 for outgoing
packets
Tracing the path to technet.microsoft.com (65.55.11.240) on TCP port 80
(www), 30 hops max
1 central.kingston.net (205.189.48.1) 0.971 ms 0.240 ms 0.223 ms
2 ge-6-11-117.car1.Toronto2.Level3.net (4.59.180.17) 4.361 ms 4.392
ms 4.297 ms
3 ae-11-11.car2.Toronto2.Level3.net (4.69.140.250) 4.185 ms 4.316 ms
4.261 ms
4 ae-2-2.car2.Montreal2.Level3.net (4.69.140.254) 11.187 ms 11.008
ms 11.250 ms
5 ae-11-11.car1.Montreal2.Level3.net (4.69.141.2) 181.748 ms 163.498
ms 196.209 ms
6 ae-5-5.ebr4.NewYork1.Level3.net (4.69.141.6) 47.224 ms 18.095 ms
18.007 ms
7 ae-6-6.ebr2.NewYork2.Level3.net (4.69.141.22) 16.685 ms 18.248 ms
18.623 ms
8 ae-2-52.edge2.NewYork2.Level3.net (4.69.138.227) 18.652 ms 18.058
ms 18.296 ms
9 MICROSOFT-C.edge2.NewYork2.Level3.net (4.71.190.2) 17.230 ms
17.304 ms 17.483 ms
10 ge-3-0-0-0.nyc-64cb-1b.ntwk.msn.net (207.46.47.216) 17.229 ms
17.116 ms 17.040 ms
11 ge-7-0-0-0.nyc-64cb-1a.ntwk.msn.net (207.46.47.20) 16.865 ms
16.531 ms 17.285 ms
12 ge-1-0-0-0.chg-64cb-1b.ntwk.msn.net (207.46.41.197) 39.865 ms
37.221 ms 38.453 ms
13 ge-0-0-0-0.chg-64cb-1a.ntwk.msn.net (207.46.43.150) 38.987 ms
35.787 ms 68.165 ms
14 ge-3-3-0-0.co2-64c-1b.ntwk.msn.net (207.46.43.153) 94.346 ms
73.243 ms 72.156 ms
15 ge-2-0-0-0.co1-64c-1b.ntwk.msn.net (207.46.43.178) 70.327 ms
69.872 ms 73.127 ms
16 10.22.8.58 70.835 ms 71.907 ms 73.112 ms
17 65.55.11.240 [open] 69.688 ms 73.720 ms 71.274 ms



Cheers
---
Ross Halliday
Network Operations
WTC Communications

Office: 613-547-6939 x203
Helpdesk: 866-547-6939 option 2
http://www.wtccommunications.ca

On Jun 11, 2009, at 9:09 AM, Ross Halliday wrote:

> -----Original Message-----
> From: outages-bounces at outages.org [mailto:outages-bounces at outages.org]
> On Behalf Of Hugo Salgado
> Sent: Thursday, June 11, 2009 10:35 AM
> To: outages at outages.org
> Subject: [outages] technet.microsoft.com
>
>> It seems that http://technet.microsoft.com is unreachable from
>> several places. Here it resolves to technet.microsoft.akadns.net
>> (64.4.11.252), but doesn't answer ping's nor telnet to port 80.
>>
>> I've tried using several looking glasses, but only
>> "downforeveryoneorjustme.com" seems to reach it.
>
> HTTP looking glass or pings? I have yet to see a Microsoft server that
> responds to ICMP. Only reliable method I've found is something like
> tcptraceroute.


$ ping netops.hotmail.com
PING netops.hotmail.com (216.32.183.201): 56 data bytes
64 bytes from 216.32.183.201: icmp_seq=0 ttl=243 time=19.860 ms
64 bytes from 216.32.183.201: icmp_seq=1 ttl=243 time=33.384 ms
64 bytes from 216.32.183.201: icmp_seq=2 ttl=243 time=20.344 ms

Ross Halliday wrote:
> -----Original Message-----
> From: outages-bounces at outages.org [mailto:outages-bounces at outages.org]
> On Behalf Of Hugo Salgado
> Sent: Thursday, June 11, 2009 10:35 AM
> To: outages at outages.org
> Subject: [outages] technet.microsoft.com
>
>> It seems that http://technet.microsoft.com is unreachable from
>> several places. Here it resolves to technet.microsoft.akadns.net
>> (64.4.11.252), but doesn't answer ping's nor telnet to port 80.
>>
>> I've tried using several looking glasses, but only
>> "downforeveryoneorjustme.com" seems to reach it.
>
> HTTP looking glass or pings? I have yet to see a Microsoft server that
> responds to ICMP. Only reliable method I've found is something like
> tcptraceroute.
>

Thanks. I did only pings with the looking glasses.

Anyway, it's back now. Thanks for your help.

Hugo


> Working fine here: (am able to view website)
>
> Selected device eth0, address 205.189.48.18, port 2236 for outgoing
> packets
> Tracing the path to technet.microsoft.com (65.55.11.240) on TCP port 80
> (www), 30 hops max
> 1 central.kingston.net (205.189.48.1) 0.971 ms 0.240 ms 0.223 ms
> 2 ge-6-11-117.car1.Toronto2.Level3.net (4.59.180.17) 4.361 ms 4.392
> ms 4.297 ms
> 3 ae-11-11.car2.Toronto2.Level3.net (4.69.140.250) 4.185 ms 4.316 ms
> 4.261 ms
> 4 ae-2-2.car2.Montreal2.Level3.net (4.69.140.254) 11.187 ms 11.008
> ms 11.250 ms
> 5 ae-11-11.car1.Montreal2.Level3.net (4.69.141.2) 181.748 ms 163.498
> ms 196.209 ms
> 6 ae-5-5.ebr4.NewYork1.Level3.net (4.69.141.6) 47.224 ms 18.095 ms
> 18.007 ms
> 7 ae-6-6.ebr2.NewYork2.Level3.net (4.69.141.22) 16.685 ms 18.248 ms
> 18.623 ms
> 8 ae-2-52.edge2.NewYork2.Level3.net (4.69.138.227) 18.652 ms 18.058
> ms 18.296 ms
> 9 MICROSOFT-C.edge2.NewYork2.Level3.net (4.71.190.2) 17.230 ms
> 17.304 ms 17.483 ms
> 10 ge-3-0-0-0.nyc-64cb-1b.ntwk.msn.net (207.46.47.216) 17.229 ms
> 17.116 ms 17.040 ms
> 11 ge-7-0-0-0.nyc-64cb-1a.ntwk.msn.net (207.46.47.20) 16.865 ms
> 16.531 ms 17.285 ms
> 12 ge-1-0-0-0.chg-64cb-1b.ntwk.msn.net (207.46.41.197) 39.865 ms
> 37.221 ms 38.453 ms
> 13 ge-0-0-0-0.chg-64cb-1a.ntwk.msn.net (207.46.43.150) 38.987 ms
> 35.787 ms 68.165 ms
> 14 ge-3-3-0-0.co2-64c-1b.ntwk.msn.net (207.46.43.153) 94.346 ms
> 73.243 ms 72.156 ms
> 15 ge-2-0-0-0.co1-64c-1b.ntwk.msn.net (207.46.43.178) 70.327 ms
> 69.872 ms 73.127 ms
> 16 10.22.8.58 70.835 ms 71.907 ms 73.112 ms
> 17 65.55.11.240 [open] 69.688 ms 73.720 ms 71.274 ms
>
>
>
> Cheers
> ---
> Ross Halliday
> Network Operations
> WTC Communications
>
> Office: 613-547-6939 x203
> Helpdesk: 866-547-6939 option 2
> http://www.wtccommunications.ca
>