Network · data from 2026-11-12

AS201867 OXAGON-AS OXAGON LIMITED

Registry name: OXAGON-AS OXAGON LIMITED, GB · not in PeeringDB

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

0IPv6 routes

1RPKI invalid 1 origin · 0 maxLength

2No ROA 2 with no route object for this origin

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

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

Announced routes

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


213.198.29.0/24	Invalid: origin	None	2 0%low visibility	2
149.7.62.0/24	No ROA	Other IRR onlyRADB	673 100%	67
154.59.135.0/24	No ROA	Other IRR onlyRADB	673 100%	67
213.152.250.0/24	Valid	None	673 100%	67

213.198.29.0/24

Invalid: origin

None

2 0%low visibility

149.7.62.0/24

No ROA

Other IRR onlyRADB

673 100%

154.59.135.0/24

No ROA

Other IRR onlyRADB

673 100%

213.152.250.0/24

Valid

None

673 100%

AS-SET

AS201867 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: origin1
ROA: none2
Route object: none2
Route object: RIR2

Change	Prefix or set	Detail	Full-table peers
ROA: origin	213.198.29.0/24	ROAs covering it name AS2914, not AS201867. If AS201867 should announce it, add a ROA for AS201867.	2 of 673
Route object: none	213.198.29.0/24	No route object for it. Add a route object with origin AS201867 in the RIR database for the space.	2 of 673
ROA: none	149.7.62.0/24	No ROA covers it. Add a ROA for AS201867, maxLength 24.	673 of 673
Route object: RIR	149.7.62.0/24	Route object only in RADB. Add it in the RIR database for the space.	673 of 673
ROA: none	154.59.135.0/24	No ROA covers it. Add a ROA for AS201867, maxLength 24.	673 of 673
Route object: RIR	154.59.135.0/24	Route object only in RADB. Add it in the RIR database for the space.	673 of 673
Route object: none	213.152.250.0/24	No route object for it. Add a route object with origin AS201867 in the RIR database for the space.	673 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: origin

213.198.29.0/24

ROAs covering it name AS2914, not AS201867. If AS201867 should announce it, add a ROA for AS201867.

2 of 673

Route object: none

213.198.29.0/24

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

2 of 673

ROA: none

149.7.62.0/24

No ROA covers it. Add a ROA for AS201867, maxLength 24.

673 of 673

Route object: RIR

149.7.62.0/24

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

673 of 673

ROA: none

154.59.135.0/24

No ROA covers it. Add a ROA for AS201867, maxLength 24.

673 of 673

Route object: RIR

154.59.135.0/24

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

673 of 673

Route object: none

213.152.250.0/24

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

673 of 673

Route objects not announced

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