This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ripe-atlas@ripe.net/
[atlas] BGP hijacking
- Previous message (by thread): [atlas] BGP hijacking
- Next message (by thread): [atlas] BGP hijacking
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Rene Wilhelm
wilhelm at ripe.net
Fri Dec 20 13:00:49 CET 2013
On 12/20/13 12:37 PM, Stephane Bortzmeyer wrote: > 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?). 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> > >
- Previous message (by thread): [atlas] BGP hijacking
- Next message (by thread): [atlas] BGP hijacking
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]