bgpreport

Network · data from 2026-11-12

AS44364 LVNET-AS LVNET LTD

Registry name: LVNET-AS LVNET LTD, CY · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS44364, 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.
2a09:cc0::/48 Valid Other IRR onlyRADB 636 100% 67
2a09:1240::/48 Valid Other IRR onlyRADB 636 100% 67
2a09:4740::/48 Valid Other IRR onlyRADB 636 100% 67
2a09:47c0::/48 Valid Other IRR onlyRADB 636 100% 67
2a09:9cc0::/48 Valid Other IRR onlyRADB 636 100% 67
2a09:9d40::/48 Valid Other IRR onlyRADB 636 100% 67
2a09:9dc0::/48 Valid Other IRR onlyRADB 636 100% 67
2a09:9e40::/48 Valid Other IRR onlyRADB 636 100% 67
2a09:a080::/48 Valid Other IRR onlyRADB 636 100% 67
2a00:48a0::/29 Valid RIR databaseRIPE 635 100% 67
2a09:cc0::/29 Valid RIR databaseRIPE 635 100% 67
2a09:1240::/29 Valid RIR databaseRIPE 635 100% 67
2a09:4740::/29 Valid RIR databaseRIPE 635 100% 67
2a09:47c0::/29 Valid RIR databaseRIPE 635 100% 67
2a09:7700::/29 Valid RIR databaseRIPE 635 100% 67
2a09:9cc0::/29 Valid RIR databaseRIPE 635 100% 67
2a09:9d40::/29 Valid RIR databaseRIPE 635 100% 67
2a09:9dc0::/29 Valid RIR databaseRIPE 635 100% 67
2a09:9e40::/29 Valid RIR databaseRIPE 635 100% 67
2a09:a080::/29 Valid RIR databaseRIPE 635 100% 67
2a0a:dd80::/29 Valid RIR databaseRIPE 635 100% 67
2a0c:8140::/29 Valid RIR databaseRIPE 635 100% 67
2a0c:fa80::/29 Valid RIR databaseRIPE 635 100% 67
2a0d:5e40::/29 Valid RIR databaseRIPE 635 100% 67
2a0e:83c0::/29 Valid RIR databaseRIPE 635 100% 67
2a10:3cc0::/29 Valid RIR databaseRIPE 633 100% 67
2a10:51c0::/29 Valid RIR databaseRIPE 633 100% 67
2a10:7880::/29 Valid RIR databaseRIPE 633 100% 67
2a11:9080::/29 Valid RIR databaseRIPE 633 100% 67
2a11:9180::/29 Valid RIR databaseRIPE 633 100% 67
2a11:9280::/29 Valid RIR databaseRIPE 633 100% 67
2a11:9680::/29 Valid RIR databaseRIPE 633 100% 67
2a11:a780::/29 Valid RIR databaseRIPE 633 100% 67
2a11:a880::/29 Valid RIR databaseRIPE 633 100% 67
2a11:a980::/29 Valid RIR databaseRIPE 633 100% 67
2a11:b280::/29 Valid RIR databaseRIPE 633 100% 67
2a11:b380::/29 Valid RIR databaseRIPE 633 100% 67
2a11:b480::/29 Valid RIR databaseRIPE 633 100% 67
2a11:d800::/29 Valid RIR databaseRIPE 633 100% 67

AS-SET

AS44364 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 9 are in fix.csv.

  • Route object: RIR9
ChangePrefix or setDetailFull-table peers
Route object: RIR2a09:cc0::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2a09:1240::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2a09:4740::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2a09:47c0::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2a09:9cc0::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2a09:9d40::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2a09:9dc0::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2a09:9e40::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2a09:a080::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636

Route objects not announced

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