Network · data from 2026-11-12

AS219084 TaylanBelce Belce Taylan

Registry name: TaylanBelce Belce Taylan, BE · not in PeeringDB

4IPv4 routes 25.0% RPKI valid · 25.0% with a route object

0IPv6 routes

3RPKI invalid 3 origin · 0 maxLength

0No ROA 3 with no route object for this origin

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

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

Announced routes

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


79.172.242.0/24	Invalid: origin	Other origin only	16 2%low visibility	12
141.11.184.0/24	Invalid: origin	Other origin only	14 2%low visibility	10
141.11.94.0/24	Invalid: origin	Other origin only	3 0%low visibility	2
179.253.171.0/24	Valid	RIR databaseRIPE	673 100%	67

79.172.242.0/24

Invalid: origin

Other origin only

16 2%low visibility

141.11.184.0/24

Invalid: origin

Other origin only

14 2%low visibility

141.11.94.0/24

Invalid: origin

Other origin only

3 0%low visibility

179.253.171.0/24

Valid

RIR databaseRIPE

673 100%

AS-SET

AS219084 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 6 are in fix.csv.

ROA: origin3
Route object: none3

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

Change

Prefix or set

Detail

Full-table peers

ROA: origin

79.172.242.0/24

ROAs covering it name AS834, not AS219084. If AS219084 should announce it, add a ROA for AS219084.

16 of 673

Route object: none

79.172.242.0/24

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

16 of 673

ROA: origin

141.11.184.0/24

ROAs covering it name AS834, not AS219084. If AS219084 should announce it, add a ROA for AS219084.

14 of 673

Route object: none

141.11.184.0/24

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

14 of 673

ROA: origin

141.11.94.0/24

ROAs covering it name AS834, not AS219084. If AS219084 should announce it, add a ROA for AS219084.

3 of 673

Route object: none

141.11.94.0/24

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

3 of 673

Route objects not announced

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