Network · data from 2026-11-12
AS15879 KPN Internedservices
Registry name: KPN-INTERNEDSERVICES Vancis IP B.V., NL · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS15879, 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.
| 88.151.36.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 195.3.176.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 5.226.40.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 46.255.104.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 77.245.80.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 80.246.176.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 81.24.48.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 82.201.0.0/17 | Valid | RIR databaseRIPE | 673 100% |
| 83.219.64.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 87.250.128.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 91.206.80.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 93.188.248.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 94.247.192.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 185.28.148.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.55.128.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 193.91.48.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 193.189.134.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.105.138.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 195.191.1.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 212.204.192.0/18 | Valid | RIR databaseRIPE | 673 100% |
| 213.130.160.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 213.133.32.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 213.197.192.0/18 | Valid | RIR databaseRIPE | 673 100% |
| 213.206.64.0/18 | Valid | RIR databaseRIPE | 673 100% |
| 217.115.192.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 217.148.80.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 217.149.64.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 217.194.96.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 193.104.111.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 193.105.3.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 2001:67c:1a4::/48 | Valid | RIR databaseRIPE | 635 100% |
| 2001:9a0::/32 | Valid | RIR databaseRIPE | 635 100% |
| 2001:14a0::/32 | Valid | RIR databaseRIPE | 635 100% |
| 2001:40e0::/32 | Valid | RIR databaseRIPE | 635 100% |
| 2a02:f18::/32 | Valid | RIR databaseRIPE | 635 100% |
| 2a02:f30::/32 | Valid | RIR databaseRIPE | 635 100% |
| 2001:898::/29 | Valid | RIR databaseRIPE | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS15879: AS-KPNIS. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS15879 isn't in the set, or no route object for AS15879 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS15879 in it | Not covered |
|---|---|---|---|---|---|
| AS-KPNIS | RIPE | 1 | 1 | Yes | 0 |
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 2 are in fix.csv.
- ROA: none2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 88.151.36.0/22 | No ROA covers it. Add a ROA for AS15879, maxLength 22. |
| ROA: none | 195.3.176.0/22 | No ROA covers it. Add a ROA for AS15879, maxLength 22. |
Route objects not announced
Every route object with origin AS15879 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.