AS8675 AS_TULATEL PJSC Rostelecom

Announced routes

Every prefix a peer of the route collectors sees with origin AS8675, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.

AS-SET

AS8675 isn't in PeeringDB, where networks name their AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 34 are in fix.csv.

• Route object: not announced34

Route objects not announced

Route objects with origin AS8675 whose prefix no peer sees AS8675 announce. Many are kept on purpose (backup routes, space announced only in some places).