bgpreport

Network · data from 2026-11-12

AS43287 RU-VITNET-AS OOO "VIT"

Registry name: RU-VITNET-AS OOO "VIT", RU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS43287, 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.
185.201.45.16/28 No ROA Nonecovered by 185.201.45.0/24 1 0%low visibility 1
193.200.211.0/28 No ROA Nonecovered by 193.200.211.0/24 1 0%low visibility 1
185.17.200.0/24 No ROA RIR databaseRIPE 671 100% 68
185.81.248.0/22 No ROA RIR databaseRIPE 671 100% 68
185.201.45.0/24 No ROA RIR databaseRIPE 671 100% 68
193.200.211.0/24 No ROA RIR databaseRIPE 671 100% 68
185.193.141.0/24 No ROA RIR databaseRIPE 670 100% 68
2a03:6660::/32 No ROA RIR databaseRIPE 636 100% 69

AS-SET

AS43287 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 10 are in fix.csv.

  • ROA: none8
  • Route object: none2
ChangePrefix or setDetailFull-table peers
ROA: none185.201.45.16/28No ROA covers it. Add a ROA for AS43287, maxLength 28.1 of 673
Route object: none185.201.45.16/28No route object for it. A route object for 185.201.45.0/24 with origin AS43287 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS43287 in the RIR database for the space.1 of 673
ROA: none193.200.211.0/28No ROA covers it. Add a ROA for AS43287, maxLength 28.1 of 673
Route object: none193.200.211.0/28No route object for it. A route object for 193.200.211.0/24 with origin AS43287 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS43287 in the RIR database for the space.1 of 673
ROA: none185.17.200.0/24No ROA covers it. Add a ROA for AS43287, maxLength 24.671 of 673
ROA: none185.81.248.0/22No ROA covers it. Add a ROA for AS43287, maxLength 22.671 of 673
ROA: none185.201.45.0/24No ROA covers it. Add a ROA for AS43287, maxLength 24.671 of 673
ROA: none193.200.211.0/24No ROA covers it. Add a ROA for AS43287, maxLength 24.671 of 673
ROA: none185.193.141.0/24No ROA covers it. Add a ROA for AS43287, maxLength 24.670 of 673
ROA: none2a03:6660::/32No ROA covers it. Add a ROA for AS43287, maxLength 32.636 of 636

Route objects not announced

Every route object with origin AS43287 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.