[97830] in North American Network Operators' Group

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

Level(3) faux paux

daemon@ATHENA.MIT.EDU (Security Admin (NetSec))
Thu Jul 12 01:58:45 2007

From: "Security Admin (NetSec)" <secadmin@netsecdesign.com>
To: "nanog@merit.edu" <nanog@merit.edu>
Date: Wed, 11 Jul 2007 22:56:32 -0700
Errors-To: owner-nanog@merit.edu


This is a multipart message in MIME format,
containing the original message body
and a footer added by BitDefender

--=-bd-boundary-xO9Y9Hwb5rdHpynI
Content-Type: multipart/alternative;
	boundary="_000_8D870AB38C30EC4C848A11A3F83D20D8060A3EF41Aexchange2007m_"

--_000_8D870AB38C30EC4C848A11A3F83D20D8060A3EF41Aexchange2007m_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I have noticed that Level(3) misconfigs/outages seem to happen more frequen=
tly than with most other Tier 1's.  Am unsure whether or not this is a mis-=
statement, but based on NANOG posts, Level(3) [AS3356] seems to show up mor=
e often with issues than say Sprint [AS1239].  Is their any one (or any cop=
oration) that keeps track of outages such as these?  Would think it might b=
e a good thing to know for proper mulit-homing relationships to minimize th=
e type of outage that Yahoo faced...

SecAdmin (aka Edward Ray)

--_000_8D870AB38C30EC4C848A11A3F83D20D8060A3EF41Aexchange2007m_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal>I have noticed that Level(3) misconfigs/outages seem t=
o
happen more frequently than with most other Tier 1&#8217;s.&nbsp; Am unsure
whether or not this is a mis-statement, but based on NANOG posts, Level(3) =
[AS3356]
seems to show up more often with issues than say Sprint [AS1239].&nbsp; Is
their any one (or any coporation) that keeps track of outages such as
these?&nbsp; Would think it might be a good thing to know for proper
mulit-homing relationships to minimize the type of outage that Yahoo faced&=
#8230;<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>SecAdmin (aka Edward Ray)<o:p></o:p></p>

</div>

</body>

</html>

--_000_8D870AB38C30EC4C848A11A3F83D20D8060A3EF41Aexchange2007m_--

--=-bd-boundary-xO9Y9Hwb5rdHpynI
Content-Type: text/plain; name="BitDefender.txt"
Content-Disposition: inline; filename="BitDefender.txt"

-- 
This mail was scanned by BitDefender
For more informations please visit http://www.bitdefender.com

--=-bd-boundary-xO9Y9Hwb5rdHpynI--



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