[170612] in North American Network Operators' Group
Re: BGPMON Alert Questions
daemon@ATHENA.MIT.EDU (Octavio Alvarez)
Wed Apr 2 15:27:40 2014
Date: Wed, 02 Apr 2014 12:08:33 -0700
From: Octavio Alvarez <alvarezp@alvarezp.ods.org>
To: Joseph Jenkins <joe@breathe-underwater.com>,
"nanog@nanog.org" <nanog@nanog.org>
In-Reply-To: <CACUUO4Gc6itVxCQJsEiT_FXAbvm_vSRoQy7o7S1fy_GcrY291Q@mail.gmail.com>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On 02/04/14 11:51, Joseph Jenkins wrote:
> So I setup BGPMON for my prefixes and got an alert about someone in
> Thailand announcing my prefix. Everything looks fine to me and I've
> checked a bunch of different Looking Glasses and everything announcing
> correctly.
>
> I am assuming I should be contacting the provider about their
> misconfiguration and announcing my prefixes and get them to fix it. Any
> other recommendations?
>
> Is there a way I can verify what they are announcing just to make sure they
> are still doing it?
>
> Here is the alert for reference:
>
> Your prefix: 8.37.93.0/24:
>
> Update time: 2014-04-02 18:26 (UTC)
>
> Detected by #peers: 2
>
> Detected prefix: 8.37.93.0/24
>
> Announced by: AS4761 (INDOSAT-INP-AP INDOSAT Internet Network
> Provider,ID)
>
> Upstream AS: AS4651 (THAI-GATEWAY The Communications Authority of
> Thailand(CAT),TH)
>
> ASpath: 18356 9931 4651 4761
>
Same here. I got an alert for two prefixes. Same origin AS, same AS path
for one of them: 18356 9931 4651 4761, but a different one for the
other: 18356 38794 4651 4761.
