Network · data from 2026-11-12

AS267102

Not in the RIR AS name list · not in PeeringDB

0IPv4 routes

3IPv6 routes 0.0% RPKI valid · 100.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

3No ROA 0 with no route object for this origin

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

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

Announced routes

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


2804:482c::/33	No ROA	Other IRR onlyRADB	2 0%low visibility	2
2804:482c:8000::/33	No ROA	Other IRR onlyRADB	2 0%low visibility	2
2804:482c::/32	No ROA	Other IRR onlyALTDB, RADB, TC	1 0%low visibility	1

2804:482c::/33

No ROA

Other IRR onlyRADB

2 0%low visibility

2804:482c:8000::/33

No ROA

Other IRR onlyRADB

2 0%low visibility

2804:482c::/32

No ROA

Other IRR onlyALTDB, RADB, TC

1 0%low visibility

AS-SET

AS267102 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: RIR3
Route object: not announced1

Change	Prefix or set	Detail	Full-table peers
ROA: none	2804:482c::/33	No ROA covers it. Add a ROA for AS267102, maxLength 33.	2 of 636
Route object: RIR	2804:482c::/33	Route object only in RADB. Add it in the RIR database for the space.	2 of 636
ROA: none	2804:482c:8000::/33	No ROA covers it. Add a ROA for AS267102, maxLength 33.	2 of 636
Route object: RIR	2804:482c:8000::/33	Route object only in RADB. Add it in the RIR database for the space.	2 of 636
ROA: none	2804:482c::/32	No ROA covers it. Add a ROA for AS267102, maxLength 32.	1 of 636
Route object: RIR	2804:482c::/32	Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.	1 of 636

Change

Prefix or set

Detail

Full-table peers

ROA: none

2804:482c::/33

No ROA covers it. Add a ROA for AS267102, maxLength 33.

2 of 636

Route object: RIR

2804:482c::/33

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

2 of 636

ROA: none

2804:482c:8000::/33

No ROA covers it. Add a ROA for AS267102, maxLength 33.

2 of 636

Route object: RIR

2804:482c:8000::/33

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

2 of 636

ROA: none

2804:482c::/32

No ROA covers it. Add a ROA for AS267102, maxLength 32.

1 of 636

Route object: RIR

2804:482c::/32

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

1 of 636

Route objects not announced

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


2804:2710::/32	RADB	No ROA

2804:2710::/32

RADB

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.