Network · data from 2026-11-12
AS215596 KISSGROUP SAS
Registry name: Kissgroup KISSGROUP SAS, FR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS215596, 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.
| 38.45.53.0/24 | Invalid: maxLength | Nonecovered by 38.45.52.0/22 | 44 7%low visibility |
| 154.41.78.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
| 91.193.27.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 212.108.117.0/24 | Valid | None | 671 100% |
| 38.45.52.0/22 | Valid | RIR databaseARIN | 671 100% |
| 82.129.10.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 82.129.36.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 154.62.100.0/24 | Valid | RIR databaseARIN, RADB | 671 100% |
| 154.62.112.0/22 | Valid | RIR databaseARIN, RADB | 671 100% |
| 193.35.209.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 2a0e:4d40::/29 | Valid | RIR databaseRIPE | 633 100% |
AS-SET
PeeringDB's irr_as_set for AS215596: AS215596:AS-KISSGROUP. 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 (AS215596 isn't in the set, or no route object for AS215596 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 | AS215596 in it | Not covered |
|---|---|---|---|---|---|
| AS215596:AS-KISSGROUP | RIPE1 member set in no database: AS214625:AS-FIBER64 | 4 | 2 | Yes | 1 |
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 8 are in fix.csv.
- ROA: maxLength1
- ROA: none2
- Route object: none2
- Route object: RIR1
- AS-SET: missing member1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 38.45.53.0/24 | ROA 38.45.52.0/22 AS215596 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 38.45.53.0/24. |
| Route object: none | 38.45.53.0/24 | No route object for it. A route object for 38.45.52.0/22 with origin AS215596 covers it (filters allowing more-specifics accept it). Add a route object with origin AS215596 in the RIR database for the space. |
| ROA: none | 154.41.78.0/24 | No ROA covers it. Add a ROA for AS215596, maxLength 24. |
| Route object: RIR | 154.41.78.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 91.193.27.0/24 | No ROA covers it. Add a ROA for AS215596, maxLength 24. |
| Route object: none | 212.108.117.0/24 | No route object for it. Add a route object with origin AS215596 in the RIR database for the space. |
| AS-SET: missing member | AS215596:AS-KISSGROUP | AS215596:AS-KISSGROUP (RIPE) lists AS214625:AS-FIBER64; no IRR database read has it. |
Route objects not announced
Route objects with origin AS215596 whose prefix no peer sees AS215596 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a13:6c00::/29 | RIPE | No 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.