Network · data from 2026-11-12

AS38854

Not in the RIR AS name list · not in PeeringDB

17IPv4 routes 70.6% RPKI valid · 76.5% with a route object

5IPv6 routes 80.0% RPKI valid · 100.0% with a route object

4RPKI invalid 4 origin · 0 maxLength

2No ROA 4 with no route object for this origin

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

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

Announced routes

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


87.232.90.0/24	Invalid: origin	None	67 10%low visibility	35
87.232.89.0/24	Invalid: origin	None	63 9%low visibility	33
128.14.49.0/24	Invalid: origin	Other origin only	2 0%low visibility	2
87.232.88.0/24	Invalid: origin	Other origin only	1 0%low visibility	1
103.167.50.0/23	No ROA	Other IRR onlyRADB	670 100%	67
2407:62c0::/32	No ROA	Other IRR onlyRADB	635 100%	67
98.98.108.0/23	Valid	Other IRR onlyRADB	672 100%	66
165.101.152.0/24	Valid	Other IRR onlyRADB	672 100%	66
165.101.153.0/24	Valid	Other IRR onlyRADB	672 100%	66
23.247.129.0/24	Valid	RIR databaseARIN	673 100%	66
66.253.44.0/24	Valid	RIR databaseARIN	673 100%	66
82.39.193.0/24	Valid	RIR databaseRADB, RIPE	673 100%	66
216.132.104.0/24	Valid	RIR databaseARIN	673 100%	66
216.132.134.0/24	Valid	RIR databaseARIN	673 100%	66
72.37.143.0/24	Valid	RIR databaseARIN	672 100%	66
72.37.167.0/24	Valid	RIR databaseARIN	672 100%	66
72.37.170.0/24	Valid	RIR databaseARIN	672 100%	66
82.39.194.0/24	Valid	RIR databaseRADB, RIPE	672 100%	67
2a0b:21c1:602b::/48	Valid	RIR databaseRIPE	635 100%	68
2a0b:21c1:601d::/48	Valid	RIR databaseRIPE	634 100%	69
2a0b:21c1:602c::/48	Valid	RIR databaseRIPE	634 100%	69
2a0b:21c1:6031::/48	Valid	RIR databaseRIPE	634 100%	67

87.232.90.0/24

Invalid: origin

None

67 10%low visibility

87.232.89.0/24

Invalid: origin

None

63 9%low visibility

128.14.49.0/24

Invalid: origin

Other origin only

2 0%low visibility

87.232.88.0/24

Invalid: origin

Other origin only

1 0%low visibility

103.167.50.0/23

No ROA

Other IRR onlyRADB

670 100%

2407:62c0::/32

No ROA

Other IRR onlyRADB

635 100%

98.98.108.0/23

Valid

Other IRR onlyRADB

672 100%

165.101.152.0/24

Valid

Other IRR onlyRADB

672 100%

165.101.153.0/24

Valid

Other IRR onlyRADB

672 100%

23.247.129.0/24

Valid

RIR databaseARIN

673 100%

66.253.44.0/24

Valid

RIR databaseARIN

673 100%

82.39.193.0/24

Valid

RIR databaseRADB, RIPE

673 100%

216.132.104.0/24

Valid

RIR databaseARIN

673 100%

216.132.134.0/24

Valid

RIR databaseARIN

673 100%

72.37.143.0/24

Valid

RIR databaseARIN

672 100%

72.37.167.0/24

Valid

RIR databaseARIN

672 100%

72.37.170.0/24

Valid

RIR databaseARIN

672 100%

82.39.194.0/24

Valid

RIR databaseRADB, RIPE

672 100%

2a0b:21c1:602b::/48

Valid

RIR databaseRIPE

635 100%

2a0b:21c1:601d::/48

Valid

RIR databaseRIPE

634 100%

2a0b:21c1:602c::/48

Valid

RIR databaseRIPE

634 100%

