[42499] in North American Network Operators' Group

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

RE: What Worked - What Didn't

daemon@ATHENA.MIT.EDU (Vivien M.)
Mon Sep 17 14:01:02 2001

From: "Vivien M." <vivienm@dyndns.org>
To: <tme@21rst-century.com>
Cc: <nanog@merit.edu>
Date: Mon, 17 Sep 2001 13:57:32 -0400
Message-ID: <NDBBKECCEHKIHGIMJECAMEAHCLAA.vivienm@dyndns.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
In-Reply-To: <3BA63791.A6AB38F3@21rst-century.com>
Errors-To: owner-nanog-outgoing@merit.edu


> -----Original Message-----
> From: owner-nanog@merit.edu [mailto:owner-nanog@merit.edu]On Behalf Of
> Marshall Eubanks
> Sent: September 17, 2001 1:49 PM
> To: Daniel Golding
> Cc: Sean Donelan; nanog@merit.edu
> Subject: Re: What Worked - What Didn't
>=20
> Akamai did not work well Tuesday morning, at least for me. I do=20
> not know whether their servers
> were overloaded, or couldn't get content from the source, but=20
> they did NOT work
> well as seen from here.
>=20
> Washington Post.com, for example, loaded ONCE for me before about=20
> 3:00 PM EDT, and I
> know that site is Akamized.

Washingtonpost.com kept alternating between Akamaized and not Akamaized =
in my experience; I'm guessing that it takes some time for content to =
replicate across Akamai servers, so in the meantime they put the new =
content up locally, and once it was on all the Akamai servers changed =
their links to the Akamaized URL. For some reason though, it seemed that =
_all_ the links changed from Akamaized or not Akamaized and back and so =
on, and not just the new ones. It made for a rather ... odd situation.

Vivien
--=20
Vivien M.
vivienm@dyndns.org
Assistant System Administrator
Dynamic DNS Network Services
http://www.dyndns.org/


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