Network report
Who holds an IP address, prefix or AS number, how it is routed (origin AS, RPKI, IRR), its reverse DNS, blocklist listings and PeeringDB record, with what to fix first.
Checking routing, RPKI, reverse DNS, blocklists and the registry. This usually takes 3 to 10 seconds.
Warning: AS202617 (KERINGEYEWEAR) announces 10 IPv4 and 1 IPv6 prefixes. 2 warnings
| AS page | AS202617 |
|---|---|
| Holder | KERINGEYEWEAR Kering Eyewear S.p.A. |
| Allocation | RIPE NCC, Italy (IT), allocated 2016-07-11 |
| Prefixes (IPv4 / IPv6) | 10 / 1 |
| RPKI valid | 100% (11 / 11) |
| Upstreams and peers | 62 |
| Peering policy | Open |
What to fix
-
Warning
3 of 11 announced prefixes have no IRR route object: 104.249.12.0/24, 104.249.14.0/24, 104.249.15.0/24.
Many networks build their prefix filters from IRR data; without route objects some of them drop the routes.
Fix: Create route (IPv4) and route6 (IPv6) objects with origin AS202617 in your RIR’s IRR database (or RADB).
route: 104.249.12.0/24 origin: AS202617 route: 104.249.14.0/24 origin: AS202617 route: 104.249.15.0/24 origin: AS202617
-
Warning
No public NOC, policy or technical contact.
Other networks use these addresses to set up peering and to reach you during an incident.
Fix: Add a role contact (for example noc@ or peering@ an address you monitor) with visibility Public.
Checks
Routing and RPKI 3 of 11 announced prefixes have no IRR route object: 104.249.12.0/24, 104.249.14.0/24, 104.249.15.0/24.
- Pass: AS202617 announces 10 IPv4 and 1 IPv6 prefixes.
- Pass: All 11 announced prefixes are RPKI valid.
- Warning: 3 of 11 announced prefixes have no IRR route object: 104.249.12.0/24, 104.249.14.0/24, 104.249.15.0/24.
- Info: 62 upstreams and peers, 0 downstream networks seen.
| Holder | KERINGEYEWEAR Kering Eyewear S.p.A. |
|---|---|
| IPv4 prefixes | 10 |
| IPv6 prefixes | 1 |
| RPKI | 11 valid |
| Without IRR route object | 3 |
| Downstream networks | 0 |
Source: RIPEstat (RIPE NCC RIS, Routinator, IRR); AS names: Team Cymru
Open in ASN & BGP prefix lookupRegistration Found at rdap.db.ripe.net.
- Pass: Found at rdap.db.ripe.net.
| Name | KERINGEYEWEAR |
|---|---|
| Handle | AS202617 |
| Range | AS202617 |
| Status | active |
| Registered | 2016-07-11T14:07:39Z |
| Last changed | 2026-08-29T20:51:26Z |
| Abuse contact | abuse@keringeyewear.com |
| Registry (RIR) | RIPE NCC |
|---|---|
| Country | Italy (IT) |
| Delegated on | 2016-07-11 |
| Status | Allocated |
| Delegated range | AS202617 |
Source: RIR delegation data, updated daily. The country is where the range was registered, not necessarily where it is used.
| Role | Name | |
|---|---|---|
| registrant | it-keringeyewear-1-mnt | |
| registrant | Kering Eyewear S.p.A. | |
| registrant | RIPE-NCC-END-MNT | |
| abuse | Abuse-C Role | abuse@keringeyewear.com |
Source: https://rdap.db.ripe.net/autnum/202617. Registration data from rdap.db.ripe.net, shown under its terms of use (terms): not for marketing or bulk collection. Personal contacts in this registry are not shown.
Open in WHOIS / RDAP lookupPeeringDB No public NOC, policy or technical contact.
- Pass: AS202617 is in PeeringDB as Kering Eyewear S.p.A..
- Info: Peering policy: Open.
- Info: Present at 7 internet exchanges with 7 ports (70G in total).
- Warning: No public NOC, policy or technical contact.
| Network | Kering Eyewear S.p.A. (Kering Eyewear) |
|---|---|
| AS number | AS202617 |
| Type | , Global |
| Website | https://www.keringeyewear.com |
| IRR as-set | AS-KERINGEYEWEAR |
| Prefixes (IPv4 / IPv6) | 20 / 10 |
| Traffic | 5-10Gbps, Balanced |
| Peering policy | Open |
| Locations | Preferred |
| Ratio required | No |
| Contracts | Not Required |
| Last updated | 2026-10-14 |
Source: PeeringDB. Results are cached for an hour.
Open in PeeringDB lookup