Network · data from 2026-11-12

AS49345 AzLink-AS BEEONLINE OJSC

Registry name: AzLink-AS BEEONLINE OJSC, AZ · not in PeeringDB

20IPv4 routes 100.0% RPKI valid · 95.0% with a route object

0IPv6 routes

0RPKI invalid 0 origin · 0 maxLength

0No ROA 1 with no route object for this origin

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

3Route objects not announced registered with origin AS49345, seen from no peer

Announced routes

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


85.132.102.0/23	Valid	None	673 100%	66
31.171.1.0/24	Valid	RIR databaseRIPE	673 100%	66
31.171.2.0/24	Valid	RIR databaseRIPE	673 100%	66
31.171.41.0/24	Valid	RIR databaseRIPE	673 100%	66
31.171.44.0/24	Valid	RIR databaseRIPE	673 100%	66
31.171.125.0/24	Valid	RIR databaseRIPE	673 100%	66
94.20.25.0/24	Valid	RIR databaseRIPE	673 100%	66
94.20.55.0/24	Valid	RIR databaseRIPE	673 100%	66
94.20.66.0/23	Valid	RIR databaseRIPE	673 100%	66
94.20.87.0/24	Valid	RIR databaseRIPE	673 100%	66
94.20.100.0/24	Valid	RIR databaseRIPE	673 100%	66
94.20.101.0/24	Valid	RIR databaseRIPE	673 100%	66
94.20.102.0/23	Valid	RIR databaseRIPE	673 100%	66
94.20.124.0/22	Valid	RIR databaseRIPE	673 100%	66
94.20.139.0/24	Valid	RIR databaseRIPE	673 100%	66
94.20.162.0/24	Valid	RIR databaseRIPE	673 100%	66
94.20.190.0/24	Valid	RIR databaseRIPE	673 100%	66
94.20.191.0/24	Valid	RIR databaseRIPE	673 100%	66
94.20.247.0/24	Valid	RIR databaseRIPE	673 100%	66
94.20.251.0/24	Valid	RIR databaseRIPE	673 100%	66

AS-SET

AS49345 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 4 are in fix.csv.

Route object: none1
Route object: not announced3

Change	Prefix or set	Detail	Full-table peers
Route object: none	85.132.102.0/23	No route object for it. Add a route object with origin AS49345 in the RIR database for the space.	673 of 673

Change

Prefix or set

Detail

Full-table peers

Route object: none

85.132.102.0/23

No route object for it. Add a route object with origin AS49345 in the RIR database for the space.

673 of 673

Route objects not announced

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


85.132.102.0/24	RIPE	Invalid: maxLength
85.132.103.0/24	RIPE	Invalid: maxLength
94.20.176.0/24	RIPE	Invalid: origin

85.132.102.0/24

RIPE

Invalid: maxLength

85.132.103.0/24

RIPE

Invalid: maxLength

94.20.176.0/24

RIPE

Invalid: origin

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.