Network · data from 2026-11-12

AS219450 VOYAR VOYAR VERIMERKEZI TEKNOLOJILERI LTD. STI

Registry name: VOYAR VOYAR VERIMERKEZI TEKNOLOJILERI LTD. STI, TR · not in PeeringDB

27IPv4 routes 96.3% RPKI valid · 96.3% with a route object

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

1RPKI invalid 1 origin · 0 maxLength

1No ROA 2 with no route object for this origin

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

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

Announced routes

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


5.252.97.0/24	Invalid: origin	Other origin only	2 0%low visibility	2
2a06:c400::/29	No ROA	Other origin only	635 100%	67
5.180.184.0/24	Valid	RIR databaseRIPE	673 100%	67
5.180.185.0/24	Valid	RIR databaseRIPE	673 100%	67
5.180.186.0/24	Valid	RIR databaseRIPE	673 100%	66
5.180.187.0/24	Valid	RIR databaseRIPE	673 100%	67
5.252.96.0/24	Valid	RIR databaseRIPE	673 100%	66
78.135.110.0/24	Valid	RIR databaseRIPE	673 100%	67
83.150.212.0/24	Valid	RIR databaseRIPE	673 100%	67
83.150.213.0/24	Valid	RIR databaseRIPE	673 100%	67
83.150.214.0/24	Valid	RIR databaseRIPE	673 100%	67
83.150.215.0/24	Valid	RIR databaseRIPE	673 100%	67
89.252.188.0/24	Valid	RIR databaseRIPE	673 100%	67
89.252.189.0/24	Valid	RIR databaseRIPE	673 100%	66
89.252.190.0/24	Valid	RIR databaseRIPE	673 100%	67
89.252.191.0/24	Valid	RIR databaseRIPE	673 100%	67
166.0.157.0/24	Valid	RIR databaseARIN	673 100%	66
185.126.216.0/24	Valid	RIR databaseRIPE	673 100%	66
185.126.217.0/24	Valid	RIR databaseRIPE	673 100%	67
185.126.218.0/24	Valid	RIR databaseRIPE	673 100%	67
185.126.219.0/24	Valid	RIR databaseRIPE	673 100%	67
185.179.24.0/24	Valid	RIR databaseRIPE	673 100%	67
185.179.25.0/24	Valid	RIR databaseRIPE	673 100%	66
185.179.26.0/24	Valid	RIR databaseRIPE	673 100%	66
185.179.27.0/24	Valid	RIR databaseRIPE	673 100%	66
188.132.196.0/24	Valid	RIR databaseRIPE	673 100%	66
194.110.169.0/24	Valid	RIR databaseRIPE	673 100%	67
77.93.148.0/24	Valid	RIR databaseRADB, RIPE	672 100%	66

5.252.97.0/24

Invalid: origin

Other origin only

2 0%low visibility

2a06:c400::/29

No ROA

Other origin only

635 100%

5.180.184.0/24

Valid

RIR databaseRIPE

673 100%

5.180.185.0/24

Valid

RIR databaseRIPE

673 100%

5.180.186.0/24

Valid

RIR databaseRIPE

673 100%

5.180.187.0/24

Valid

RIR databaseRIPE

673 100%

5.252.96.0/24

Valid

RIR databaseRIPE

673 100%

78.135.110.0/24

Valid

RIR databaseRIPE

673 100%

83.150.212.0/24

Valid

RIR databaseRIPE

673 100%

83.150.213.0/24

Valid

RIR databaseRIPE

673 100%

83.150.214.0/24

Valid

RIR databaseRIPE

673 100%

83.150.215.0/24

Valid

RIR databaseRIPE

673 100%

89.252.188.0/24

Valid

RIR databaseRIPE

673 100%

89.252.189.0/24

Valid

RIR databaseRIPE

673 100%

89.252.190.0/24

Valid

RIR databaseRIPE

673 100%

89.252.191.0/24

Valid

RIR databaseRIPE

673 100%

166.0.157.0/24

Valid

RIR databaseARIN

673 100%

185.126.216.0/24

Valid

RIR databaseRIPE

673 100%

185.126.217.0/24

Valid

RIR databaseRIPE

673 100%

185.126.218.0/24

Valid

RIR databaseRIPE

673 100%

185.126.219.0/24

Valid

RIR databaseRIPE

673 100%

185.179.24.0/24

Valid

RIR databaseRIPE

673 100%

185.179.25.0/24

Valid

RIR databaseRIPE

673 100%

185.179.26.0/24

Valid

RIR databaseRIPE

673 100%

185.179.27.0/24

Valid

RIR databaseRIPE

673 100%

188.132.196.0/24

Valid

RIR databaseRIPE

673 100%

194.110.169.0/24

Valid

RIR databaseRIPE

673 100%

77.93.148.0/24

Valid

RIR databaseRADB, RIPE

672 100%

AS-SET

AS219450 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
ROA: none1
Route object: none2

Change	Prefix or set	Detail	Full-table peers
ROA: origin	5.252.97.0/24	ROAs covering it name AS216385, not AS219450. If AS219450 should announce it, add a ROA for AS219450.	2 of 673
Route object: none	5.252.97.0/24	Route objects for it name AS216385. Add a route object with origin AS219450 in the RIR database for the space.	2 of 673
ROA: none	2a06:c400::/29	No ROA covers it. Add a ROA for AS219450, maxLength 29.	635 of 636
Route object: none	2a06:c400::/29	Route objects for it name AS203576. Add a route object with origin AS219450 in the RIR database for the space.	635 of 636

Change

Prefix or set

Detail

Full-table peers

ROA: origin

5.252.97.0/24

ROAs covering it name AS216385, not AS219450. If AS219450 should announce it, add a ROA for AS219450.

2 of 673

Route object: none

5.252.97.0/24

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

2 of 673

ROA: none

2a06:c400::/29

No ROA covers it. Add a ROA for AS219450, maxLength 29.

635 of 636

Route object: none

2a06:c400::/29

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

635 of 636

Route objects not announced

Every route object with origin AS219450 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.