Network · data from 2026-11-12

AS39246 LIULINNET Optical Structural Network Ltd.

Registry name: LIULINNET Optical Structural Network Ltd., BG · not in PeeringDB

51IPv4 routes 98.0% RPKI valid · 100.0% with a route object

0IPv6 routes

0RPKI invalid 0 origin · 0 maxLength

1No ROA 0 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

23Route objects not announced registered with origin AS39246, seen from no peer

Announced routes

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


109.121.189.0/24	No ROA	RIR databaseRIPE	673 100%	66
31.193.189.0/24	Valid	RIR databaseRIPE	673 100%	66
62.192.132.0/24	Valid	RIR databaseRIPE	673 100%	66
62.192.133.0/24	Valid	RIR databaseRIPE	673 100%	66
85.187.204.0/24	Valid	RIR databaseRIPE	673 100%	66
85.187.205.0/24	Valid	RIR databaseRIPE	673 100%	66
85.187.206.0/24	Valid	RIR databaseRIPE	673 100%	66
109.121.129.0/24	Valid	RIR databaseRIPE	673 100%	66
109.121.130.0/24	Valid	RIR databaseRIPE	673 100%	66
109.121.131.0/24	Valid	RIR databaseRIPE	673 100%	66
109.121.132.0/24	Valid	RIR databaseRIPE	673 100%	66
109.121.148.0/24	Valid	RIR databaseRIPE	673 100%	66
109.121.149.0/24	Valid	RIR databaseRIPE	673 100%	66
109.121.150.0/24	Valid	RIR databaseRIPE	673 100%	66
109.121.151.0/24	Valid	RIR databaseRIPE	673 100%	66
109.121.154.0/24	Valid	RIR databaseRIPE	673 100%	66
109.121.155.0/24	Valid	RIR databaseRIPE	673 100%	66
109.121.156.0/24	Valid	RIR databaseRIPE	673 100%	66
109.121.157.0/24	Valid	RIR databaseRIPE	673 100%	66
109.121.158.0/24	Valid	RIR databaseRIPE	673 100%	66
109.121.164.0/24	Valid	RIR databaseRIPE	673 100%	66
109.121.165.0/24	Valid	RIR databaseRIPE	673 100%	66
109.121.167.0/24	Valid	RIR databaseRIPE	673 100%	66
109.121.168.0/24	Valid	RIR databaseRIPE	673 100%	66
109.121.169.0/24	Valid	RIR databaseRIPE	673 100%	66
109.121.170.0/24	Valid	RIR databaseRIPE	673 100%	66
109.121.171.0/24	Valid	RIR databaseRIPE	673 100%	66
109.121.176.0/24	Valid	RIR databaseRIPE	673 100%	66
109.121.177.0/24	Valid	RIR databaseRIPE	673 100%	66
109.121.178.0/24	Valid	RIR databaseRIPE	673 100%	66
109.121.179.0/24	Valid	RIR databaseRIPE	673 100%	66
109.121.184.0/24	Valid	RIR databaseRIPE	673 100%	66
109.121.185.0/24	Valid	RIR databaseRIPE	673 100%	66
109.121.186.0/24	Valid	RIR databaseRIPE	673 100%	66
109.121.187.0/24	Valid	RIR databaseRIPE	673 100%	66
109.121.188.0/24	Valid	RIR databaseRIPE	673 100%	66
77.78.128.0/24	Valid	RIR databaseRIPE	672 100%	66
77.78.129.0/24	Valid	RIR databaseRIPE	672 100%	66
77.78.131.0/24	Valid	RIR databaseRIPE	672 100%	66
77.78.132.0/24	Valid	RIR databaseRIPE	672 100%	66
77.78.133.0/24	Valid	RIR databaseRIPE	672 100%	66
77.78.134.0/24	Valid	RIR databaseRIPE	672 100%	66
77.78.135.0/24	Valid	RIR databaseRIPE	672 100%	66
77.78.137.0/24	Valid	RIR databaseRIPE	672 100%	66
77.78.138.0/24	Valid	RIR databaseRIPE	672 100%	66
77.78.139.0/24	Valid	RIR databaseRIPE	672 100%	66
77.78.140.0/24	Valid	RIR databaseRIPE	672 100%	66
77.78.141.0/24	Valid	RIR databaseRIPE	672 100%	66
77.78.142.0/24	Valid	RIR databaseRIPE	672 100%	66
77.78.143.0/24	Valid	RIR databaseRIPE	672 100%	66
77.78.136.0/24	Valid	RIR databaseRIPE	669 99%	66

AS-SET

AS39246 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: none1
Route object: not announced23

Change	Prefix or set	Detail	Full-table peers
ROA: none	109.121.189.0/24	No ROA covers it. Add a ROA for AS39246, maxLength 24.	673 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

109.121.189.0/24

No ROA covers it. Add a ROA for AS39246, maxLength 24.

673 of 673

Route objects not announced

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


62.192.132.0/22	RIPE	No ROA
62.192.132.0/23	RIPE	No ROA
62.192.134.0/23	RIPE	No ROA
62.192.134.0/24	RIPE	No ROA
62.192.135.0/24	RIPE	No ROA
77.78.128.0/20	RIPE	No ROA
77.78.130.0/24	RIPE	Valid
77.78.144.0/24	RIPE	Valid
85.187.207.0/24	RIPE	Valid
85.187.250.0/24	RIPE	Valid
85.187.251.0/24	RIPE	Valid
85.187.252.0/24	RIPE	Valid
85.187.253.0/24	RIPE	Valid
109.121.140.0/24	RIPE	No ROA
109.121.141.0/24	RIPE	No ROA
109.121.146.0/24	RIPE	No ROA
109.121.152.0/23	RIPE	No ROA
109.121.163.0/24	RIPE	No ROA
109.121.172.0/24	RIPE	No ROA
109.121.173.0/24	RIPE	No ROA
109.121.174.0/24	RIPE	No ROA
109.121.180.0/22	RIPE	No ROA
109.121.190.0/23	RIPE	No ROA

62.192.132.0/22

RIPE

No ROA

62.192.132.0/23

RIPE

No ROA

62.192.134.0/23

RIPE

No ROA

62.192.134.0/24

RIPE

No ROA

62.192.135.0/24

RIPE

No ROA

77.78.128.0/20

RIPE

No ROA

77.78.130.0/24

RIPE

Valid

77.78.144.0/24

RIPE

Valid

85.187.207.0/24

RIPE

Valid

85.187.250.0/24

RIPE

Valid

85.187.251.0/24

RIPE

Valid

85.187.252.0/24

RIPE

Valid

85.187.253.0/24

RIPE

Valid

109.121.140.0/24

RIPE

No ROA

109.121.141.0/24

RIPE

No ROA

109.121.146.0/24

RIPE

No ROA

109.121.152.0/23

RIPE

No ROA

109.121.163.0/24

RIPE

No ROA

109.121.172.0/24

RIPE

No ROA

109.121.173.0/24

RIPE

No ROA

109.121.174.0/24

RIPE

No ROA

109.121.180.0/22

RIPE

No ROA

109.121.190.0/23

RIPE

No 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.