Re: Amazon?

[Jon R. Kibler]

I am currently in the DC area. It appears that Amazon came up about 20 minutes ago.

SANS ISC has a little info on the problem. Quoting from http://isc.sans.org/diary.php?n&storyid=1625 :
> UPDATE:
>
> Diligent Reader Corwin Grey points out:
>
> "Amazon may be having more than a 'little' trouble. :/ Check out their whois:
>
>
>   Server Name: AMAZON.COM.IS.N0T.AS.1337.AS.WWW.GULLI.COM
>   IP Address: 80.190.192.24
>   Registrar: KEY-SYSTEMS GMBH
>   Whois Server: whois.rrpproxy.net
>   Referral URL: http://www.key-systems.net
>
>  <snip>"
>
> Now, amazon.com looks OK from a whois lookup at www.internic.net (record points to Network Solutions) and from a Network Solutions whois lookup.  But, it looks like we've got some whois database hijinks out there for some of the whois servers and the www.amazon.com info.
>
> Reader Sean points out that these gulli folks do this kind of thing a lot to sites like Amazon.com, Microsoft, and others, and these whois hijinks are likely independent of the back-end problems that Amazon.com appears to be having.  I agree.
>
> I just now checked, and they seem to be back up...  so, intermittent problem fixed?  For now...  It's not the end of the world.
>
> --Ed Skoudis
> Intelguardians



Elijah Savage wrote:
> Thats strange I am not having any issues at all and I have tested it 
> from 3 different peering points.
>
> ----- Original Message -----
> From: Brandon Galbraith <brandon.galbraith@xxxxxxxxx>
> To: Steven M. Bellovin <smb@xxxxxxxxxxxxxxx>
> Cc: Jon R. Kibler <Jon.Kibler@xxxxxxxx>, nanog@xxxxxxxxx
> Sent: Monday, August 21, 2006 3:42:21 PM GMT-0500
> Subject: Re: Amazon?
>
> Intermittent application/load balancer issues perhaps?
>
> -brandon
>
> On 8/21/06, *Steven M. Bellovin* <smb@xxxxxxxxxxxxxxx 
> <mailto:smb@xxxxxxxxxxxxxxx>> wrote:
>
>
>     On Mon, 21 Aug 2006 15:21:40 -0400, "Jon R. Kibler" <
>     Jon.Kibler@xxxxxxxx <mailto:Jon.Kibler@xxxxxxxx>>
>     wrote:
>
>      > Hi,
>      >
>      > Anyone know what is up with Amazon? They appear to be down.
>      >
>      > Doesn't appear to be a network issue... tried from two different
>     ISP's networks.
>      >
>     That's odd.  When I try from one path, I get the same error you get;
>     when
>     I try another, it works.  A tcptraceroute shows that both are ending
>     up at
>     the same IP address at Amazon, too.
>
>                     --Steven M. Bellovin,
>     http://www.cs.columbia.edu/~smb <http://www.cs.columbia.edu/%7Esmb>
>
>
>
>
> --
> Brandon Galbraith
> Email: brandon.galbraith@xxxxxxxxx <mailto:brandon.galbraith@xxxxxxxxx>
> AIM: brandong00
> Voice: 630.400.6992
> "A true pirate starts drinking before the sun hits the yard-arm. Yarrrr. 
> --thelost"
>
>
>
> ==================================================
> Filtered by: TRUSTEM.COM's Email Filtering Service
> http://www.trustem.com/
> No Spam. No Viruses. Just Good Clean Email.

--
Jon R. Kibler
Chief Technical Officer
Advanced Systems Engineering Technology, Inc.
Charleston, SC  USA
(843) 849-8214





==================================================
Filtered by: TRUSTEM.COM's Email Filtering Service
http://www.trustem.com/
No Spam. No Viruses. Just Good Clean Email.