bgpreport

Network · data from 2026-11-12

AS20477 RANDOLPHTELEPHONE - Randolph Telephone Company

Registry name: RANDOLPHTELEPHONE - Randolph Telephone Company, US · not in PeeringDB

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

Announced routes

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

74.206.64.0/20 Valid Nonecovered by 74.206.64.0/19 671 100% 68
74.206.80.0/20 Valid Nonecovered by 74.206.64.0/19 671 100% 68
137.118.156.0/23 Valid Nonecovered by 137.118.156.0/22 671 100% 68
137.118.158.0/23 Valid Nonecovered by 137.118.156.0/22 671 100% 68
137.118.160.0/21 Valid Nonecovered by 137.118.160.0/20 671 100% 68
137.118.168.0/21 Valid Nonecovered by 137.118.160.0/20 671 100% 68
137.118.196.0/23 Valid Nonecovered by 137.118.196.0/22 671 100% 68
137.118.198.0/23 Valid Nonecovered by 137.118.196.0/22 671 100% 68
137.118.204.0/23 Valid Nonecovered by 137.118.204.0/22 671 100% 68
137.118.206.0/23 Valid Nonecovered by 137.118.204.0/22 671 100% 68
137.118.208.0/23 Valid Nonecovered by 137.118.208.0/22 671 100% 68
137.118.210.0/23 Valid Nonecovered by 137.118.208.0/22 671 100% 68
137.118.176.0/21 Valid Other IRR onlyRADB 672 100% 67
137.118.150.0/23 Valid Other IRR onlyRADB 671 100% 68
74.206.64.0/19 Valid RIR databaseARIN, RADB 672 100% 67
137.118.156.0/22 Valid RIR databaseARIN, RADB 672 100% 67
137.118.160.0/20 Valid RIR databaseARIN, RADB 672 100% 67
137.118.196.0/22 Valid RIR databaseARIN, RADB 672 100% 67
137.118.204.0/22 Valid RIR databaseARIN, RADB 672 100% 67
137.118.208.0/22 Valid RIR databaseARIN, RADB 672 100% 67
137.118.176.0/22 Valid RIR databaseARIN 671 100% 68
137.118.180.0/22 Valid RIR databaseARIN, RADB 671 100% 68

AS-SET

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

  • Route object: none12
  • Route object: RIR2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: none74.206.64.0/20No route object for it. A route object for 74.206.64.0/19 with origin AS20477 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20477 in the RIR database for the space.671 of 673
Route object: none74.206.80.0/20No route object for it. A route object for 74.206.64.0/19 with origin AS20477 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20477 in the RIR database for the space.671 of 673
Route object: none137.118.156.0/23No route object for it. A route object for 137.118.156.0/22 with origin AS20477 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20477 in the RIR database for the space.671 of 673
Route object: none137.118.158.0/23No route object for it. A route object for 137.118.156.0/22 with origin AS20477 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20477 in the RIR database for the space.671 of 673
Route object: none137.118.160.0/21No route object for it. A route object for 137.118.160.0/20 with origin AS20477 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20477 in the RIR database for the space.671 of 673
Route object: none137.118.168.0/21No route object for it. A route object for 137.118.160.0/20 with origin AS20477 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20477 in the RIR database for the space.671 of 673
Route object: none137.118.196.0/23No route object for it. A route object for 137.118.196.0/22 with origin AS20477 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20477 in the RIR database for the space.671 of 673
Route object: none137.118.198.0/23No route object for it. A route object for 137.118.196.0/22 with origin AS20477 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20477 in the RIR database for the space.671 of 673
Route object: none137.118.204.0/23No route object for it. A route object for 137.118.204.0/22 with origin AS20477 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20477 in the RIR database for the space.671 of 673
Route object: none137.118.206.0/23No route object for it. A route object for 137.118.204.0/22 with origin AS20477 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20477 in the RIR database for the space.671 of 673
Route object: none137.118.208.0/23No route object for it. A route object for 137.118.208.0/22 with origin AS20477 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20477 in the RIR database for the space.671 of 673
Route object: none137.118.210.0/23No route object for it. A route object for 137.118.208.0/22 with origin AS20477 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20477 in the RIR database for the space.671 of 673
Route object: RIR137.118.176.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR137.118.150.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

Route objects with origin AS20477 whose prefix no peer sees AS20477 announce. Many are kept on purpose (backup routes, space announced only in some places).

74.206.88.0/21RADBValid
2001:470:165::/48ARINValid

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.