Network · data from 2026-11-12
AS199877 KENNAMETAL Kennametal Shared Services GmbH
Registry name: KENNAMETAL Kennametal Shared Services GmbH, DE · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS199877, 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.
| 194.180.88.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 194.180.80.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 194.180.90.0/24 | No ROA | RIR databaseRIPE | 672 100% |
AS-SET
AS199877 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 7 are in fix.csv.
- ROA: none3
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 194.180.88.0/24 | No ROA covers it. Add a ROA for AS199877, maxLength 24. |
| ROA: none | 194.180.80.0/24 | No ROA covers it. Add a ROA for AS199877, maxLength 24. |
| ROA: none | 194.180.90.0/24 | No ROA covers it. Add a ROA for AS199877, maxLength 24. |
Route objects not announced
Route objects with origin AS199877 whose prefix no peer sees AS199877 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 194.180.81.0/24 | RIPE | No ROA |
| 194.180.84.0/23 | RIPE | No ROA |
| 194.180.86.0/24 | RIPE | No ROA |
| 194.180.89.0/24 | 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.