bgpreport

Network · data from 2026-11-12

AS394998 LAKELAND-INTERNET

Registry name: LAKELAND-INTERNET - LakeLand Internet LLC, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS394998, 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.
64.255.112.0/23 No ROA Nonecovered by 64.255.112.0/21 1 0%low visibility 1
2607:36c0::/32 No ROA Other IRR onlyRADB 635 100% 69
64.255.112.0/21 No ROA RIR databaseARIN, RADB 671 100% 68
67.199.254.0/24 No ROA RIR databaseARIN, RADB 671 100% 68
141.193.242.0/24 No ROA RIR databaseARIN 671 100% 68
172.111.28.0/22 No ROA RIR databaseARIN 671 100% 68
203.31.221.0/24 No ROA RIR databaseARIN 671 100% 68
203.33.45.0/24 No ROA RIR databaseARIN 671 100% 68
208.69.188.0/22 No ROA RIR databaseARIN, RADB 671 100% 68
209.163.120.0/22 No ROA RIR databaseARIN 671 100% 68

AS-SET

AS394998's PeeringDB record names no 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 15 are in fix.csv.

  • ROA: none10
  • Route object: none1
  • Route object: RIR1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none64.255.112.0/23No ROA covers it. Add a ROA for AS394998, maxLength 23.1 of 673
Route object: none64.255.112.0/23No route object for it. A route object for 64.255.112.0/21 with origin AS394998 covers it (filters allowing more-specifics accept it). Add a route object with origin AS394998 in the RIR database for the space.1 of 673
ROA: none2607:36c0::/32No ROA covers it. Add a ROA for AS394998, maxLength 32.635 of 636
Route object: RIR2607:36c0::/32Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none64.255.112.0/21No ROA covers it. Add a ROA for AS394998, maxLength 21.671 of 673
ROA: none67.199.254.0/24No ROA covers it. Add a ROA for AS394998, maxLength 24.671 of 673
ROA: none141.193.242.0/24No ROA covers it. Add a ROA for AS394998, maxLength 24.671 of 673
ROA: none172.111.28.0/22No ROA covers it. Add a ROA for AS394998, maxLength 22.671 of 673
ROA: none203.31.221.0/24No ROA covers it. Add a ROA for AS394998, maxLength 24.671 of 673
ROA: none203.33.45.0/24No ROA covers it. Add a ROA for AS394998, maxLength 24.671 of 673
ROA: none208.69.188.0/22No ROA covers it. Add a ROA for AS394998, maxLength 22.671 of 673
ROA: none209.163.120.0/22No ROA covers it. Add a ROA for AS394998, maxLength 22.671 of 673

Route objects not announced

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

38.143.171.0/24RADBNo ROA
38.143.172.0/22RADBNo ROA
38.143.173.0/24RADBNo 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.