Network · data from 2026-11-12
AS11944 LTC-1 - LaValle Telephone Cooperative
Registry name: LTC-1 - LaValle Telephone Cooperative, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS11944, 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.
| 2602:fa22::/40 | No ROA | RIR databaseARIN | 634 100% |
AS-SET
AS11944 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 5 are in fix.csv.
- ROA: none1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2602:fa22::/40 | No ROA covers it. Add a ROA for AS11944, maxLength 40. |
Route objects not announced
Route objects with origin AS11944 whose prefix no peer sees AS11944 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 31.186.231.0/24 | RADB | No ROA |
| 63.251.85.0/24 | RADB | No ROA |
| 208.92.238.0/24 | BBOI | Invalid: origin |
| 2606:a600:ffff::/48 | 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.