bgpreport

Network · data from 2026-11-12

AS21286 KPN-Corporate-Market KPN B.V.

Registry name: KPN-Corporate-Market KPN B.V., NL · not in PeeringDB

23IPv4 routes 95.7% RPKI valid · 100.0% with a route object
5IPv6 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
3Route objects not announced registered with origin AS21286, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS21286, 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.
158.67.0.0/16 No ROA RIR databaseRIPE 673 100% 67
80.79.96.0/20 Valid RIR databaseRIPE 673 100% 67
145.13.0.0/16 Valid RIR databaseRIPE 673 100% 67
145.15.0.0/22 Valid RIR databaseRIPE 673 100% 67
145.15.90.0/24 Valid RIR databaseRIPE 673 100% 67
145.15.92.0/22 Valid RIR databaseRIPE 673 100% 67
145.15.96.0/22 Valid RIR databaseRIPE 673 100% 67
145.222.0.0/16 Valid RIR databaseRIPE 673 100% 67
192.33.235.0/24 Valid RIR databaseRIPE 673 100% 67
192.33.238.0/24 Valid RIR databaseRIPE 673 100% 67
192.33.239.0/24 Valid RIR databaseRIPE 673 100% 67
192.35.133.0/24 Valid RIR databaseRIPE 673 100% 67
192.58.226.0/24 Valid RIR databaseRIPE 673 100% 67
192.58.227.0/24 Valid RIR databaseRIPE 673 100% 67
192.101.111.0/24 Valid RIR databaseRIPE 673 100% 67
192.101.112.0/24 Valid RIR databaseRIPE 673 100% 67
192.101.113.0/24 Valid RIR databaseRIPE 673 100% 67
193.176.216.0/23 Valid RIR databaseRIPE 673 100% 67
193.202.32.0/23 Valid RIR databaseRIPE 673 100% 67
194.104.32.0/24 Valid RIR databaseRIPE 673 100% 67
194.104.59.0/24 Valid RIR databaseRIPE 673 100% 67
199.88.208.0/24 Valid RIR databaseRIPE 673 100% 67
199.88.209.0/24 Valid RIR databaseRIPE 673 100% 67
2001:67c:5a0::/48 Valid RIR databaseRIPE 635 100% 67
2a02:2b50:ffff::/48 Valid RIR databaseRIPE 635 100% 67
2a03:4800::/40 Valid RIR databaseRIPE 635 100% 67
2a03:4800:100::/40 Valid RIR databaseRIPE 635 100% 67
2a07:3502:1120::/48 Valid RIR databaseRIPE 635 100% 67

AS-SET

AS21286 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 4 are in fix.csv.

  • ROA: none1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none158.67.0.0/16No ROA covers it. Add a ROA for AS21286, maxLength 16.673 of 673

Route objects not announced

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

144.44.0.0/16RIPENo ROA
170.37.203.0/24RIPENo ROA
192.58.228.0/24RIPEValid

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.