bgpreport

Network · data from 2026-11-12

AS213161 VERTOM-GROUPINT Vertom Facilities B.V.

Registry name: VERTOM-GROUPINT Vertom Facilities B.V., NL · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS213161, 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.
37.72.103.0/24 Valid Other origin only 673 100% 67
2a06:d782::/32 Valid Other origin only 634 100% 67
2a06:d783::/32 Valid Other origin only 634 100% 67
91.193.112.0/24 Valid RIR databaseRIPE 673 100% 67
212.11.94.0/24 Valid RIR databaseRIPE 673 100% 67
2a06:d780::/32 Valid RIR databaseRIPE 635 100% 68
2a06:d781::/32 Valid RIR databaseRIPE 635 100% 68

AS-SET

AS213161 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 3 are in fix.csv.

  • Route object: none3
ChangePrefix or setDetailFull-table peers
Route object: none37.72.103.0/24Route objects for it name AS15830. Add a route object with origin AS213161 in the RIR database for the space.673 of 673
Route object: none2a06:d782::/32Route objects for it name AS15830. Add a route object with origin AS213161 in the RIR database for the space.634 of 636
Route object: none2a06:d783::/32Route objects for it name AS15830. Add a route object with origin AS213161 in the RIR database for the space.634 of 636

Route objects not announced

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