North American Network Operators Group
Date Prev | Date Next |
Date Index |
Thread Index |
Author Index |
Historical
Re: So -- what did happen to Panix?
- From: Josh Karlin
- Date: Thu Jan 26 18:23:36 2006
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=gB+7v0fkvcS7JhuHmkJ8xc/c3NK3eupNMdx8Lacr7nxbCc7kKekfs6gxDcnccnqldWYz5fiD7g3k2F9ofOl/wyjZbJrzFUSjGuSejwvdX+eyP2v24IzO1weGtmASrktnEyaky2WsTgPzaOxUqtRDuRO+VKMsIH03XGCKJWflwpc=
The noise of origin changes is fairly heavy, somewhere in the low
hundreds of alerts per day given a 3 day history window. Supposing a
falsely originated route was delayed, what is the chance of identifying
and fixing it before the end of the delay period? Do operators
commonly catch misconfigurations on their own or do they usually find
out about it from other operators due to service disruption?
|
