bgpreport

Network · data from 2026-11-12

AS54579 Chariton Valley Telephone Corporation

Registry name: CVALLEY - Chariton Valley Telephone Corporation, US · PeeringDB

5IPv4 routes 20.0% RPKI valid · 100.0% with a route object
1IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
5No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS54579, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS54579, 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.
65.255.144.0/20 No ROA Other IRR onlyRADB 671 100% 67
68.68.184.0/22 No ROA Other IRR onlyRADB 671 100% 67
76.8.144.0/20 No ROA Other IRR onlyRADB 671 100% 67
199.36.80.0/22 No ROA Other IRR onlyRADB 671 100% 67
2606:5780::/32 No ROA Other IRR onlyALTDB, RADB 605 95% 67
65.255.130.0/24 Valid Other IRR onlyRADB 671 100% 67

AS-SET

PeeringDB's irr_as_set for AS54579: AS54579:AS-ALL. 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 (AS54579 isn't in the set, or no route object for AS54579 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.

NameDatabaseASNsSets Route objectsAS54579 in itNot covered
AS54579:AS-ALL RADB 4144 No 6

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 12 are in fix.csv.

  • ROA: none5
  • Route object: RIR6
  • AS-SET: own ASN1
ChangePrefix or setDetailFull-table peers
ROA: none65.255.144.0/20No ROA covers it. Add a ROA for AS54579, maxLength 20.671 of 673
Route object: RIR65.255.144.0/20Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none68.68.184.0/22No ROA covers it. Add a ROA for AS54579, maxLength 22.671 of 673
Route object: RIR68.68.184.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none76.8.144.0/20No ROA covers it. Add a ROA for AS54579, maxLength 20.671 of 673
Route object: RIR76.8.144.0/20Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none199.36.80.0/22No ROA covers it. Add a ROA for AS54579, maxLength 22.671 of 673
Route object: RIR199.36.80.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none2606:5780::/32No ROA covers it. Add a ROA for AS54579, maxLength 32.605 of 636
Route object: RIR2606:5780::/32Route object only in ALTDB, RADB. Add it in the RIR database for the space.605 of 636
Route object: RIR65.255.130.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
AS-SET: own ASNAS54579:AS-ALLAS54579 isn't in AS54579:AS-ALL (RADB) once expanded. Add AS54579 to it.

Route objects not announced

Every route object with origin AS54579 is announced.

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.