[143182] in North American Network Operators' Group
=?iso-8859-1?Q?RE:_Community_troubleshooting_=E9tiquette/BCP_=28was:_L3_I?=
daemon@ATHENA.MIT.EDU (Scott Berkman)
Mon Aug 1 14:51:50 2011
From: "Scott Berkman" <scott@sberkman.net>
To: "'Jason Lixfeld'" <jason@lixfeld.ca>,
<nanog@nanog.org>
In-Reply-To: <81CCBB29-A43A-4B41-94D9-3E53896B9F7C@lixfeld.ca>
Date: Mon, 1 Aug 2011 14:50:30 -0400
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
I did finally see a Level 3 network event posted about this in their =
portal.
Actually they list two separate ones:
A routing issue failure between Dallas, TX and Los Angeles, CA is =
impacting
IP services. Impacted for: 1 hour 29 minutes =20
A loss of connectivity to servers in Dallas, TX, Tustin, CA, and Tokyo,
Japan caused an impact to CDN services.=20
The second one probably explains the Akamai issues one poster mentioned.
-----Original Message-----
From: Jason Lixfeld [mailto:jason@lixfeld.ca]=20
Sent: Monday, August 01, 2011 2:03 PM
To: nanog@nanog.org
Subject: Community troubleshooting =E9tiquette/BCP (was: L3 Issues)
On 2011-08-01, at 1:48 PM, Jon Lewis wrote:
> Things seem to be moving again.
I happen to have an L3 link out of NYC, but unfortunately I don't have a
list of on-net L3 prefixes in any of the reportedly affected regions, so =
I'm
unable to provide any data from my vantage point up here. I'm sure =
others
are in my position as well.
Is there any sort of etiquette/BCP for reporting issues like this to the
community? Something that might specify a method of providing =
information a
little more specific than just specifying the affected region(s)? Maybe =
a
list of a few affected hosts/prefixes/URLS/etc?
(incidentally, images.apple.com also resolves to our local Akamai =
cluster)
