Every 1 hour the prefix 147.189.(216+N).0/24 is advertised. The
N here is calculated as HH % 8, so the hour in 24h format
modulo 8. Naturally, UTC is used. The prefix is withdrawn 10'
after the advertisement.
At most one /24 should be available at any single time, which
means that all 8 prefixes of the /21 rotate 3 times a day.
At 00:00, 147.189.216.0/24 is advertised, at 00:10 it is then
withdrawn, then at 01:00 147.189.217.0/24 is advertised, which
is in turn withdrawn at 01:10, and so on.
Why? We are conducting research on BGP Stuck Routes to better
understand how they happen, when, which equipment is more
buggy, etc. We also want to understand them better. As this is
a beacon, anyone can study the results using RIPE RIS, or any
other source like RouteViews. Feel free to take a look and let
everyone know if something interesting ever comes up!
An example of research presented at RIPE 89 is here:
https://ripe89.ripe.net/wp-content/uploads/presentations/8-BGP-Zombies-RIPE89.pdf
We are also studying the propagation of BGP Communities with
this beacon, to minimize the count of BGP UPDATEs generated.
At origin, all prefixes are tagged with the following values:
BGP Legacy Communities:
(4492, 64700)
(4601, 64700)
BGP Extended Communities:
(ro, 4492, 1337)
(ro, 4601, 1337)
(ro, 210312, 1337)
BGP Large Communities:
(4492, 64700, 1337)
(4601, 64700, 1337)
(210312, 64700, 1337)
For any more info or collaboration, find me using the Contact
page at daknob.net :)
Geofeed https://geo.daknob.net/as210312.csv