Network · data from 2026-11-12

AS44128 INTERNET-PRO-AS Internet-Pro LLC

Registry name: INTERNET-PRO-AS Internet-Pro LLC, RU · not in PeeringDB

39IPv4 routes 97.4% RPKI valid · 92.3% with a route object

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

0RPKI invalid 0 origin · 0 maxLength

1No ROA 3 with no route object for this origin

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

6Route objects not announced registered with origin AS44128, seen from no peer

Announced routes

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


91.205.176.0/24	No ROA	RIR databaseRIPE	673 100%	66
213.189.222.0/24	Valid	Nonecovered by 213.189.222.0/23	673 100%	66
89.223.78.0/23	Valid	None	672 100%	66
213.189.223.0/24	Valid	Nonecovered by 213.189.222.0/23	668 99%	67
2.58.124.0/23	Valid	RIR databaseRIPE	673 100%	66
2.58.126.0/23	Valid	RIR databaseRIPE	673 100%	66
5.181.252.0/23	Valid	RIR databaseRIPE	673 100%	66
5.181.254.0/23	Valid	RIR databaseRIPE	673 100%	66
5.182.36.0/23	Valid	RIR databaseRIPE	673 100%	66
5.182.38.0/23	Valid	RIR databaseRIPE	673 100%	66
45.86.39.0/24	Valid	RIR databaseRIPE	673 100%	66
45.86.180.0/23	Valid	RIR databaseRIPE	673 100%	66
45.86.182.0/23	Valid	RIR databaseRIPE	673 100%	66
80.87.96.0/23	Valid	RIR databaseRIPE	673 100%	66
80.87.98.0/23	Valid	RIR databaseRIPE	673 100%	66
80.87.100.0/23	Valid	RIR databaseRIPE	673 100%	66
80.87.101.0/24	Valid	RIR databaseRIPE	673 100%	66
80.87.102.0/23	Valid	RIR databaseRIPE	673 100%	66
80.87.104.0/23	Valid	RIR databaseRIPE	673 100%	66
80.87.106.0/23	Valid	RIR databaseRIPE	673 100%	66
80.87.108.0/23	Valid	RIR databaseRIPE	673 100%	66
80.87.110.0/23	Valid	RIR databaseRIPE	673 100%	66
89.223.76.0/23	Valid	RIR databaseRIPE	673 100%	66
91.201.52.0/24	Valid	RIR databaseRIPE	673 100%	66
91.201.53.0/24	Valid	RIR databaseRIPE	673 100%	66
91.201.54.0/23	Valid	RIR databaseRIPE	673 100%	66
91.226.80.0/23	Valid	RIR databaseRIPE	673 100%	66
91.226.82.0/23	Valid	RIR databaseRIPE	673 100%	66
94.141.100.0/23	Valid	RIR databaseRIPE	673 100%	66
94.141.102.0/23	Valid	RIR databaseRIPE	673 100%	66
185.41.160.0/23	Valid	RIR databaseRIPE	673 100%	66
185.41.162.0/23	Valid	RIR databaseRIPE	673 100%	66
185.93.108.0/23	Valid	RIR databaseRIPE	673 100%	66
185.93.110.0/23	Valid	RIR databaseRIPE	673 100%	66
193.107.236.0/23	Valid	RIR databaseRIPE	673 100%	66
193.107.238.0/23	Valid	RIR databaseRIPE	673 100%	66
213.189.216.0/23	Valid	RIR databaseRIPE	673 100%	66
213.189.218.0/23	Valid	RIR databaseRIPE	673 100%	66
213.189.220.0/23	Valid	RIR databaseRIPE	673 100%	66
2a01:5560::/33	Valid	RIR databaseRIPE	636 100%	68
2a01:5560:8000::/33	Valid	RIR databaseRIPE	636 100%	68

AS-SET

AS44128 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 10 are in fix.csv.

ROA: none1
Route object: none3
Route object: not announced6

Change	Prefix or set	Detail	Full-table peers
ROA: none	91.205.176.0/24	No ROA covers it. Add a ROA for AS44128, maxLength 24.	673 of 673
Route object: none	213.189.222.0/24	No route object for it. A route object for 213.189.222.0/23 with origin AS44128 covers it (filters allowing more-specifics accept it). Add a route object with origin AS44128 in the RIR database for the space.	673 of 673
Route object: none	89.223.78.0/23	No route object for it. Add a route object with origin AS44128 in the RIR database for the space.	672 of 673
Route object: none	213.189.223.0/24	No route object for it. A route object for 213.189.222.0/23 with origin AS44128 covers it (filters allowing more-specifics accept it). Add a route object with origin AS44128 in the RIR database for the space.	668 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

91.205.176.0/24

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

673 of 673

Route object: none

213.189.222.0/24

No route object for it. A route object for 213.189.222.0/23 with origin AS44128 covers it (filters allowing more-specifics accept it). Add a route object with origin AS44128 in the RIR database for the space.

673 of 673

Route object: none

89.223.78.0/23

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

672 of 673

Route object: none

213.189.223.0/24

668 of 673

Route objects not announced

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


89.223.78.0/24	RIPE	Invalid: maxLength
91.201.52.0/23	RIPE	No ROA
91.226.80.0/22	RIPE	No ROA
185.153.94.0/24	RIPE	Valid
193.107.236.0/22	RIPE	No ROA
213.189.222.0/23	RIPE	No ROA

89.223.78.0/24

RIPE

Invalid: maxLength

91.201.52.0/23

RIPE

No ROA

91.226.80.0/22

RIPE

No ROA

185.153.94.0/24

RIPE

Valid

193.107.236.0/22

RIPE

No ROA

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