bgpreport

Network · data from 2026-11-12

AS216230 infowise INFOWISE SERVICES ApS

Registry name: infowise INFOWISE SERVICES ApS, DK · not in PeeringDB

6IPv4 routes 16.7% 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
5No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS216230, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS216230, 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.
45.134.164.0/22 No ROA RIR databaseRIPE 673 100% 66
185.94.104.0/22 No ROA RIR databaseRIPE 673 100% 66
185.118.180.0/22 No ROA RIR databaseRIPE 673 100% 66
185.155.152.0/22 No ROA RIR databaseRIPE 673 100% 66
185.243.224.0/22 No ROA RIR databaseRIPE 673 100% 66
80.75.208.0/24 Valid RIR databaseRIPE 672 100% 66
2a13:f540::/29 Valid RIR databaseRIPE 632 99% 67

AS-SET

AS216230 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 5 are in fix.csv.

  • ROA: none5
ChangePrefix or setDetailFull-table peers
ROA: none45.134.164.0/22No ROA covers it. Add a ROA for AS216230, maxLength 22.673 of 673
ROA: none185.94.104.0/22No ROA covers it. Add a ROA for AS216230, maxLength 22.673 of 673
ROA: none185.118.180.0/22No ROA covers it. Add a ROA for AS216230, maxLength 22.673 of 673
ROA: none185.155.152.0/22No ROA covers it. Add a ROA for AS216230, maxLength 22.673 of 673
ROA: none185.243.224.0/22No ROA covers it. Add a ROA for AS216230, maxLength 22.673 of 673

Route objects not announced

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