bgpreport

Network · data from 2026-11-12

AS55230 PWRTC-AS - Pulaski White Rural Telephone Cooperative Inc.

Registry name: PWRTC-AS - Pulaski White Rural Telephone Cooperative Inc., US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS55230, 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.230.192.0/21 Valid Nonecovered by 192.230.192.0/20 673 100% 67
192.230.200.0/21 Valid Nonecovered by 192.230.192.0/20 673 100% 67
205.174.148.0/22 Valid Nonecovered by 205.174.144.0/21 671 100% 67
216.205.16.0/22 Valid Nonecovered by 216.205.16.0/21 671 100% 67
216.205.20.0/22 Valid Nonecovered by 216.205.16.0/21 671 100% 67
2604:c580::/32 Valid None 634 100% 67
64.184.120.0/21 Valid Other IRR onlyRADB 673 100% 67
192.230.192.0/20 Valid RIR databaseARIN 673 100% 67
205.174.144.0/21 Valid RIR databaseARIN, RADB 673 100% 67
216.205.16.0/21 Valid RIR databaseARIN, RADB 673 100% 67

AS-SET

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

  • Route object: none6
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
Route object: none192.230.192.0/21No route object for it. A route object for 192.230.192.0/20 with origin AS55230 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55230 in the RIR database for the space.673 of 673
Route object: none192.230.200.0/21No route object for it. A route object for 192.230.192.0/20 with origin AS55230 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55230 in the RIR database for the space.673 of 673
Route object: none205.174.148.0/22No route object for it. A route object for 205.174.144.0/21 with origin AS55230 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55230 in the RIR database for the space.671 of 673
Route object: none216.205.16.0/22No route object for it. A route object for 216.205.16.0/21 with origin AS55230 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55230 in the RIR database for the space.671 of 673
Route object: none216.205.20.0/22No route object for it. A route object for 216.205.16.0/21 with origin AS55230 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55230 in the RIR database for the space.671 of 673
Route object: none2604:c580::/32No route object for it. Add a route object with origin AS55230 in the RIR database for the space.634 of 636
Route object: RIR64.184.120.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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