[109473] in North American Network Operators' Group
RE: Sprint Problems?
daemon@ATHENA.MIT.EDU (Mills, Charles)
Mon Nov 24 16:52:04 2008
Date: Mon, 24 Nov 2008 16:51:56 -0500
In-Reply-To: <4D58C7B4943F874BA4CB5D68A79240605FC3FA@Epikserver2.Epik.local>
From: "Mills, Charles" <cmills@accessdc.com>
To: "Ryan Werber" <RWerber@epiknetworks.com>,
"Justin M. Streiner" <streiner@cluebyfour.org>
Cc: nanog@merit.edu
Errors-To: nanog-bounces@nanog.org
Found out from an upstream provider that Sprint might be having some
major backbone issues right now.
A number of their backbone routers are down. This is third hand
information but would seem to make sense considering what we're seeing
here. We dropped our sprint connection until this clears up but
reachability to any site that is on their network or uses them for
transit is iffy at best.
Chuck
-----Original Message-----
From: Ryan Werber [mailto:RWerber@epiknetworks.com]=20
Sent: Monday, November 24, 2008 4:47 PM
To: Justin M. Streiner; Mills, Charles
Cc: nanog@merit.edu
Subject: RE: Sprint Problems?
Hello,
>-----Original Message-----
>From: Justin M. Streiner [mailto:streiner@cluebyfour.org]=20
>Sent: Monday, November 24, 2008 1:42 PM
>On Mon, 24 Nov 2008, Mills, Charles wrote:
>> Anyone seeing or have an insight as to what is going on with Sprint?
>> Connectivity very sporadic. Very high latency.
>Yeah, I'm seeing it here too. Looks like Sprint is advertising routes=20
>that they don't actually have reachability for... Perhaps someone=20
>fat-fingered an access-list?
We had a customer of ours last night complain of unreachability to a
PEER1 (AS13768) route but for some reason Sprint was advertising it.
That route had nothing to do with sprint originally. Packets were
getting thrown around in the Atlanta area until the TTL finally expired.
It seemed to clear it self up last night, but I think we are seeing some
residual damage here.
Ryan Werber
Sr. Network Engineer
Epik Networks (AS 21513)
This e-mail message and any files transmitted with it contain =
confidential information intended only for the person(s) to whom this =
email message is addressed. If you have received this e-mail message in =
error, please notify the sender immediately by telephone or e-mail and =
destroy the original message without making a copy. Thank you.
Neither this information block, the typed name of the sender, nor =
anything else in this message is intended to constitute an electronic =
signature unless a specific statement to the contrary is included in =
this message.
