bgpreport

Network · data from 2026-11-12

AS61213 Visma

Registry name: VISMA-AS Visma Software International AS, NO · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS61213, 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.123.48.0/24 No ROA RIR databaseRIPE 673 100% 66
91.123.49.0/24 No ROA RIR databaseRIPE 673 100% 66
91.123.50.0/23 No ROA RIR databaseRIPE 673 100% 66
91.123.52.0/22 No ROA RIR databaseRIPE 673 100% 66
91.123.56.0/24 No ROA RIR databaseRIPE 673 100% 66
91.123.57.0/24 No ROA RIR databaseRIPE 673 100% 66
91.123.60.0/22 No ROA RIR databaseRIPE 673 100% 66
193.181.186.0/24 No ROA RIR databaseRIPE 672 100% 67
194.68.15.0/24 No ROA RIR databaseRIPE 672 100% 67
94.140.17.0/24 Valid RIR databaseRIPE 673 100% 66
185.206.4.0/22 Valid RIR databaseRIPE 673 100% 66
185.206.4.0/23 Valid RIR databaseRIPE 673 100% 66
185.206.6.0/23 Valid RIR databaseRIPE 673 100% 66
2a02:d60::/32 Valid RIR databaseRIPE 634 100% 67

AS-SET

AS61213'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 13 are in fix.csv.

  • ROA: none9
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none91.123.48.0/24No ROA covers it. Add a ROA for AS61213, maxLength 24.673 of 673
ROA: none91.123.49.0/24No ROA covers it. Add a ROA for AS61213, maxLength 24.673 of 673
ROA: none91.123.50.0/23No ROA covers it. Add a ROA for AS61213, maxLength 23.673 of 673
ROA: none91.123.52.0/22No ROA covers it. Add a ROA for AS61213, maxLength 22.673 of 673
ROA: none91.123.56.0/24No ROA covers it. Add a ROA for AS61213, maxLength 24.673 of 673
ROA: none91.123.57.0/24No ROA covers it. Add a ROA for AS61213, maxLength 24.673 of 673
ROA: none91.123.60.0/22No ROA covers it. Add a ROA for AS61213, maxLength 22.673 of 673
ROA: none193.181.186.0/24No ROA covers it. Add a ROA for AS61213, maxLength 24.672 of 673
ROA: none194.68.15.0/24No ROA covers it. Add a ROA for AS61213, maxLength 24.672 of 673

Route objects not announced

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

91.123.58.0/23RIPENo ROA
2a02:d60::/48RIPEValid
2a02:d60:1::/48RIPEValid
2a02:d60:2::/48RIPEValid

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.