Network · data from 2026-11-12
AS272962 KW SERVICES RD, S.R.L.
Registry name: AS272962 - KW SERVICES RD, S.R.L., DO · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS272962, 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.
| 109.110.191.0/24 | Valid | Nonecovered by 109.110.190.0/23 | 672 100% |
| 109.66.166.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 38.7.106.0/24 | Valid | RIR databaseARIN | 671 100% |
| 38.7.107.0/24 | Valid | RIR databaseARIN | 671 100% |
| 38.224.236.0/24 | Valid | RIR databaseARIN | 671 100% |
| 38.224.238.0/24 | Valid | RIR databaseARIN | 671 100% |
| 38.224.239.0/24 | Valid | RIR databaseARIN | 671 100% |
| 2803:f990:2::/48 | Valid | RIR databaseLACNIC | 636 100% |
| 2803:f990::/32 | Valid | RIR databaseLACNIC | 635 100% |
| 2803:f990:7::/48 | Valid | RIR databaseLACNIC | 635 100% |
| 2803:f990:8::/48 | Valid | RIR databaseLACNIC | 635 100% |
| 2803:f990:9::/48 | Valid | RIR databaseLACNIC | 635 100% |
| 2803:f990:a::/48 | Valid | RIR databaseLACNIC | 635 100% |
| 2803:f990:800::/48 | Valid | RIR databaseLACNIC | 635 100% |
| 2803:f990:5::/48 | Valid | RIR databaseLACNIC | 634 100% |
| 2803:f990:6::/48 | Valid | RIR databaseLACNIC | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS272962: AS272962:AS-KW. 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 (AS272962 isn't in the set, or no route object for AS272962 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 | AS272962 in it | Not covered |
|---|---|---|---|---|---|
| AS272962:AS-KW | LACNIC | 15 | 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: none1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 109.110.191.0/24 | No route object for it. A route object for 109.110.190.0/23 with origin AS272962 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272962 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS272962 whose prefix no peer sees AS272962 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.153.165.0/24 | RADB, RIPE | Valid |
| 109.66.199.0/24 | RADB, RIPE | Valid |
| 109.110.190.0/23 | RADB, RIPE | Valid |
| 109.122.17.0/24 | RADB, RIPE | Valid |
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.