Network · data from 2026-11-12

AS49531 NETCOM-R-AS "NetCom-R" LLC

Registry name: NETCOM-R-AS "NetCom-R" LLC, RU · not in PeeringDB

69IPv4 routes 100.0% RPKI valid · 98.6% with a route object

1IPv6 routes 100.0% RPKI valid · 100.0% with a route object

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

2Route objects not announced registered with origin AS49531, seen from no peer

Announced routes

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


94.159.0.0/17	Valid	None	672 100%	66
91.214.204.0/22	Valid	RIR databaseRIPE	671 100%	68
93.92.32.0/21	Valid	RIR databaseRIPE	671 100%	68
93.92.32.0/24	Valid	RIR databaseRIPE	671 100%	68
93.92.33.0/24	Valid	RIR databaseRIPE	671 100%	68
93.92.34.0/23	Valid	RIR databaseRIPE	671 100%	68
93.92.36.0/23	Valid	RIR databaseRIPE	671 100%	68
93.92.38.0/23	Valid	RIR databaseRIPE	671 100%	68
93.186.48.0/20	Valid	RIR databaseRIPE	671 100%	68
93.186.48.0/23	Valid	RIR databaseRIPE	671 100%	68
93.186.50.0/23	Valid	RIR databaseRIPE	671 100%	68
93.186.52.0/23	Valid	RIR databaseRIPE	671 100%	68
93.186.54.0/23	Valid	RIR databaseRIPE	671 100%	68
93.186.56.0/23	Valid	RIR databaseRIPE	671 100%	68
93.186.58.0/23	Valid	RIR databaseRIPE	671 100%	68
93.186.60.0/23	Valid	RIR databaseRIPE	671 100%	68
93.186.62.0/23	Valid	RIR databaseRIPE	671 100%	68
94.159.0.0/18	Valid	RIR databaseRIPE	671 100%	68
94.159.0.0/23	Valid	RIR databaseRIPE	671 100%	68
94.159.2.0/23	Valid	RIR databaseRIPE	671 100%	68
94.159.4.0/23	Valid	RIR databaseRIPE	671 100%	68
94.159.6.0/23	Valid	RIR databaseRIPE	671 100%	68
94.159.8.0/23	Valid	RIR databaseRIPE	671 100%	68
94.159.10.0/23	Valid	RIR databaseRIPE	671 100%	68
94.159.12.0/23	Valid	RIR databaseRIPE	671 100%	68
94.159.14.0/23	Valid	RIR databaseRIPE	671 100%	68
94.159.16.0/23	Valid	RIR databaseRIPE	671 100%	68
94.159.18.0/23	Valid	RIR databaseRIPE	671 100%	68
94.159.20.0/23	Valid	RIR databaseRIPE	671 100%	68
94.159.22.0/23	Valid	RIR databaseRIPE	671 100%	68
94.159.24.0/23	Valid	RIR databaseRIPE	671 100%	68
94.159.26.0/23	Valid	RIR databaseRIPE	671 100%	68
94.159.28.0/23	Valid	RIR databaseRIPE	671 100%	68
94.159.30.0/23	Valid	RIR databaseRIPE	671 100%	68
94.159.32.0/23	Valid	RIR databaseRIPE	671 100%	68
94.159.34.0/23	Valid	RIR databaseRIPE	671 100%	68
94.159.36.0/23	Valid	RIR databaseRIPE	671 100%	68
94.159.38.0/23	Valid	RIR databaseRIPE	671 100%	68
94.159.40.0/23	Valid	RIR databaseRIPE	671 100%	68
94.159.42.0/23	Valid	RIR databaseRIPE	671 100%	68
94.159.44.0/23	Valid	RIR databaseRIPE	671 100%	68
94.159.46.0/23	Valid	RIR databaseRIPE	671 100%	68
94.159.48.0/23	Valid	RIR databaseRIPE	671 100%	68
94.159.50.0/23	Valid	RIR databaseRIPE	671 100%	68
94.159.52.0/23	Valid	RIR databaseRIPE	671 100%	68
94.159.54.0/23	Valid	RIR databaseRIPE	671 100%	68
94.159.56.0/23	Valid	RIR databaseRIPE	671 100%	68
94.159.58.0/23	Valid	RIR databaseRIPE	671 100%	68
94.159.60.0/23	Valid	RIR databaseRIPE	671 100%	68
94.159.62.0/23	Valid	RIR databaseRIPE	671 100%	68
94.159.64.0/19	Valid	RIR databaseRIPE	671 100%	68
94.159.64.0/23	Valid	RIR databaseRIPE	671 100%	68
94.159.66.0/23	Valid	RIR databaseRIPE	671 100%	68
94.159.68.0/23	Valid	RIR databaseRIPE	671 100%	68
94.159.70.0/24	Valid	RIR databaseRIPE	671 100%	68
94.159.72.0/23	Valid	RIR databaseRIPE	671 100%	68
94.159.74.0/23	Valid	RIR databaseRIPE	671 100%	68
94.159.76.0/23	Valid	RIR databaseRIPE	671 100%	68
94.159.78.0/23	Valid	RIR databaseRIPE	671 100%	68
94.159.80.0/23	Valid	RIR databaseRIPE	671 100%	68
94.159.82.0/23	Valid	RIR databaseRIPE	671 100%	68
94.159.85.0/24	Valid	RIR databaseRIPE	671 100%	68
94.159.88.0/22	Valid	RIR databaseRIPE	671 100%	68
94.159.92.0/24	Valid	RIR databaseRIPE	671 100%	68
94.159.118.0/24	Valid	RIR databaseRIPE	671 100%	68
94.159.119.0/24	Valid	RIR databaseRIPE	671 100%	68
94.159.120.0/22	Valid	RIR databaseRIPE	671 100%	68
94.159.124.0/22	Valid	RIR databaseRIPE	671 100%	68
185.42.108.0/22	Valid	RIR databaseRIPE	671 100%	68
2a04:8f00::/29	Valid	RIR databaseRIPE	635 100%	69

AS-SET

AS49531 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 3 are in fix.csv.

Route object: none1
Route object: not announced2

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

Change

Prefix or set

Detail

Full-table peers

Route object: none

94.159.0.0/17

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

672 of 673

Route objects not announced

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


94.159.80.0/24	RIPE	Invalid: maxLength
94.159.112.0/21	RIPE	Valid

94.159.80.0/24

RIPE

Invalid: maxLength

94.159.112.0/21

RIPE

Valid

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.