bgpreport

Network · data from 2026-11-12

AS25222 AS-ISOL Inmarsat Solutions B.V.

Registry name: AS-ISOL Inmarsat Solutions B.V., NL · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS25222, 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.
103.7.98.0/24 No ROA RIR databaseAPNIC 671 100% 68
68.67.0.0/22 Valid RIR databaseARIN 671 100% 68
78.40.66.0/23 Valid RIR databaseRIPE 671 100% 68
78.40.68.0/22 Valid RIR databaseRIPE 671 100% 68
89.207.115.0/24 Valid RIR databaseRIPE 671 100% 68
89.207.118.0/24 Valid RIR databaseRIPE 671 100% 68
92.43.8.0/22 Valid RIR databaseRIPE 671 100% 68
109.232.12.0/23 Valid RIR databaseRADB, RIPE 671 100% 68
173.243.96.0/22 Valid RIR databaseARIN 671 100% 68
173.243.106.0/23 Valid RIR databaseARIN 671 100% 68
180.94.48.0/21 Valid RIR databaseAPNIC, RADB 671 100% 68
185.151.232.0/23 Valid RIR databaseRIPE 671 100% 68
192.40.224.0/22 Valid RIR databaseARIN 671 100% 68
212.165.64.0/21 Valid RIR databaseRIPE 671 100% 68
212.165.70.0/24 Valid RIR databaseRIPE 671 100% 68
212.165.72.0/22 Valid RIR databaseRIPE 671 100% 68
212.165.76.0/22 Valid RIR databaseRIPE 671 100% 68
212.165.92.0/22 Valid RIR databaseRIPE 671 100% 68
212.165.96.0/20 Valid RIR databaseRIPE 671 100% 68
212.165.112.0/22 Valid RIR databaseRIPE 671 100% 68
212.165.118.0/23 Valid RIR databaseNTTCOM, RIPE 671 100% 68
212.165.120.0/23 Valid RIR databaseRIPE 671 100% 68
212.165.122.0/23 Valid RIR databaseNTTCOM, RIPE 671 100% 68
212.165.124.0/24 Valid RIR databaseRIPE 671 100% 68
212.165.126.0/24 Valid RIR databaseRIPE 671 100% 68
216.86.240.0/20 Valid RIR databaseARIN 671 100% 68
216.129.170.0/23 Valid RIR databaseARIN 671 100% 68
2402:1500:8000::/33 Valid RIR databaseAPNIC 635 100% 69
2605:db00::/32 Valid RIR databaseARIN 635 100% 69
2a03:1c80::/32 Valid RIR databaseRIPE 635 100% 69

AS-SET

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

  • ROA: none1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none103.7.98.0/24No ROA covers it. Add a ROA for AS25222, maxLength 24.671 of 673

Route objects not announced

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

46.235.5.0/24RIPENo ROA
103.41.108.0/24APNIC, RADBNo 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.