bgpreport

Network · data from 2026-11-12

AS26421 PONDEROSA-INTERNET - Ponderosa Cablevision

Registry name: PONDEROSA-INTERNET - Ponderosa Cablevision, US · not in PeeringDB

15IPv4 routes 100.0% RPKI valid · 100.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
0No 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 AS26421, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS26421, 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.
50.58.142.0/23 Valid Other IRR onlyRADB 671 100% 70
64.129.228.0/24 Valid Other IRR onlyRADB 671 100% 70
74.202.200.0/23 Valid Other IRR onlyRADB 671 100% 70
206.169.217.0/24 Valid Other IRR onlyRADB 671 100% 70
206.169.218.0/23 Valid Other IRR onlyRADB 671 100% 70
207.114.159.0/24 Valid Other IRR onlyRADB 671 100% 70
209.150.76.0/24 Valid Other IRR onlyRADB 671 100% 70
209.150.77.0/24 Valid Other IRR onlyRADB 671 100% 70
209.234.196.0/24 Valid Other IRR onlyRADB 671 100% 70
209.234.206.0/24 Valid Other IRR onlyRADB 671 100% 70
209.234.207.0/24 Valid Other IRR onlyRADB 671 100% 70
209.234.208.0/23 Valid Other IRR onlyRADB 671 100% 70
209.234.216.0/23 Valid Other IRR onlyRADB 671 100% 70
209.234.222.0/24 Valid Other IRR onlyRADB 671 100% 70
23.29.0.0/20 Valid RIR databaseARIN, RADB 671 100% 69

AS-SET

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

  • Route object: RIR14
ChangePrefix or setDetailFull-table peers
Route object: RIR50.58.142.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR64.129.228.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR74.202.200.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR206.169.217.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR206.169.218.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR207.114.159.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR209.150.76.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR209.150.77.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR209.234.196.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR209.234.206.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR209.234.207.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR209.234.208.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR209.234.216.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR209.234.222.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

Every route object with origin AS26421 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.