AboveNet is experiencing a network event.
Unrelated to that issue, can someone from Abovenet engineering with BGP
clue, please contact me off list.
Thanks,
Hank
On Thu, Feb 28, 2008 at 12:28:39PM -0700, Blake Pfankuch wrote:
> AboveNet is experiencing a network event.
Why does that remind me of "rain event" in
http://youtube.com/watch?v=DagVklB4VHQ
http://youtube.com/watch?v=UjKciefHo38
?
:-)
Sorry for off-topic,
best regards,
Daniel
--
CLUE-RIPE --
Hi!
The CIDR Report:
Recent Table History
Date PrefixesCIDR Agg
22-02-08251555 162505
23-02-08251796 163136
24-02-08251963 163643
25-02-08252045 163871
26-02-08252278 159794
27-02-082
On Thu, Feb 28, 2008 at 07:04:21PM -0500, John Dvorak wrote:
> Anyone aware if this is causing any bleedover to Sprint? Seeing massive
> delays
> (~280+ ms) and drops between Relay, MD (144.232.15.2) and San Jose
> (144.232.8.145).
According to AboveNet, the routing instability has a temporary
Anyone aware if this is causing any bleedover to Sprint? Seeing massive delays
(~280+ ms) and drops between Relay, MD (144.232.15.2) and San Jose
(144.232.8.145).
Also seeing same from fort worth (144.232.9.192) to ana (144.232.20.64).
Cisco.com is a good destination to try.
On Thu, 28 Feb 20
I'm seeing everything from Hughes Network (my vsat) go to Portland,
Maine, from Northern Virginia, by way of Nashville, Las Vegas, Los
Angeles (Verizon), and then back to Boston (Alter), for 20 hops. The
usual is 10, straight up the eastern seaboard.
Lots of delay, and more bad dns than usua
his event. AboveNet is currently investigating the issue. Updates
will be made as they become available.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Ross Vandegrift
Sent: Thursday, February 28, 2008 11:54 AM
To: nanog@merit.edu
Subject: AboveNet Global Rout
On Thu, Feb 28, 2008 at 1:54 PM, Ross Vandegrift <[EMAIL PROTECTED]> wrote:
>
> Hi Everyone,
>
> Just received a light-up of calls about general connectivity, a call
> to AboveNet got us the answer that they are having "global routing
> issues".
>
> Has anyone received any more details?
>
Seeing i
Hi Everyone,
Just received a light-up of calls about general connectivity, a call
to AboveNet got us the answer that they are having "global routing
issues".
Has anyone received any more details?
--
Ross Vandegrift
[EMAIL PROTECTED]
"The good Christian should beware of mathematicians, and a
Pekka Savola wrote:
Hi -
TeliaSonera has reported routing problem due to prefix filtering leaks
/ max-prefix triggering, starting around 0616 UTC. I guess some
others are seeing this as well. I wonder what was the more exact
reason, and why the problem still persists after about 6 hours.
On 8/2/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
>
>
> AIX 5.2 and earlier supported it for UDP (we're getting out of the AIX
> business, so I can't speak to what 5.3 does). Basically, it would send
> out a
> gratuitous 64K ICMP Echo Request with DF set, and waited to see what came
> back
On Thu, 02 Aug 2007 18:33:16 PDT, Jim Shankland said:
> Hmm; I've never actually heard of anybody doing PMTUD on non-TCP
> traffic, though it's possible. Does anybody actually do it?
AIX 5.2 and earlier supported it for UDP (we're getting out of the AIX
business, so I can't speak to what 5.3 doe
Adrian Chadd wrote:
On Thu, Aug 02, 2007, Jim Shankland wrote:
Linux has a nifty iptables option (clamp-mss-to-pmtu) to rewrite the
MSS in TCP SYN packets when forwarding a packet onto a link with
a lower MTU than the MSS in the packet. Works like a charm. If every
packet forwarding device o
On Thu, Aug 02, 2007, Jim Shankland wrote:
> Linux has a nifty iptables option (clamp-mss-to-pmtu) to rewrite the
> MSS in TCP SYN packets when forwarding a packet onto a link with
> a lower MTU than the MSS in the packet. Works like a charm. If every
> packet forwarding device on the Internet
Robert Boyle wrote:
Either your firewall/router or the customer's firewall/router is
blocking PMTUD packets. I suspect an overzealous firewall admin
> is blocking all icmp.
Which you can't do anything about if the overzealous firewall admin
is at the other end of the connection. My repea
At 09:30 AM 8/2/2007, Craig D. Rice wrote:
For four months dozens of our users who are Comcast subscribers have
had difficulty reaching St. Olaf College's and Carleton College's
network services.
We have worked through everything we can think of with our Onvoy
(regional ISP) network engineer
On 8/2/07, Craig D. Rice <[EMAIL PROTECTED]> wrote:
> We have already attempted the usual troubleshooting and have eliminated user
> problems, computer problems, server problems, cable modem problems, and
> Linksys router problems. Traceroutes have been somewhat inconclusive since
> Onvoy blocks I
g Comcast Contact: need to troubleshoot packet
> loss and/or asymmetric routing issue between Comcast & Onvoy
>
>
>
> For four months dozens of our users who are Comcast
> subscribers have had difficulty reaching St. Olaf College's
> and Carleton College's n
For four months dozens of our users who are Comcast subscribers have had
difficulty reaching St. Olaf College's and Carleton College's network services.
We have worked through everything we can think of with our Onvoy (regional
ISP) network engineers. We have isolated the problem a couple of
On Jun 28, 2007, at 12:21 PM, Justin Scott wrote:
Good afternoon, is there anyone on the list from Cox communications?
Many of our customers that use Cox in Arizona (Phoenix and Tucson
specifically, 68.15.190.16 is one of the sources) are having trouble
reaching our network in Tampa, FL (64.15
Good afternoon, is there anyone on the list from Cox communications?
Many of our customers that use Cox in Arizona (Phoenix and Tucson
specifically, 68.15.190.16 is one of the sources) are having trouble
reaching our network in Tampa, FL (64.156.29.150 is one address here).
This has been an interm
On 11/29/06, Jim Popovitch <[EMAIL PROTECTED]> wrote:
On Thu, 2006-11-30 at 00:06 -0500, Jim Popovitch wrote:
> Question: What could cause the first trace below to succeed, but the
> second trace to fail?
>
> $ mtr 69.61.40.35
> HOST: blueLoss% Snt Last Avg Best W
On Wed, Nov 29, 2006, Jeremy Chadwick wrote:
> >
> > Taking the 69.61.40.33/28 subnet a bit further, .36 drops at 68.86.84.70
> > but .37 - .39 make it. .40 drops at 68.86.84.70, but .41 makes it.
>
> You're not the only one who noticed this.
Not that its probably it; but i've seen some crapp
Comcast broke themselves doing a maintenance..
On Thu, November 30, 2006 01:59, Jeremy Chadwick wrote:
>
> On Thu, Nov 30, 2006 at 12:06:29AM -0500, Jim Popovitch wrote:
>> $ mtr 69.61.40.34
>> HOST: blueLoss% Snt Last Avg Best Wrst
>> 1. 192.168.3.1
On Thu, Nov 30, 2006 at 12:06:29AM -0500, Jim Popovitch wrote:
> $ mtr 69.61.40.34
> HOST: blueLoss% Snt Last Avg Best Wrst
> 1. 192.168.3.1 0.0% 11.1 1.1 1.1 1.1
> 2. 73.62.48.10.0% 19.9 9.9 9.9
On Thu, Nov 30, 2006 at 12:28:30AM -0500, Jim Popovitch wrote:
>
> On Thu, 2006-11-30 at 00:06 -0500, Jim Popovitch wrote:
> > Question: What could cause the first trace below to succeed, but the
> > second trace to fail?
> >
[snip]
> > Taking the 69.61.40.33/28 subnet a bit further, .36 drops
On Thu, 2006-11-30 at 00:06 -0500, Jim Popovitch wrote:
> Question: What could cause the first trace below to succeed, but the
> second trace to fail?
>
> $ mtr 69.61.40.35
> HOST: blueLoss% Snt Last Avg Best Wrst
> 1. 192.168.3.1 0.0% 1
Question: What could cause the first trace below to succeed, but the
second trace to fail?
$ mtr 69.61.40.35
HOST: blueLoss% Snt Last Avg Best Wrst
1. 192.168.3.1 0.0% 14.3 4.3 4.3 4.3
2. 73.62.48.10.0% 1
Thanks to everyone that replied to my message. I'll contact the NOC
directly.
On Tue, 3 Jan 2006, Joseph W. Breu wrote:
Can someone from Sprint NOC contact me offlist regarding a routing issue?
--
Thanks,
-
Joseph W.
On Tue, 3 Jan 2006, Joseph W. Breu wrote:
>
> Can someone from Sprint NOC contact me offlist regarding a routing issue?
>
one presumes you already tried:
http://puck.nether.net/netops/nocs.cgi?ispname=sprint
and I'm guessing you have a customer contact number since you appear
Can someone from Sprint NOC contact me offlist regarding a routing issue?
--
Thanks,
-
Joseph W. Breu, CCNA phone : +1.319.268.5228
Senior Network Administratorfax : +1.319.266.8158
Cedar Falls Utilities
Hi John,
I just chatted with someone in the SBCIS NRC and discovered the situation
has been resolved. There was a loop in Dallas and they did escalate
properly & resolved it within an hour of notification. Not bad for 6 pm on
the eve of a national holiday
BTW, http://www.sbcbackbone.net is
Thanks to Tom S at SBC for fixing the issue...
john brown
On Wed, Nov 26, 2003 at 03:50:17PM -0700, John Brown (CV) wrote:
>
> seems there is an issue with SPRINT and SBC out of DFW
>
> SBC NS's are unreachable...
>
> Sprint says there is no problem with their gw-39 router.
>
> SBC NOC/N
seems there is an issue with SPRINT and SBC out of DFW
SBC NS's are unreachable...
Sprint says there is no problem with their gw-39 router.
SBC NOC/NRC refused to assist because we aren't their customer.
SBC's customer (BN Railroad) hasn't had any luck thru the normal
customer support channels
Message-
From: Wallace Keith
Sent: Friday, September 19, 2003 4:15 PM
To: [EMAIL PROTECTED]
Subject: routing issue?
Can anyone reach the 38.221.129/24 range?I'm seeing this announced as
a /24 by L3, but looks like it should be a /8 from Cogent(PSI).
Just looking for another view
On Fri, Sep 19, 2003 at 04:15:20AM -0400, [EMAIL PROTECTED] wrote:
>
> Can anyone reach the 38.221.129/24 range?I'm seeing this announced as
> a /24 by L3, but looks like it should be a /8 from Cogent(PSI).
> Just looking for another viewpoint. tnx.
from uunet:
traceroute to 38.221.12
Can anyone reach the 38.221.129/24 range?I'm seeing this announced as
a /24 by L3, but looks like it should be a /8 from Cogent(PSI).
Just looking for another viewpoint. tnx.
Keith
37 matches
Mail list logo
