bgpreport

Network · data from 2026-11-12

AS213208 roxit Visma Roxit B.V.

Registry name: roxit Visma Roxit B.V., NL · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS213208, 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.200.85.0/24 Valid None 672 100% 66
2a07:5201::/48 Valid None 635 100% 67
2a07:5201:1::/48 Valid None 635 100% 67
2a07:5204:1::/48 Valid None 635 100% 67
2a07:5200::/48 Valid None 634 100% 67
2a07:5202::/48 Valid None 634 100% 67
2a07:5202:1::/48 Valid None 634 100% 67
2a07:5203::/48 Valid None 634 100% 67
2a07:5203:1::/48 Valid None 634 100% 67
2a07:5204::/48 Valid None 634 100% 67

AS-SET

AS213208 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.

  • Route object: none10
ChangePrefix or setDetailFull-table peers
Route object: none37.200.85.0/24No route object for it. Add a route object with origin AS213208 in the RIR database for the space.672 of 673
Route object: none2a07:5201::/48No route object for it. Add a route object with origin AS213208 in the RIR database for the space.635 of 636
Route object: none2a07:5201:1::/48No route object for it. Add a route object with origin AS213208 in the RIR database for the space.635 of 636
Route object: none2a07:5204:1::/48No route object for it. Add a route object with origin AS213208 in the RIR database for the space.635 of 636
Route object: none2a07:5200::/48No route object for it. Add a route object with origin AS213208 in the RIR database for the space.634 of 636
Route object: none2a07:5202::/48No route object for it. Add a route object with origin AS213208 in the RIR database for the space.634 of 636
Route object: none2a07:5202:1::/48No route object for it. Add a route object with origin AS213208 in the RIR database for the space.634 of 636
Route object: none2a07:5203::/48No route object for it. Add a route object with origin AS213208 in the RIR database for the space.634 of 636
Route object: none2a07:5203:1::/48No route object for it. Add a route object with origin AS213208 in the RIR database for the space.634 of 636
Route object: none2a07:5204::/48No route object for it. Add a route object with origin AS213208 in the RIR database for the space.634 of 636

Route objects not announced

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