[154354] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: FYI Netflix is down

daemon@ATHENA.MIT.EDU (James Downs)
Mon Jul 2 19:05:09 2012

From: James Downs <egon@egon.cc>
In-Reply-To: <alpine.BSF.2.00.1207021618330.95272@murf.icantclick.org>
Date: Mon, 2 Jul 2012 16:03:58 -0700
To: david raistrick <drais@icantclick.org>
Cc: Nanog <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org


On Jul 2, 2012, at 1:20 PM, david raistrick wrote:

> Amazon resources are controlled (from a consumer viewpoint) by API - =
that API is also used by amazon's internal toolkits that support ELB =
(and RDS..).   Those (http accessed) API interfaces were unavailable for =
a good portion of the outages.

Right, and other toolkits like boto. Each AZ has a different endpoint =
(url), and as I have no resources running in East, I saw no problems =
with the API endpoints I use. So, as you note, US-EAST Region was "not =
controllable".

> I know nothing of the netflix side of it - but that's what -we- saw. =
(and that caused all us-east RDS instances in every AZ to appear=20


And, if you lose US-EAST, you need to run *somewhere*. Netflix did not =
cutover www.netflix.com to another Region. Why not is another question.

-j=


home help back first fref pref prev next nref lref last post