2a0b:21c1:6031::/48

Valid

RIR databaseRIPE

634 100%

AS-SET

AS38854 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
ROA: none2
Route object: none4
Route object: RIR5
Route object: not announced1

Change	Prefix or set	Detail	Full-table peers
ROA: origin	87.232.90.0/24	ROAs covering it name AS34346, not AS38854. If AS38854 should announce it, add a ROA for AS38854.	67 of 673
Route object: none	87.232.90.0/24	No route object for it. Add a route object with origin AS38854 in the RIR database for the space.	67 of 673
ROA: origin	87.232.89.0/24	ROAs covering it name AS34346, not AS38854. If AS38854 should announce it, add a ROA for AS38854.	63 of 673
Route object: none	87.232.89.0/24	No route object for it. Add a route object with origin AS38854 in the RIR database for the space.	63 of 673
ROA: origin	128.14.49.0/24	ROAs covering it name AS21859, AS62610, not AS38854. If AS38854 should announce it, add a ROA for AS38854.	2 of 673
Route object: none	128.14.49.0/24	Route objects for it name AS62610, AS400866. Add a route object with origin AS38854 in the RIR database for the space.	2 of 673
ROA: origin	87.232.88.0/24	ROAs covering it name AS218998, not AS38854. If AS38854 should announce it, add a ROA for AS38854.	1 of 673
Route object: none	87.232.88.0/24	Route objects for it name AS218998. Add a route object with origin AS38854 in the RIR database for the space.	1 of 673
ROA: none	103.167.50.0/23	No ROA covers it. Add a ROA for AS38854, maxLength 23.	670 of 673
Route object: RIR	103.167.50.0/23	Route object only in RADB. Add it in the RIR database for the space.	670 of 673
ROA: none	2407:62c0::/32	No ROA covers it. Add a ROA for AS38854, maxLength 32.	635 of 636
Route object: RIR	2407:62c0::/32	Route object only in RADB. Add it in the RIR database for the space.	635 of 636
Route object: RIR	98.98.108.0/23	Route object only in RADB. Add it in the RIR database for the space.	672 of 673
Route object: RIR	165.101.152.0/24	Route object only in RADB. Add it in the RIR database for the space.	672 of 673
Route object: RIR	165.101.153.0/24	Route object only in RADB. Add it in the RIR database for the space.	672 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: origin

87.232.90.0/24

ROAs covering it name AS34346, not AS38854. If AS38854 should announce it, add a ROA for AS38854.

67 of 673

Route object: none

87.232.90.0/24

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

67 of 673

ROA: origin

87.232.89.0/24

ROAs covering it name AS34346, not AS38854. If AS38854 should announce it, add a ROA for AS38854.

63 of 673

Route object: none

87.232.89.0/24

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

63 of 673

ROA: origin

128.14.49.0/24

ROAs covering it name AS21859, AS62610, not AS38854. If AS38854 should announce it, add a ROA for AS38854.

2 of 673

Route object: none

128.14.49.0/24

Route objects for it name AS62610, AS400866. Add a route object with origin AS38854 in the RIR database for the space.

2 of 673

ROA: origin

87.232.88.0/24

ROAs covering it name AS218998, not AS38854. If AS38854 should announce it, add a ROA for AS38854.

1 of 673

Route object: none

87.232.88.0/24

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

1 of 673

ROA: none

103.167.50.0/23

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

670 of 673

Route object: RIR

103.167.50.0/23

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

670 of 673

ROA: none

2407:62c0::/32

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

635 of 636

Route object: RIR

2407:62c0::/32

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

635 of 636

Route object: RIR

98.98.108.0/23

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

672 of 673

Route object: RIR

165.101.152.0/24

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

672 of 673

Route object: RIR

165.101.153.0/24

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

672 of 673

Route objects not announced

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


61.67.118.0/24	RADB	No ROA

61.67.118.0/24

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.