Network · data from 2026-11-12

AS50531 ABAX

Registry name: ABAX ABAX as, NO · PeeringDB

2IPv4 routes 50.0% RPKI valid · 100.0% with a route object

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

0RPKI invalid 0 origin · 0 maxLength

2No ROA 0 with no route object for this origin

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

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

Announced routes

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


185.89.92.0/22	No ROA	RIR databaseRIPE	673 100%	66
2a03:8220::/32	No ROA	RIR databaseRIPE	636 100%	69
185.53.191.0/24	Valid	RIR databaseRIPE	673 100%	66

AS-SET

AS50531's PeeringDB record names no 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 2 are in fix.csv.

ROA: none2

Change	Prefix or set	Detail	Full-table peers
ROA: none	185.89.92.0/22	No ROA covers it. Add a ROA for AS50531, maxLength 22.	673 of 673
ROA: none	2a03:8220::/32	No ROA covers it. Add a ROA for AS50531, maxLength 32.	636 of 636

Change

Prefix or set

Detail

Full-table peers

ROA: none

185.89.92.0/22

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

673 of 673

ROA: none

2a03:8220::/32

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

636 of 636

Route objects not announced

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