nanog mailing list archives

Re: BGPMON Alert Questions


From: Adrian Minta <adrian.minta () gmail com>
Date: Thu, 03 Apr 2014 00:26:53 +0300

Already too late :(

*Delivery has failed to these recipients or groups:*

indriana.triyunianingtyas () indosat com <mailto:indriana.triyunianingtyas () indosat com> The recipient's mailbox is full and can't accept messages now. Please try resending this message later, or contact the recipient directly.




On 02.04.2014 23:40, Aris Lambrianidis wrote:
Contacted ip.tac () indosat com about this, I urge others to do the same.

--Aris


On Wed, Apr 2, 2014 at 9:33 PM, Andrew (Andy) Ashley
<andrew.a () aware co th>wrote:

Hi All,

I am a network admin for Aware Corporation AS18356 (Thailand), as
mentioned in the alert.
We operate a BGPMon PeerMon node on our network, which peers with the
BGPMon service as a collector.

It is likely that AS4761 (INDOSAT) has somehow managed to hijack these
prefixes and CAT (Communications Authority of Thailand AS4651) is not
filtering them,
hence they are announced to us and are triggering these BGPMon alerts.

I have had several mails to our NOC about this already and have responded
directly to those.
I suggest contacting Indosat directly to get this resolved.
AS18356 is a stub AS, so we are not actually advertising these learned
hijacked prefixes to anyone but BGPMon for data collection purposes.




--
Best regards,
Adrian Minta



Current thread: