Network · data from 2026-11-12

AS49811 UZLOVAYA-NET Uzlovaya.net Ltd

Registry name: UZLOVAYA-NET Uzlovaya.net Ltd, RU · not in PeeringDB

9IPv4 routes 77.8% RPKI valid · 100.0% with a route object

0IPv6 routes

0RPKI invalid 0 origin · 0 maxLength

2No ROA 0 with no route object for this origin

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

20Route objects not announced registered with origin AS49811, seen from no peer

Announced routes

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


176.124.168.0/22	No ROA	RIR databaseRIPE	673 100%	66
193.24.196.0/22	No ROA	RIR databaseRIPE	673 100%	66
31.148.16.0/22	Valid	RIR databaseRIPE	673 100%	66
31.148.244.0/24	Valid	RIR databaseRIPE	673 100%	66
92.38.44.0/23	Valid	RIR databaseRIPE	673 100%	66
93.170.48.0/23	Valid	RIR databaseRIPE	673 100%	66
93.171.236.0/23	Valid	RIR databaseRIPE	673 100%	66
95.47.52.0/23	Valid	RIR databaseRIPE	673 100%	66
95.47.254.0/23	Valid	RIR databaseRIPE	673 100%	66

AS-SET

AS49811 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 22 are in fix.csv.

ROA: none2
Route object: not announced20

Change	Prefix or set	Detail	Full-table peers
ROA: none	176.124.168.0/22	No ROA covers it. Add a ROA for AS49811, maxLength 22.	673 of 673
ROA: none	193.24.196.0/22	No ROA covers it. Add a ROA for AS49811, maxLength 22.	673 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

176.124.168.0/22

No ROA covers it. Add a ROA for AS49811, maxLength 22.

673 of 673

ROA: none

193.24.196.0/22

No ROA covers it. Add a ROA for AS49811, maxLength 22.

673 of 673

Route objects not announced

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


31.148.16.0/23	RIPE	Valid
31.148.16.0/24	RIPE	Valid
31.148.17.0/24	RIPE	Valid
31.148.18.0/23	RIPE	Valid
31.148.18.0/24	RIPE	Valid
31.148.19.0/24	RIPE	Valid
93.171.236.0/24	RIPE	Valid
93.171.237.0/24	RIPE	Valid
176.124.168.0/23	RIPE	No ROA
176.124.168.0/24	RIPE	No ROA
176.124.169.0/24	RIPE	No ROA
176.124.170.0/23	RIPE	No ROA
176.124.170.0/24	RIPE	No ROA
176.124.171.0/24	RIPE	No ROA
193.24.196.0/23	RIPE	No ROA
193.24.196.0/24	RIPE	No ROA
193.24.197.0/24	RIPE	No ROA
193.24.198.0/23	RIPE	No ROA
193.24.198.0/24	RIPE	No ROA
193.24.199.0/24	RIPE	No ROA

31.148.16.0/23

RIPE

Valid

31.148.16.0/24

RIPE

Valid

31.148.17.0/24

RIPE

Valid

31.148.18.0/23

RIPE

Valid

31.148.18.0/24

RIPE

Valid

31.148.19.0/24

RIPE

Valid

93.171.236.0/24

RIPE

Valid

93.171.237.0/24

RIPE

Valid

176.124.168.0/23

RIPE

No ROA

176.124.168.0/24

RIPE

No ROA

176.124.169.0/24

RIPE

No ROA

176.124.170.0/23

RIPE

No ROA

176.124.170.0/24

RIPE

No ROA

176.124.171.0/24

RIPE

No ROA

193.24.196.0/23

RIPE

No ROA

193.24.196.0/24

RIPE

No ROA

193.24.197.0/24

RIPE

No ROA

193.24.198.0/23

RIPE

No ROA

193.24.198.0/24

RIPE

No ROA

193.24.199.0/24

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.