bgpreport

Network · data from 2026-11-12

AS400589 LTCCONNECT - LTC Connect

Registry name: LTCCONNECT - LTC Connect, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS400589, 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.
66.38.27.0/24 No ROA Nonecovered by 66.38.24.0/22 670 100% 67
66.38.63.0/24 No ROA Other origin only 670 100% 67
74.50.32.0/21 No ROA Other IRR onlyRADB 672 100% 67
66.38.6.0/23 No ROA Other IRR onlyRADB 670 100% 67
66.38.20.0/22 No ROA Other IRR onlyRADB 670 100% 67
66.38.24.0/22 No ROA Other IRR onlyRADB 670 100% 67
66.38.28.0/24 No ROA Other IRR onlyRADB 670 100% 67
66.38.82.0/24 No ROA Other IRR onlyRADB 670 100% 67
209.46.24.0/22 No ROA Other IRR onlyRADB 670 100% 67
209.46.96.0/22 No ROA Other IRR onlyRADB 670 100% 67
216.245.148.0/22 No ROA Other IRR onlyRADB 670 100% 67
74.50.47.0/24 No ROA Other IRR onlyRADB 669 99% 67

AS-SET

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

  • ROA: none12
  • Route object: none2
  • Route object: RIR10
ChangePrefix or setDetailFull-table peers
ROA: none66.38.27.0/24No ROA covers it. Add a ROA for AS400589, maxLength 24.670 of 673
Route object: none66.38.27.0/24No route object for it. A route object for 66.38.24.0/22 with origin AS400589 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400589 in the RIR database for the space.670 of 673
ROA: none66.38.63.0/24No ROA covers it. Add a ROA for AS400589, maxLength 24.670 of 673
Route object: none66.38.63.0/24Route objects for it name AS11979. Add a route object with origin AS400589 in the RIR database for the space.670 of 673
ROA: none74.50.32.0/21No ROA covers it. Add a ROA for AS400589, maxLength 21.672 of 673
Route object: RIR74.50.32.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none66.38.6.0/23No ROA covers it. Add a ROA for AS400589, maxLength 23.670 of 673
Route object: RIR66.38.6.0/23Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none66.38.20.0/22No ROA covers it. Add a ROA for AS400589, maxLength 22.670 of 673
Route object: RIR66.38.20.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none66.38.24.0/22No ROA covers it. Add a ROA for AS400589, maxLength 22.670 of 673
Route object: RIR66.38.24.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none66.38.28.0/24No ROA covers it. Add a ROA for AS400589, maxLength 24.670 of 673
Route object: RIR66.38.28.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none66.38.82.0/24No ROA covers it. Add a ROA for AS400589, maxLength 24.670 of 673
Route object: RIR66.38.82.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none209.46.24.0/22No ROA covers it. Add a ROA for AS400589, maxLength 22.670 of 673
Route object: RIR209.46.24.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none209.46.96.0/22No ROA covers it. Add a ROA for AS400589, maxLength 22.670 of 673
Route object: RIR209.46.96.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none216.245.148.0/22No ROA covers it. Add a ROA for AS400589, maxLength 22.670 of 673
Route object: RIR216.245.148.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none74.50.47.0/24No ROA covers it. Add a ROA for AS400589, maxLength 24.669 of 673
Route object: RIR74.50.47.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673

Route objects not announced

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