Hi I know that is not related with RIPE atlas, but maybe do know where to report in RIPE BGP hijacking topic?
From today BGP table:
46.0.0.0/8 xx 33 6939 5541 I 77.0.0.0/8 xxx 33 6939 5541 I 89.0.0.0/8 xxx 33 6939 5541 I 91.0.0.0/8 xxx 33 6939 5541 I 94.0.0.0/8 xxx 33 6939 5541 I 95.0.0.0/8 xxx 33 6939 5541 I
On Fri, Dec 20, 2013 at 11:59:13AM +0100, Lukasz Trabinski <lukasz@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>
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@nic.fr>
On Fri, Dec 20, 2013 at 11:59:13AM +0100, Lukasz Trabinski <lukasz@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>
Hi again. Well. It seems to be fixed. 2013/12/20 Łukasz Trąbiński <lukasz@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@nic.fr>
On Fri, Dec 20, 2013 at 11:59:13AM +0100, Lukasz Trabinski <lukasz@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>
On 12/20/13 12:37 PM, Stephane Bortzmeyer wrote:
On Fri, Dec 20, 2013 at 11:59:13AM +0100, Lukasz Trabinski <lukasz@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?).
They are visible in the BGPlay widget. For example https://stat.ripe.net/widget/bgplay#w.resource=46.0.0.0%2F8 First announced yesterday at 23:00 UTC. Seen by in total 120 peers on 13 RIS route collectors. The RIPEstat at-a-glance page, https://stat.ripe.net/46/8#tabId=at-a-glance , does not show them yet because the backend powering those widgets does not have the most recent data. As the warning in the prefix-overview and routing-status widgets says, the data there is at this moment 35 hours old. We are working on replacing that backend system by one which process the RIS data more timely. In near future the delays will be much shorter. -- Rene
Neither does the looking glass of the upstream <http://bgp.he.net/AS5541#_prefixes>
participants (4)
-
Lukasz Trabinski -
Rene Wilhelm -
Stephane Bortzmeyer -
Łukasz Trąbiński