bgpreport

Network · data from 2026-11-12

AS30263 Cal-Ore Telephone

Registry name: COTNET - Cal-Ore Telephone Co., US · PeeringDB

10IPv4 routes 100.0% RPKI valid · 100.0% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
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 AS30263, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS30263, 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.

69.36.192.0/20 Valid Other IRR onlyRADB 673 100% 67
216.7.112.0/20 Valid Other IRR onlyRADB 673 100% 67
69.36.192.0/22 Valid Other IRR onlyRADB 671 100% 70
69.36.196.0/22 Valid Other IRR onlyRADB 671 100% 70
69.36.200.0/22 Valid Other IRR onlyRADB 671 100% 70
69.36.204.0/22 Valid Other IRR onlyRADB 671 100% 70
216.7.112.0/22 Valid Other IRR onlyRADB 671 100% 70
216.7.116.0/22 Valid Other IRR onlyRADB 671 100% 70
216.7.120.0/22 Valid Other IRR onlyRADB 671 100% 70
216.7.124.0/22 Valid Other IRR onlyRADB 671 100% 70
2607:1000::/32 Valid Other IRR onlyRADB 635 100% 70

AS-SET

AS30263's PeeringDB record names no 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 11 are in fix.csv.

  • Route object: RIR11
ChangePrefix or setDetailFull-table peers
Route object: RIR69.36.192.0/20Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR216.7.112.0/20Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR69.36.192.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR69.36.196.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR69.36.200.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR69.36.204.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR216.7.112.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR216.7.116.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR216.7.120.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR216.7.124.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR2607:1000::/32Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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