Autunomous system filtering?

Fri Nov 18 20:36:34 UTC 2016

On Fri, Nov 18, 2016 at 1:39 PM,  <spano at datacast.it> wrote:

> Consider that when we were announcing the whole /22 everything was working correctly, then suddenly some ASs stopped to accept our prefixes. That's why we decided to split the network and announce prefixes with different AS. Moreover the /23 announced by AS2876 spreaded correctly, even if the object has been created at the same time as the other...

around 11/16 16:00UTC, 185.85.20.0/22's originating ASN changed from
AS28716 to AS207029

The route object for 185.85.20.0/22 had origin changed from AS28716 to
AS207029 at 2016-11-16T15:09:22Z but AS207029 was not in AS-RETELIT
(it is now 2016-11-18T14:34:44Z). So when AS28716's upstreams rebuilt
the inbound filter, 185.85.20.0/22 got dropped.

When AS28716's upstreams update the filter again, 185.85.22.0/23
should become visible. It looks like the route object for
185.85.20.0/22 has been deleted.

Is there a whowas service for routing registries?

Yang