Network · data from 2026-11-12
AS202617 Kering Eyewear S.p.A.
Registry name: KERINGEYEWEAR Kering Eyewear S.p.A., IT · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS202617, 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.
| 104.249.12.0/24 | Valid | Nonecovered by 104.249.12.0/22 | 673 100% |
| 104.249.15.0/24 | Valid | Nonecovered by 104.249.12.0/22 | 673 100% |
| 104.249.14.0/24 | Valid | Nonecovered by 104.249.12.0/22 | 668 99% |
| 84.247.18.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 93.113.103.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 93.113.109.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 104.249.12.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.159.0.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.216.12.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.254.65.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 2a07:b0c0::/29 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS202617: AS-KERINGEYEWEAR. 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 (AS202617 isn't in the set, or no route object for AS202617 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 | AS202617 in it | Not covered |
|---|---|---|---|---|---|
| AS-KERINGEYEWEAR | 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 5 are in fix.csv.
- Route object: none3
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 104.249.12.0/24 | No route object for it. A route object for 104.249.12.0/22 with origin AS202617 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202617 in the RIR database for the space. |
| Route object: none | 104.249.15.0/24 | No route object for it. A route object for 104.249.12.0/22 with origin AS202617 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202617 in the RIR database for the space. |
| Route object: none | 104.249.14.0/24 | No route object for it. A route object for 104.249.12.0/22 with origin AS202617 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202617 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS202617 whose prefix no peer sees AS202617 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a07:b0c0::/32 | RIPE | Invalid: maxLength |
| 2a07:b0c1::/32 | RIPE | Invalid: 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.