Network · data from 2026-11-12

AS201813 Starhost

Registry name: Contrust-Solutions Contrust Solutions S.R.L., MD · PeeringDB

5IPv4 routes 40.0% RPKI valid · 40.0% with a route object

0IPv6 routes

1RPKI invalid 1 origin · 0 maxLength

2No ROA 3 with no route object for this origin

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

0Route objects not announced registered with origin AS201813, seen from no peer

Announced routes

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


195.178.146.0/24	Invalid: origin	Other origin only	25 4%low visibility	23
104.243.250.0/24	No ROA	Other origin only	669 99%	67
206.123.144.0/24	No ROA	Other origin only	652 97%	67
109.160.40.0/24	Valid	RIR databaseRIPE	669 99%	67
94.26.69.0/24	Valid	RIR databaseRIPE	668 99%	67

195.178.146.0/24

Invalid: origin

Other origin only

25 4%low visibility

104.243.250.0/24

No ROA

Other origin only

669 99%

206.123.144.0/24

No ROA

Other origin only

652 97%

109.160.40.0/24

Valid

RIR databaseRIPE

669 99%

94.26.69.0/24

Valid

RIR databaseRIPE

668 99%

AS-SET

AS201813's PeeringDB record names no 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 6 are in fix.csv.

ROA: origin1
ROA: none2
Route object: none3

Change	Prefix or set	Detail	Full-table peers
ROA: origin	195.178.146.0/24	ROAs covering it name AS3319, not AS201813. If AS201813 should announce it, add a ROA for AS201813.	25 of 673
Route object: none	195.178.146.0/24	Route objects for it name AS3319. Add a route object with origin AS201813 in the RIR database for the space.	25 of 673
ROA: none	104.243.250.0/24	No ROA covers it. Add a ROA for AS201813, maxLength 24.	669 of 673
Route object: none	104.243.250.0/24	Route objects for it name AS9009, AS206264. Add a route object with origin AS201813 in the RIR database for the space.	669 of 673
ROA: none	206.123.144.0/24	No ROA covers it. Add a ROA for AS201813, maxLength 24.	652 of 673
Route object: none	206.123.144.0/24	Route objects for it name AS36351. Add a route object with origin AS201813 in the RIR database for the space.	652 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: origin

195.178.146.0/24

ROAs covering it name AS3319, not AS201813. If AS201813 should announce it, add a ROA for AS201813.

25 of 673

Route object: none

195.178.146.0/24

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

25 of 673

ROA: none

104.243.250.0/24

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

669 of 673

Route object: none

104.243.250.0/24

Route objects for it name AS9009, AS206264. Add a route object with origin AS201813 in the RIR database for the space.

669 of 673

ROA: none

206.123.144.0/24

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

652 of 673

Route object: none

206.123.144.0/24

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

652 of 673

Route objects not announced

Every route object with origin AS201813 is announced.

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.