Network · data from 2026-11-12

AS397563 ADEOXTECH - ADEOX

Registry name: ADEOXTECH - ADEOX, US · not in PeeringDB

19IPv4 routes 78.9% RPKI valid · 68.4% with a route object

0IPv6 routes

4RPKI invalid 4 origin · 0 maxLength

0No ROA 6 with no route object for this origin

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

6Route objects not announced registered with origin AS397563, seen from no peer

Announced routes

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


151.247.213.0/24	Invalid: origin	None	31 5%low visibility	24
31.57.142.0/24	Invalid: origin	Other origin only	24 4%low visibility	22
147.90.50.0/24	Invalid: origin	Other origin only	15 2%low visibility	17
89.44.209.0/24	Invalid: origin	Other origin only	6 1%low visibility	6
213.142.136.0/24	Valid	Nonecovered by 213.142.136.0/23	672 100%	67
213.142.137.0/24	Valid	Nonecovered by 213.142.136.0/23	672 100%	67
74.122.100.0/22	Valid	RIR databaseARIN	671 100%	67
213.142.152.0/24	Valid	RIR databaseRADB, RIPE	671 100%	67
213.142.153.0/24	Valid	RIR databaseRADB, RIPE	671 100%	67
80.253.252.0/24	Valid	RIR databaseRADB, RIPE	670 100%	67
80.253.253.0/24	Valid	RIR databaseRADB, RIPE	670 100%	67
91.151.80.0/24	Valid	RIR databaseRIPE	670 100%	67
91.151.82.0/24	Valid	RIR databaseRIPE	670 100%	67
91.151.91.0/24	Valid	RIR databaseRIPE	670 100%	67
213.142.128.0/24	Valid	RIR databaseRIPE	670 100%	67
213.142.129.0/24	Valid	RIR databaseRIPE	670 100%	67
213.142.130.0/24	Valid	RIR databaseRIPE	670 100%	67
213.142.131.0/24	Valid	RIR databaseRIPE	670 100%	67
213.142.142.0/24	Valid	RIR databaseRIPE	670 100%	67

151.247.213.0/24

Invalid: origin

None

31 5%low visibility

31.57.142.0/24

Invalid: origin

Other origin only

24 4%low visibility

147.90.50.0/24

Invalid: origin

Other origin only

15 2%low visibility

89.44.209.0/24

Invalid: origin

Other origin only

6 1%low visibility

213.142.136.0/24

Valid

Nonecovered by 213.142.136.0/23

672 100%

213.142.137.0/24

Valid

Nonecovered by 213.142.136.0/23

672 100%

74.122.100.0/22

Valid

RIR databaseARIN

671 100%

213.142.152.0/24

Valid

RIR databaseRADB, RIPE

671 100%

213.142.153.0/24

Valid

RIR databaseRADB, RIPE

671 100%

80.253.252.0/24

Valid

RIR databaseRADB, RIPE

670 100%

80.253.253.0/24

Valid

RIR databaseRADB, RIPE

670 100%

91.151.80.0/24

Valid

RIR databaseRIPE

670 100%

91.151.82.0/24

Valid

RIR databaseRIPE

670 100%

91.151.91.0/24

Valid

RIR databaseRIPE

670 100%

213.142.128.0/24

Valid

RIR databaseRIPE

670 100%

213.142.129.0/24

Valid

RIR databaseRIPE

670 100%

213.142.130.0/24

Valid

RIR databaseRIPE

670 100%

213.142.131.0/24

Valid

RIR databaseRIPE

670 100%

213.142.142.0/24

Valid

RIR databaseRIPE

670 100%

AS-SET

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

ROA: origin4
Route object: none6
Route object: not announced6

Change	Prefix or set	Detail	Full-table peers
ROA: origin	151.247.213.0/24	ROAs covering it name AS834, AS20473, not AS397563. If AS397563 should announce it, add a ROA for AS397563.	31 of 673
Route object: none	151.247.213.0/24	No route object for it. Add a route object with origin AS397563 in the RIR database for the space.	31 of 673
ROA: origin	31.57.142.0/24	ROAs covering it name AS834, AS202051, not AS397563. If AS397563 should announce it, add a ROA for AS397563.	24 of 673
Route object: none	31.57.142.0/24	Route objects for it name AS202051. Add a route object with origin AS397563 in the RIR database for the space.	24 of 673
ROA: origin	147.90.50.0/24	ROAs covering it name AS40676, not AS397563. If AS397563 should announce it, add a ROA for AS397563.	15 of 673
Route object: none	147.90.50.0/24	Route objects for it name AS40676. Add a route object with origin AS397563 in the RIR database for the space.	15 of 673
ROA: origin	89.44.209.0/24	ROAs covering it name AS34450, not AS397563. If AS397563 should announce it, add a ROA for AS397563.	6 of 673
Route object: none	89.44.209.0/24	Route objects for it name AS34450. Add a route object with origin AS397563 in the RIR database for the space.	6 of 673
Route object: none	213.142.136.0/24	No route object for it. A route object for 213.142.136.0/23 with origin AS397563 covers it (filters allowing more-specifics accept it). Add a route object with origin AS397563 in the RIR database for the space.	672 of 673
Route object: none	213.142.137.0/24	No route object for it. A route object for 213.142.136.0/23 with origin AS397563 covers it (filters allowing more-specifics accept it). Add a route object with origin AS397563 in the RIR database for the space.	672 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: origin

151.247.213.0/24

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

31 of 673

Route object: none

151.247.213.0/24

No route object for it. Add a route object with origin AS397563 in the RIR database for the space.

31 of 673

ROA: origin

31.57.142.0/24

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

24 of 673

Route object: none

31.57.142.0/24

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

24 of 673

ROA: origin

147.90.50.0/24

ROAs covering it name AS40676, not AS397563. If AS397563 should announce it, add a ROA for AS397563.

15 of 673

Route object: none

147.90.50.0/24

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

15 of 673

ROA: origin

89.44.209.0/24

ROAs covering it name AS34450, not AS397563. If AS397563 should announce it, add a ROA for AS397563.

6 of 673

Route object: none

89.44.209.0/24

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

6 of 673

Route object: none

213.142.136.0/24

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

672 of 673

Route object: none

213.142.137.0/24

672 of 673

Route objects not announced

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


45.128.14.0/24	RADB	No ROA
45.128.15.0/24	RADB	No ROA
80.253.252.0/23	RIPE	Valid
205.234.151.0/24	RADB	No ROA
213.142.136.0/23	RIPE	No ROA
213.142.152.0/23	RIPE	Valid

45.128.14.0/24

RADB

No ROA

45.128.15.0/24

RADB

No ROA

80.253.252.0/23

RIPE

Valid

205.234.151.0/24

RADB

No ROA

213.142.136.0/23

RIPE

No ROA

213.142.152.0/23

RIPE

Valid

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.