bgpreport

Network · data from 2026-11-12

AS215721 zn-as Zinchenko Natalya

Registry name: zn-as Zinchenko Natalya, RU · not in PeeringDB

6IPv4 routes 0.0% RPKI valid · 0.0% with a route object
0IPv6 routes
6RPKI invalid 6 origin · 0 maxLength
0No ROA 6 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS215721, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS215721, 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.
91.247.96.0/22 Invalid: origin None 81 12% 38
91.247.100.0/22 Invalid: origin None 81 12% 38
91.247.106.0/23 Invalid: origin None 81 12% 38
91.247.123.0/24 Invalid: origin None 81 12% 38
91.247.124.0/24 Invalid: origin None 81 12% 38
185.186.232.0/23 Invalid: origin None 55 8%low visibility 31

AS-SET

AS215721 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 12 are in fix.csv.

  • ROA: origin6
  • Route object: none6
ChangePrefix or setDetailFull-table peers
ROA: origin91.247.96.0/22ROAs covering it name AS6789, not AS215721. If AS215721 should announce it, add a ROA for AS215721.81 of 673
Route object: none91.247.96.0/22No route object for it. Add a route object with origin AS215721 in the RIR database for the space.81 of 673
ROA: origin91.247.100.0/22ROAs covering it name AS6789, not AS215721. If AS215721 should announce it, add a ROA for AS215721.81 of 673
Route object: none91.247.100.0/22No route object for it. Add a route object with origin AS215721 in the RIR database for the space.81 of 673
ROA: origin91.247.106.0/23ROAs covering it name AS6789, not AS215721. If AS215721 should announce it, add a ROA for AS215721.81 of 673
Route object: none91.247.106.0/23No route object for it. Add a route object with origin AS215721 in the RIR database for the space.81 of 673
ROA: origin91.247.123.0/24ROAs covering it name AS6789, not AS215721. If AS215721 should announce it, add a ROA for AS215721.81 of 673
Route object: none91.247.123.0/24No route object for it. Add a route object with origin AS215721 in the RIR database for the space.81 of 673
ROA: origin91.247.124.0/24ROAs covering it name AS6789, not AS215721. If AS215721 should announce it, add a ROA for AS215721.81 of 673
Route object: none91.247.124.0/24No route object for it. Add a route object with origin AS215721 in the RIR database for the space.81 of 673
ROA: origin185.186.232.0/23ROAs covering it name AS6789, not AS215721. If AS215721 should announce it, add a ROA for AS215721.55 of 673
Route object: none185.186.232.0/23No route object for it. Add a route object with origin AS215721 in the RIR database for the space.55 of 673

Route objects not announced

Every route object with origin AS215721 is announced.

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.