nanog mailing list archives

Re: Level 3's side of the story


From: Daniel Karrenberg <daniel.karrenberg () ripe net>
Date: Mon, 17 Oct 2005 10:38:49 +0200


On 16.10 16:04, Simon Leinen wrote:

Kevin Loch writes:
Does anyone have reachability data for c-root during this episode?

The RIPE NCC "DNSMON" service has some:

http://dnsmon.ripe.net/dns-servmon/server/plot?server=c.root-servers.net&type=drops&tstart=1128246543&tstop=1128972253

If there is anyone with more comprehensive  data I'd like to hear about it ;-) !

According to BGPlay for that particular prefix from Route-Views data
(for some reason the RIPE RIS server used by BGPlay seems to be down
at the moment), the "episode" seems to be between these times (UTC):

It is up now. Of the two routes to c.root-servers.net via Level 3 in that 
data set one stayed up during the period and the other got healed immediateely 
via AS286. It flipped back later.

...

The interval in the URL above starts 72 hours before the start of the
episode and ends 72 hours after its end.  I cannot see any particular
problems that would coincide with the episode, from that set of probes
(RIPE TTM).

I agree that there is nothing really significant here. It is mostly noise.
What one is looking for in these graphs is strong vertical 
patterns.  dnsmon did not detect anything significant concerning
reachability of c.root-servers.net.

As someone else said, partial unreachability of a particular root
nameserver isn't that much of an issue.  

Indeed.

But it's an interesting question nevertheless.

A red instance of a fish from the northern seas ?

Daniel


Current thread: