[atlas] BGP hijacking

Hi again.

Well. It seems to be fixed.


2013/12/20 Łukasz Trąbiński <lukasz at trabinski.net>

> from lg.he.net:
>
> core1.fmt1.he.net> show ip bgp routes detail 46.0.0.0/8
> Number of BGP Routes matching display condition : 1
>        S:SUPPRESSED F:FILTERED s:STALE
> 1       Prefix: 46.0.0.0/8,  Status: BI,  Age: 10h37m29s
>          NEXT_HOP: 216.66.87.162, Metric: 1869, Learned from Peer: 216.218.252.169 (6939)
>           LOCAL_PREF: 140,  MED: 20,  ORIGIN: igp,  Weight: 0
>          AS_PATH: 5541
>             COMMUNITIES: 6939:1001 6939:1002 6939:1510 6939:1000
>        Last update to IP routing table: 10h37m29s, 1 path(s) installed:
> # Entry cached for another 60 seconds.
>
>
>
>
>
> 2013/12/20 Stephane Bortzmeyer <bortzmeyer at nic.fr>
>
>> On Fri, Dec 20, 2013 at 11:59:13AM +0100,
>>  Lukasz Trabinski <lukasz at wsisiz.edu.pl> wrote
>>  a message of 20 lines which said:
>>
>> > I know that is not related with RIPE atlas, but maybe do know where
>> > to report in RIPE BGP hijacking topic?
>>
>> Apparently, they did not went too far? RIPE stat does not see them
>> (yet?).
>>
>> Neither does the looking glass of the upstream
>> <http://bgp.he.net/AS5541#_prefixes>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </ripe/mail/archives/ripe-atlas/attachments/20131220/7b2b3bad/attachment.html>