bgpreport

Network · data from 2026-11-12

AS396990 CTS-MONTICELLO - Monticello - Wayne County Telecommunication Board

Registry name: CTS-MONTICELLO - Monticello - Wayne County Telecommunication Board, US · not in PeeringDB

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

Announced routes

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

2602:fcda::/36 No ROA Other origin only 634 100% 69
23.188.64.0/24 No ROA Other IRR onlyRADB 671 100% 68
38.79.160.0/22 No ROA Other IRR onlyRADB 671 100% 68
38.79.160.0/23 No ROA Other IRR onlyRADB 671 100% 68
161.199.244.0/24 No ROA Other IRR onlyRADB 671 100% 68
199.30.74.0/24 No ROA Other IRR onlyRADB 671 100% 68
23.188.65.0/24 No ROA Other IRR onlyRADB 669 99% 68
23.188.66.0/24 No ROA Other IRR onlyRADB 669 99% 68
38.79.162.0/23 No ROA Other IRR onlyRADB 669 99% 68
104.255.80.0/22 No ROA Other IRR onlyRADB 669 99% 68
2604:ba40::/32 No ROA Other IRR onlyRADB 635 100% 70
162.155.42.0/24 Valid Other IRR onlyRADB 671 100% 68

AS-SET

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

  • ROA: none11
  • Route object: none1
  • Route object: RIR11
ChangePrefix or setDetailFull-table peers
ROA: none2602:fcda::/36No ROA covers it. Add a ROA for AS396990, maxLength 36.634 of 636
Route object: none2602:fcda::/36Route objects for it name AS54142. Add a route object with origin AS396990 in the RIR database for the space.634 of 636
ROA: none23.188.64.0/24No ROA covers it. Add a ROA for AS396990, maxLength 24.671 of 673
Route object: RIR23.188.64.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none38.79.160.0/22No ROA covers it. Add a ROA for AS396990, maxLength 22.671 of 673
Route object: RIR38.79.160.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none38.79.160.0/23No ROA covers it. Add a ROA for AS396990, maxLength 23.671 of 673
Route object: RIR38.79.160.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none161.199.244.0/24No ROA covers it. Add a ROA for AS396990, maxLength 24.671 of 673
Route object: RIR161.199.244.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none199.30.74.0/24No ROA covers it. Add a ROA for AS396990, maxLength 24.671 of 673
Route object: RIR199.30.74.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none23.188.65.0/24No ROA covers it. Add a ROA for AS396990, maxLength 24.669 of 673
Route object: RIR23.188.65.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none23.188.66.0/24No ROA covers it. Add a ROA for AS396990, maxLength 24.669 of 673
Route object: RIR23.188.66.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none38.79.162.0/23No ROA covers it. Add a ROA for AS396990, maxLength 23.669 of 673
Route object: RIR38.79.162.0/23Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none104.255.80.0/22No ROA covers it. Add a ROA for AS396990, maxLength 22.669 of 673
Route object: RIR104.255.80.0/22Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none2604:ba40::/32No ROA covers it. Add a ROA for AS396990, maxLength 32.635 of 636
Route object: RIR2604:ba40::/32Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR162.155.42.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 AS396990 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.