Network · data from 2026-11-12

AS271652

Not in the RIR AS name list · not in PeeringDB

3IPv4 routes 0.0% RPKI valid · 33.3% with a route object

0IPv6 routes

0RPKI invalid 0 origin · 0 maxLength

3No ROA 2 with no route object for this origin

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

1Route objects not announced registered with origin AS271652, seen from no peer

Announced routes

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


200.50.148.0/23	No ROA	Nonecovered by 200.50.148.0/22	1 0%low visibility	1
200.50.150.0/23	No ROA	Nonecovered by 200.50.148.0/22	1 0%low visibility	1
200.50.148.0/22	No ROA	Other IRR onlyRADB	3 0%low visibility	3

200.50.148.0/23

No ROA

Nonecovered by 200.50.148.0/22

1 0%low visibility

200.50.150.0/23

No ROA

Nonecovered by 200.50.148.0/22

1 0%low visibility

200.50.148.0/22

No ROA

Other IRR onlyRADB

3 0%low visibility

AS-SET

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

ROA: none3
Route object: none2
Route object: RIR1
Route object: not announced1

Change	Prefix or set	Detail	Full-table peers
ROA: none	200.50.148.0/23	No ROA covers it. Add a ROA for AS271652, maxLength 23.	1 of 673
Route object: none	200.50.148.0/23	No route object for it. A route object for 200.50.148.0/22 with origin AS271652 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271652 in the RIR database for the space.	1 of 673
ROA: none	200.50.150.0/23	No ROA covers it. Add a ROA for AS271652, maxLength 23.	1 of 673
Route object: none	200.50.150.0/23	No route object for it. A route object for 200.50.148.0/22 with origin AS271652 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271652 in the RIR database for the space.	1 of 673
ROA: none	200.50.148.0/22	No ROA covers it. Add a ROA for AS271652, maxLength 22.	3 of 673
Route object: RIR	200.50.148.0/22	Route object only in RADB. Add it in the RIR database for the space.	3 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

200.50.148.0/23

No ROA covers it. Add a ROA for AS271652, maxLength 23.

1 of 673

Route object: none

200.50.148.0/23

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

1 of 673

ROA: none

200.50.150.0/23

No ROA covers it. Add a ROA for AS271652, maxLength 23.

1 of 673

Route object: none

200.50.150.0/23

1 of 673

ROA: none

200.50.148.0/22

No ROA covers it. Add a ROA for AS271652, maxLength 22.

3 of 673

Route object: RIR

200.50.148.0/22

Route object only in RADB. Add it in the RIR database for the space.

3 of 673

Route objects not announced

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


2804:7edc::/32	RADB, TC	No ROA

2804:7edc::/32

RADB, TC

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.