Network · data from 2026-11-12

AS142289 Roxonic Systems

Registry name: ROXONIC-AS-AP - Roxonic Systems, NL · PeeringDB

0IPv4 routes

8IPv6 routes 75.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 AS142289, seen from no peer

Announced routes

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


2a0e:46c4:106::/48	No ROA	RIR databaseRIPE	635 100%	67
2a0e:46c4:2c10::/44	No ROA	RIR databaseRIPE	635 100%	67
2a06:a005:700::/44	Valid	RIR databaseRIPE	635 100%	67
2a06:a005:a30::/44	Valid	RIR databaseRIPE	635 100%	67
2a06:a005:a40::/44	Valid	RIR databaseRIPE	635 100%	67
2a06:a005:a50::/44	Valid	RIR databaseRIPE	635 100%	67
2a06:a005:a60::/44	Valid	RIR databaseRIPE	635 100%	67
2a0e:b107:15f0::/44	Valid	RIR databaseRIPE	635 100%	67

AS-SET

PeeringDB's irr_as_set for AS142289: RIPE::AS-ROXONIC. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS142289 isn't in the set, or no route object for AS142289 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

Name	Database	ASNs	Sets	Route objects	AS142289 in it	Not covered
RIPE::AS-ROXONIC	RIPE1 member set in no database: AS154571:AS-ZENFIBER	3	2	119	Yes	0

Name

Database

ASNs

Sets

Route objects

AS142289 in it

Not covered

RIPE::AS-ROXONIC

RIPE1 member set in no database: AS154571:AS-ZENFIBER

119

Yes

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

ROA: none2
AS-SET: missing member1

Change	Prefix or set	Detail	Full-table peers
ROA: none	2a0e:46c4:106::/48	No ROA covers it. Add a ROA for AS142289, maxLength 48.	635 of 636
ROA: none	2a0e:46c4:2c10::/44	No ROA covers it. Add a ROA for AS142289, maxLength 44.	635 of 636
AS-SET: missing member	RIPE::AS-ROXONIC	AS-ROXONIC (RIPE) lists AS154571:AS-ZENFIBER; no IRR database read has it.

Change

Prefix or set

Detail

Full-table peers

ROA: none

2a0e:46c4:106::/48

No ROA covers it. Add a ROA for AS142289, maxLength 48.

635 of 636

ROA: none

2a0e:46c4:2c10::/44

No ROA covers it. Add a ROA for AS142289, maxLength 44.

635 of 636

AS-SET: missing member

RIPE::AS-ROXONIC

AS-ROXONIC (RIPE) lists AS154571:AS-ZENFIBER; no IRR database read has it.

Route objects not announced

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