Network · data from 2026-11-12

AS219010 Prosto-AS Prosto Solution LLC

Registry name: Prosto-AS Prosto Solution LLC, GE · not in PeeringDB

24IPv4 routes 95.8% RPKI valid · 95.8% with a route object

0IPv6 routes

1RPKI invalid 1 origin · 0 maxLength

0No ROA 1 with no route object for this origin

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

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

Announced routes

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


163.5.119.0/24	Invalid: origin	Other origin only	3 0%low visibility	1
13.143.148.0/24	Valid	RIR databaseRIPE	673 100%	67
87.120.68.0/24	Valid	RIR databaseRIPE	673 100%	67
104.143.223.0/24	Valid	RIR databaseRIPE	673 100%	67
179.254.105.0/24	Valid	RIR databaseRIPE	673 100%	67
193.124.119.0/24	Valid	RIR databaseRIPE	673 100%	67
194.87.53.0/24	Valid	RIR databaseRIPE	673 100%	67
194.87.59.0/24	Valid	RIR databaseRIPE	673 100%	66
194.87.142.0/24	Valid	RIR databaseRIPE	673 100%	67
195.58.33.0/24	Valid	RIR databaseRIPE	673 100%	67
195.133.72.0/24	Valid	RIR databaseRIPE	673 100%	67
79.182.189.0/24	Valid	RIR databaseRADB, RIPE	672 100%	66
179.236.142.0/24	Valid	RIR databaseRIPE	672 100%	66
179.253.189.0/24	Valid	RIR databaseRIPE	672 100%	66
185.87.24.0/24	Valid	RIR databaseRIPE	672 100%	67
201.58.159.0/24	Valid	RIR databaseRIPE	672 100%	66
201.58.171.0/24	Valid	RIR databaseRIPE	672 100%	66
89.125.97.0/24	Valid	RIR databaseRIPE	671 100%	67
86.62.52.0/24	Valid	RIR databaseRIPE	670 100%	67
88.218.80.0/24	Valid	RIR databaseRIPE	670 100%	67
45.130.186.0/24	Valid	RIR databaseRIPE	669 99%	67
88.218.239.0/24	Valid	RIR databaseRIPE	669 99%	67
80.243.228.0/24	Valid	RIR databaseRIPE	668 99%	67
13.143.144.0/24	Valid	RIR databaseRIPE	652 97%	66

163.5.119.0/24

Invalid: origin

Other origin only

3 0%low visibility

13.143.148.0/24

Valid

RIR databaseRIPE

673 100%

87.120.68.0/24

Valid

RIR databaseRIPE

673 100%

104.143.223.0/24

Valid

RIR databaseRIPE

673 100%

179.254.105.0/24

Valid

RIR databaseRIPE

673 100%

193.124.119.0/24

Valid

RIR databaseRIPE

673 100%

194.87.53.0/24

Valid

RIR databaseRIPE

673 100%

194.87.59.0/24

Valid

RIR databaseRIPE

673 100%

194.87.142.0/24

Valid

RIR databaseRIPE

673 100%

195.58.33.0/24

Valid

RIR databaseRIPE

673 100%

195.133.72.0/24

Valid

RIR databaseRIPE

673 100%

79.182.189.0/24

Valid

RIR databaseRADB, RIPE

672 100%

179.236.142.0/24

Valid

RIR databaseRIPE

672 100%

179.253.189.0/24

Valid

RIR databaseRIPE

672 100%

185.87.24.0/24

Valid

RIR databaseRIPE

672 100%

201.58.159.0/24

Valid

RIR databaseRIPE

672 100%

201.58.171.0/24

Valid

RIR databaseRIPE

672 100%

89.125.97.0/24

Valid

RIR databaseRIPE

671 100%

86.62.52.0/24

Valid

RIR databaseRIPE

670 100%

88.218.80.0/24

Valid

RIR databaseRIPE

670 100%

45.130.186.0/24

Valid

RIR databaseRIPE

669 99%

88.218.239.0/24

Valid

RIR databaseRIPE

669 99%

80.243.228.0/24

Valid

RIR databaseRIPE

668 99%

13.143.144.0/24

Valid

RIR databaseRIPE

652 97%

AS-SET

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

ROA: origin1
Route object: none1
Route object: not announced2

Change	Prefix or set	Detail	Full-table peers
ROA: origin	163.5.119.0/24	ROAs covering it name AS20473, not AS219010. If AS219010 should announce it, add a ROA for AS219010.	3 of 673
Route object: none	163.5.119.0/24	Route objects for it name AS20473. Add a route object with origin AS219010 in the RIR database for the space.	3 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: origin

163.5.119.0/24

ROAs covering it name AS20473, not AS219010. If AS219010 should announce it, add a ROA for AS219010.

3 of 673

Route object: none

163.5.119.0/24

Route objects for it name AS20473. Add a route object with origin AS219010 in the RIR database for the space.

3 of 673

Route objects not announced

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


45.88.66.0/24	RIPE	Valid
78.17.127.0/24	RIPE	Valid

45.88.66.0/24

RIPE

Valid

78.17.127.0/24

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.