Network · data from 2026-11-12
AS36460 WATTSCORPORATEASN - Watts Water Technologies, Inc.
Registry name: WATTSCORPORATEASN - Watts Water Technologies, Inc., US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS36460, 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.
| 199.91.94.0/24 | No ROA | Nonecovered by 199.91.92.0/22 | 673 100% |
| 199.91.95.0/24 | No ROA | Nonecovered by 199.91.92.0/22 | 673 100% |
AS-SET
AS36460 isn't in PeeringDB, where networks name their AS-SET.
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 6 are in fix.csv.
- ROA: none2
- Route object: none2
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 199.91.94.0/24 | No ROA covers it. Add a ROA for AS36460, maxLength 24. |
| Route object: none | 199.91.94.0/24 | No route object for it. A route object for 199.91.92.0/22 with origin AS36460 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36460 in the RIR database for the space. |
| ROA: none | 199.91.95.0/24 | No ROA covers it. Add a ROA for AS36460, maxLength 24. |
| Route object: none | 199.91.95.0/24 | No route object for it. A route object for 199.91.92.0/22 with origin AS36460 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36460 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS36460 whose prefix no peer sees AS36460 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 65.114.190.0/24 | RADB | No ROA |
| 199.91.92.0/22 | RADB | 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.