Belpak / Beltelecom contact to address a BGP hijacking issue?

Anurag Bhatia me at anuragbhatia.com
Mon Oct 29 18:03:56 UTC 2012


Hello Sarah


Seems like they are not advertising it anymore. AS6697 has transit from
Level3 and peering/transit from HE. Both of them show path to AS3215 for
that prefix now.


http://lookingglass.level3.net/


BGP query on all sites seems OK for now.


Also same on results from Oregon as well as HE. Infact HE is taking 1299
5511 3215 ...way longer then direct 6697 if existed. Surely they were
getting wrong announcement as per http://bgp.he.net/net/2.2.2.0/24 - which
is updated once in 24hrs.


So likely issue resolved?




On Mon, Oct 29, 2012 at 3:24 PM, Sarah Nataf <sarah.nataf at gmail.com> wrote:

> Hi all,
>
> Does anyone have a technical or peering contact at Belpak / Beltelecom
> (AS 66697) to address
> an apparent netblock hijacking issue?
>
> AS6697 is advertising the 2.2.2.0/24 address space which is under
> AS3215 management.
> We've tried to announce the same prefix but it's difficult to get the
> traffic back!
>
> No answer from people listed in the whois, no peeringDB information.
> Any suggestions?
>
> Thanks in advance,
> --
> sarah
>
>


-- 

Anurag Bhatia
anuragbhatia.com

Linkedin <http://in.linkedin.com/in/anuragbhatia21> |
Twitter<https://twitter.com/anurag_bhatia>|
Google+ <https://plus.google.com/118280168625121532854>


More information about the NANOG mailing list