I concur, this is an extremely dangerous slippery slope that ICANN should
refrain. There’s the possibility for misfires, misattribution and
miscalculation that could backfire which is extremely concerning.
—
regards,
/vrode
> On Mar 1, 2022, at 00:56, Matthew Petach wrote:
>
>
>
>
>> On
Hi,
No, that's for changes and updates related to the list. I would stick with w/
outages@ and outages-discussion@ as mentioned below.
outa...@outages.org - Warnings of (un)planned outages and reports of observed
current outages
outages-discuss...@outages.org - Discussion about post outages
(t
Hi -
On 01/19/2011 04:35 PM, Brandon Kim wrote:
Gents:
What measures do you take to protect your border routers? Our routers are
running BGP so I'm interested
if there is any way to secure them without interfering with BGP? Is it normal
to put a firewall in front of the
border routers?
I'm
On 07/31/2011 01:35 PM, Joe Renwick wrote:
Several of my customers in San Diego noticed large drops in traffic at 1pm
today. Note it was not a total loss in connectivity. Anyone else notice
this?
---
Several of our east coat/overseas customers called in about reachability
iss
On 07/31/2011 01:55 PM, Khurram Khan wrote:
Also impacted our POP's out of Houston and San Antonio, TX. We peer
with L3 at both of those locations.
Level3's had a core router failure in their Dallas region that lost
adjacency towards LA region.
regards,
/virendra
On S
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi -
We've been victims of these attacks many a times and more recently
towards our customer dns servers which was rated at ~ 4gbps for a
duration of 30mins.
Tracking the source of an attack is simplified when the source is more
likely to be "valid
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Brings up another question to mind, how many of you have peered using
partial route transit versus having direct peering relationship at the
exchange?
I've personally ran into companies during peering meetings wanting to
sell you their peering relat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 02/23/2012 10:00 AM, Jared Mauch wrote:
>
> On Feb 23, 2012, at 12:39 PM, virendra rode wrote:
>
>> I understand this is not true peering relationship, however its an
>> interesting way to obtain exchange point routes and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Speaking of leaking the world, I remember one of our transit peer during
their nightly maintenance decided they needed people to talk to, so they
decided to share some love by passing ~ 350k routes causing a meltdown.
As lesson learned, we included
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 02/27/2012 08:11 AM, Marshall Eubanks wrote:
> Is anyone seeing this ?
>
> http://www.bbc.co.uk/news/world-africa-17179544
>
> "East Africa's high-speed internet access has been severely disrupted
> after a ship dropped its anchor onto fibre-opt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 03/11/2012 03:57 AM, Peter Losher wrote:
> On Mar 9, 2012, at 10:19 PM, Anurag Bhatia wrote:
>
>> I can see India has 3 root servers hosting root zone - i, j & k in India
>> which is good. So we can resolve the root zone i.e dot within India.
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
On 06/25/2012 10:45 PM, Graham Beneke wrote:
> Hi All
>
> I'm busy doing some digging to find a solution for collecting
> layer-2 flows data on a medium sized IXP. All we have at the moment
> is some MRTG graphs and we're trying to get a better
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
On 07/16/2012 07:36 PM, Bill Woodcock wrote:
>
> On Jul 16, 2012, at 3:23 PM, Jay Hanke wrote:
>
>> After a bit of googling, I found some references to an Internet
>> Exchange in St. Louis, MO called the St. Louis Regional
>> Exchange. Is thi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
What baffles me is that we have external sources reporting the status
as opposed to the provider. In all fairness there's a list of others
right behind.
Their their status page has been static as a sticky bit & sealed
harder than woodpecker lips.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 08/25/2012 11:36 AM, Jason Baugher wrote:
> On 8/24/2012 11:39 PM, Randy Bush wrote:
>>> You mean outages@...
>> chris, this is not productive. outages are a very apt subject
>> for nanog.
>>
> Did anyone ever give any details of the issue? We'r
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 08/27/2012 10:54 AM, Patrick W. Gilmore wrote:
> On Aug 27, 2012, at 12:58, virendra rode
> wrote:
>> On 08/25/2012 11:36 AM, Jason Baugher wrote:
>>> On 8/24/2012 11:39 PM, Randy Bush wrote:
>>>>> You mean
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 08/30/2012 01:10 PM, chris wrote:
> Anyone heard anything about an XO fiber cut in northeast? We have
> had a bunch of issues with some DID's in NJ today and one of our
> carriers forwarded a a vague statement from XO:
>
> *XO Communications is c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 08/31/2012 09:21 AM, bill.ing...@t-systems.com wrote:
> I think having a GRE tunnel for the internal routing protocol is
> unnecessary. Can you explain the reasoning behind this? I
> understand the technical issue whereby GRE will allow multica
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
On 09/04/2012 07:20 AM, Bryn Sadler wrote:
> Many thanks to Jared for jumping on this so quickly off-list, it's
> much appreciated and hopefully we're getting towards a solution
> now.
>
> Bryn
- --
yup you are in good hands, so
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 10/08/2012 12:06 PM, Eric Rosenberry wrote:
> Looks like Sprint is having a very bad day today in the NW?
>
> Anybody able to elaborate on exactly where these fiber cuts are and exactly
> what is impacted? I see mention of several different plac
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 10/31/2012 09:19 AM, Jeff Shultz wrote:
> An online magazine I work with is, we believe, hosted at 75 Broad
> or 111 8th. It dropped out Monday night, right after they announced
> that the diesel pumps had fried due to flooding at 75 Broad, came
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
On 10/30/2012 02:00 PM, Justin Wilson wrote:
> Anyone know of lists, contacts, etc. for companies looking for
> I.T. Folks for help with cleanup and such on the eastern seaboard?
> I am guessing there will be a demand for anyone from cable pulle
Thank you for reaching out.
Will update outages wiki so people can reach admins directly for future
reference.
Sorry for any inconvenience this may have caused.
regards,
outages team
> On Nov 13, 2015, at 7:25 AM, Hugo Slabbert wrote:
>
> The problem seems to have been with mailman. I ping
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
James Jun wrote:
>>> I think what's going on is that packets from www.ietf.org don't make it
>>> back to my ISP. A ping6 or traceroute6 doesn't show any ICMP errors and
>>> TCP sessions don't connect so it's not a PMTUD problem. So it's an
>>> actual
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
shake righa wrote:
> What have been the routing implications in regards to internet traffic
> with SMW4
> cable beign down?
- ---
Latency and slowness then again things are starting to change (mid-2010)
in terms of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/16/2010 09:13 AM, N. Yaakov Ziskind wrote:
> Does anyone have any information (beyond the wimpy statement that
> "technical issues" were to blame) on the Chase outage?
-
- From my understanding their back-end database suffered fr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Joe -
Maybe the middlebox along the path doesn't like tcp window scale
parameter being changed in the midway due to dropped tcp connections or
something. Could be specific to microsoft server. What does your pix
logs show?
Have you tried turning off
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Just wondering if there's any interest in meeting up during nanog 44
(los angeles) and sharing your thoughts, challenges or your outages
experience in general or would like to simply vent and empty your head.
Topics of interest:
* Service provi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Hannigan wrote:
> On Fri, Dec 19, 2008 at 12:17 PM, Suresh Ramasubramanian
> wrote:
>> On Dave Farber's IP list.
>>
>>> From: France Telecom / Press
>>> To: France Telecom / Press
>>> Subject: Three undersea cables cut: traffic greatly dist
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
IMHO, this is exactly what service providers love to hear in order for
them not to be forth coming.
regards,
/virendra
Matthew Petach wrote:
> On 12/28/08, Blake Pfankuch wrote:
>> Any word on the actual cause of the issue?
>
> Given the lurking
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Owen Roth wrote:
> Hello nanog mailing list,
>
> I was curious how one would go about looking for certain types of remote
> hands by geography (ie coaxial runs in Phoenix, AZ). Is there another
> mailing list or a web site that recommends itself?
>
-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
FYI -/
- Original Message
Subject: isotf outtages
Date: Thu, 24 Apr 2008 13:41:42 -0500
From: RVaughn <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
CC: virendra rode // <[EMAIL PROTECTED]>, Gadi Evron
<[EMAIL PROTECTE
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
We are on the final stages of getting the host operational that has
taken longer than we expected. This was a combination of application /
hardware related issue that caused a prolonged outage.
We deeply regret the delay and we should have outage
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Robert Blayzor wrote:
> Does anyone know of any NY fiber cuts going on near/around 60 Hudson
> Street? I have a Level3 DIA Gig-E that's been out for almost 36 hours
> and each time I call them I get a different answer on what the problem
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[ Apologies to those of you who receive this note in multiple forums. ]
Hello all,
I wanted to drop a quick note to everyone and explain how/why things
took so long and I deeply apologize for the service interruption.
Apparently the machine hosting
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jared Mauch wrote:
>
> On May 27, 2008, at 6:47 PM, Jerry Dixon wrote:
>
>> Jared nailed it on the head. It is absolutely critical to get to know
>> who
>> your State JFO POC is, State EOC POC, and have the National Communication
>> Systems Hotline
On Wed, May 28, 2008 at 4:05 PM, Tuc at T-B-O-H.NET <[EMAIL PROTECTED]> wrote:
> Hi,
>
>Sorry, would have posted this elsewhere, but I can't get
> to alot of places...
>
>I originally started chasing not being able to get to
> 71.74.56.243 (RR Mail server). I then found out neither
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tuc at T-B-O-H wrote:
>> On Wed, May 28, 2008 at 4:05 PM, Tuc at T-B-O-H.NET <[EMAIL PROTECTED]>
>> wrote:
>>
>>> Hi,
>>>
>>>Sorry, would have posted this elsewhere, but I can't get
>>> to alot of places...
>>>
>>>I originally started
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Robert E. Seastrom wrote:
> Is anyone else seeing issues with multiple copies and delayed
> originals for SMSes on the AT&T network? I've been seeing this
> behavior for about the past 24-36 hours.
- ---
Some reported sbc outage on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
You may or may not have noticed puck.nether.net (hosting outages.org
mailing list) suffered an outage this am. This was caused due to a file
system issue (possible inconsistence state) on a fairly large (1tb)
filesystem
which caused services on p
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Martin Hannigan wrote:
> On Sat, Jan 9, 2010 at 9:37 AM, Paul Wall wrote:
>
>> On Thu, Jan 7, 2010 at 5:04 AM, Mike
>> wrote:
>>> We just had a qwest outage of about 2 mins at 1:41am pst. When I called
>> to
>>> report it I was told it was a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul,
If my memory serves me correct, Richard presented traceroute presto at
nanog47 that covered location identifiers.
HTH,
regards,
/virendra
Paul Stewart wrote:
> Hi Folks...
>
>
>
> With many changes going on this year in our network, I f
42 matches
Mail list logo
