Network · data from 2026-11-12
AS46496 WTNC-INTERNAL-ISP - Washoe Tribe of Nevada and California
Registry name: WTNC-INTERNAL-ISP - Washoe Tribe of Nevada and California, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS46496, 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.
| 192.54.123.0/24 | No ROA | RIR databaseARIN, RADB | 673 100% |
| 75.141.64.0/24 | Valid | Other origin only | 673 100% |
| 47.45.48.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
AS-SET
AS46496 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 3 are in fix.csv.
- ROA: none1
- Route object: none1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 192.54.123.0/24 | No ROA covers it. Add a ROA for AS46496, maxLength 24. |
| Route object: none | 75.141.64.0/24 | Route objects for it name AS23222. Add a route object with origin AS46496 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS46496 whose prefix no peer sees AS46496 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 208.48.55.0/24 | ALTDB | 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.