bgpreport

Network · data from 2026-11-12

AS48137 PI-GROUP PI-GROUP BV

Registry name: PI-GROUP PI-GROUP BV, BE · not in PeeringDB

7IPv4 routes 28.6% 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
10Route objects not announced registered with origin AS48137, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS48137, 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.208.56.0/21 No ROA RIR databaseRIPE 673 100% 67
217.30.14.0/24 No ROA RIR databaseRIPE 673 100% 67
217.30.15.0/24 No ROA RIR databaseRIPE 673 100% 67
185.130.40.0/22 No ROA RIR databaseRIPE 672 100% 67
196.202.163.0/24 No ROA RIR databaseAFRINIC 672 100% 67
94.126.48.0/24 Valid RIR databaseRIPE 673 100% 67
94.126.49.0/24 Valid RIR databaseRIPE 673 100% 67
2a02:f00::/48 Valid RIR databaseRIPE 636 100% 67

AS-SET

AS48137 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 15 are in fix.csv.

  • ROA: none5
  • Route object: not announced10
ChangePrefix or setDetailFull-table peers
ROA: none37.208.56.0/21No ROA covers it. Add a ROA for AS48137, maxLength 21.673 of 673
ROA: none217.30.14.0/24No ROA covers it. Add a ROA for AS48137, maxLength 24.673 of 673
ROA: none217.30.15.0/24No ROA covers it. Add a ROA for AS48137, maxLength 24.673 of 673
ROA: none185.130.40.0/22No ROA covers it. Add a ROA for AS48137, maxLength 22.672 of 673
ROA: none196.202.163.0/24No ROA covers it. Add a ROA for AS48137, maxLength 24.672 of 673

Route objects not announced

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

37.208.56.0/24RIPENo ROA
37.208.57.0/24RIPENo ROA
37.208.58.0/23RIPENo ROA
37.208.60.0/24RIPENo ROA
37.208.61.0/24RIPENo ROA
37.208.62.0/23RIPENo ROA
94.126.48.0/21RIPENo ROA
102.222.44.0/24AFRINICNo ROA
2a02:f00::/32RIPENo ROA
2a02:f00::/64RIPEInvalid: maxLength

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.