bgpreport

Network · data from 2026-11-12

AS35586 VOM

Registry name: VOM VOLYN OPTICAL NETWORKS LLC, UA · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS35586, 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.
94.131.212.0/23 No ROA RIR databaseRIPE 671 100% 68
185.183.92.0/22 No ROA RIR databaseRIPE 671 100% 68

AS-SET

AS35586's PeeringDB record names no 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 7 are in fix.csv.

  • ROA: none2
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none94.131.212.0/23No ROA covers it. Add a ROA for AS35586, maxLength 23.671 of 673
ROA: none185.183.92.0/22No ROA covers it. Add a ROA for AS35586, maxLength 22.671 of 673

Route objects not announced

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

185.183.92.0/24RIPENo ROA
185.183.93.0/24RIPENo ROA
185.183.94.0/24RIPENo ROA
185.183.95.0/24RIPENo ROA
2a07:7c00::/29RIPENo ROA

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.