bgpreport

Network · data from 2026-11-12

AS25674 MT-1392-25674 - Lingo Telecom, LLC

Registry name: MT-1392-25674 - Lingo Telecom, LLC, US · not in PeeringDB

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

Announced routes

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

68.71.112.0/22 No ROA Nonecovered by 68.71.112.0/20 673 100% 67
68.71.112.0/24 No ROA Nonecovered by 68.71.112.0/20 673 100% 67
68.71.113.0/24 No ROA Nonecovered by 68.71.112.0/20 673 100% 67
68.71.114.0/24 No ROA Nonecovered by 68.71.112.0/20 673 100% 67
68.71.120.0/24 No ROA Nonecovered by 68.71.112.0/20 673 100% 67
68.71.121.0/24 No ROA Nonecovered by 68.71.112.0/20 673 100% 67
64.195.133.0/24 No ROA Nonecovered by 64.195.128.0/21 672 100% 67
64.195.140.0/24 No ROA Nonecovered by 64.195.136.0/21 672 100% 67
64.195.142.0/24 No ROA Nonecovered by 64.195.136.0/21 672 100% 67
68.71.116.0/24 No ROA Nonecovered by 68.71.112.0/20 672 100% 67
68.71.119.0/24 No ROA Nonecovered by 68.71.112.0/20 672 100% 67
68.71.120.0/23 No ROA Nonecovered by 68.71.112.0/20 672 100% 67
68.71.124.0/24 No ROA Nonecovered by 68.71.112.0/20 672 100% 67
68.71.126.0/24 No ROA Nonecovered by 68.71.112.0/20 672 100% 67
64.194.212.0/24 No ROA Other IRR onlyNTTCOM 673 100% 67
8.12.76.0/24 No ROA Other IRR onlyNTTCOM 672 100% 67
64.194.139.0/24 No ROA Other IRR onlyNTTCOM 672 100% 67
64.194.211.0/24 No ROA Other IRR onlyNTTCOM 672 100% 67
64.200.128.0/24 No ROA Other IRR onlyNTTCOM 672 100% 67
206.223.103.0/24 No ROA Other IRR onlyNTTCOM 672 100% 67

AS-SET

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

  • ROA: none20
  • Route object: none14
  • Route object: RIR6
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
ROA: none68.71.112.0/22No ROA covers it. Add a ROA for AS25674, maxLength 22.673 of 673
Route object: none68.71.112.0/22No route object for it. A route object for 68.71.112.0/20 with origin AS25674 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25674 in the RIR database for the space.673 of 673
ROA: none68.71.112.0/24No ROA covers it. Add a ROA for AS25674, maxLength 24.673 of 673
Route object: none68.71.112.0/24No route object for it. A route object for 68.71.112.0/20 with origin AS25674 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25674 in the RIR database for the space.673 of 673
ROA: none68.71.113.0/24No ROA covers it. Add a ROA for AS25674, maxLength 24.673 of 673
Route object: none68.71.113.0/24No route object for it. A route object for 68.71.112.0/20 with origin AS25674 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25674 in the RIR database for the space.673 of 673
ROA: none68.71.114.0/24No ROA covers it. Add a ROA for AS25674, maxLength 24.673 of 673
Route object: none68.71.114.0/24No route object for it. A route object for 68.71.112.0/20 with origin AS25674 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25674 in the RIR database for the space.673 of 673
ROA: none68.71.120.0/24No ROA covers it. Add a ROA for AS25674, maxLength 24.673 of 673
Route object: none68.71.120.0/24No route object for it. A route object for 68.71.112.0/20 with origin AS25674 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25674 in the RIR database for the space.673 of 673
ROA: none68.71.121.0/24No ROA covers it. Add a ROA for AS25674, maxLength 24.673 of 673
Route object: none68.71.121.0/24No route object for it. A route object for 68.71.112.0/20 with origin AS25674 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25674 in the RIR database for the space.673 of 673
ROA: none64.195.133.0/24No ROA covers it. Add a ROA for AS25674, maxLength 24.672 of 673
Route object: none64.195.133.0/24No route object for it. A route object for 64.195.128.0/21 with origin AS25674 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25674 in the RIR database for the space.672 of 673
ROA: none64.195.140.0/24No ROA covers it. Add a ROA for AS25674, maxLength 24.672 of 673
Route object: none64.195.140.0/24No route object for it. A route object for 64.195.136.0/21 with origin AS25674 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25674 in the RIR database for the space.672 of 673
ROA: none64.195.142.0/24No ROA covers it. Add a ROA for AS25674, maxLength 24.672 of 673
Route object: none64.195.142.0/24No route object for it. A route object for 64.195.136.0/21 with origin AS25674 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25674 in the RIR database for the space.672 of 673
ROA: none68.71.116.0/24No ROA covers it. Add a ROA for AS25674, maxLength 24.672 of 673
Route object: none68.71.116.0/24No route object for it. A route object for 68.71.112.0/20 with origin AS25674 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25674 in the RIR database for the space.672 of 673
ROA: none68.71.119.0/24No ROA covers it. Add a ROA for AS25674, maxLength 24.672 of 673
Route object: none68.71.119.0/24No route object for it. A route object for 68.71.112.0/20 with origin AS25674 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25674 in the RIR database for the space.672 of 673
ROA: none68.71.120.0/23No ROA covers it. Add a ROA for AS25674, maxLength 23.672 of 673
Route object: none68.71.120.0/23No route object for it. A route object for 68.71.112.0/20 with origin AS25674 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25674 in the RIR database for the space.672 of 673
ROA: none68.71.124.0/24No ROA covers it. Add a ROA for AS25674, maxLength 24.672 of 673
Route object: none68.71.124.0/24No route object for it. A route object for 68.71.112.0/20 with origin AS25674 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25674 in the RIR database for the space.672 of 673
ROA: none68.71.126.0/24No ROA covers it. Add a ROA for AS25674, maxLength 24.672 of 673
Route object: none68.71.126.0/24No route object for it. A route object for 68.71.112.0/20 with origin AS25674 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25674 in the RIR database for the space.672 of 673
ROA: none64.194.212.0/24No ROA covers it. Add a ROA for AS25674, maxLength 24.673 of 673
Route object: RIR64.194.212.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
ROA: none8.12.76.0/24No ROA covers it. Add a ROA for AS25674, maxLength 24.672 of 673
Route object: RIR8.12.76.0/24Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673
ROA: none64.194.139.0/24No ROA covers it. Add a ROA for AS25674, maxLength 24.672 of 673
Route object: RIR64.194.139.0/24Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673
ROA: none64.194.211.0/24No ROA covers it. Add a ROA for AS25674, maxLength 24.672 of 673
Route object: RIR64.194.211.0/24Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673
ROA: none64.200.128.0/24No ROA covers it. Add a ROA for AS25674, maxLength 24.672 of 673
Route object: RIR64.200.128.0/24Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673
ROA: none206.223.103.0/24No ROA covers it. Add a ROA for AS25674, maxLength 24.672 of 673
Route object: RIR206.223.103.0/24Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

8.14.115.0/24NTTCOMNo ROA
8.19.146.0/24NTTCOMNo ROA
64.195.128.0/21NTTCOMNo ROA
64.195.135.0/24NTTCOMNo ROA
64.195.136.0/21NTTCOMNo ROA
68.71.112.0/20NTTCOMNo ROA
68.71.122.0/23NTTCOMNo ROA
68.71.125.0/24RADBNo ROA
204.9.192.0/24NTTCOMNo ROA

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.