Network · data from 2026-11-12

AS17185 Quonix Networks

Registry name: D102-PHL-1 - Data102, US · PeeringDB

7IPv4 routes 85.7% RPKI valid · 100.0% with a route object

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

0RPKI invalid 0 origin · 0 maxLength

1No ROA 0 with no route object for this origin

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

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

Announced routes

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


76.8.48.0/20	No ROA	RIR databaseARIN, RADB	671 100%	67
74.115.168.0/21	Valid	RIR databaseARIN, RADB	671 100%	67
173.195.144.0/20	Valid	RIR databaseARIN, RADB	671 100%	67
199.16.48.0/21	Valid	RIR databaseARIN, RADB	671 100%	67
208.72.236.0/22	Valid	RIR databaseARIN, RADB	671 100%	67
208.82.128.0/22	Valid	RIR databaseARIN, RADB	671 100%	67
208.88.48.0/21	Valid	RIR databaseARIN, RADB	671 100%	67
2604:bf00::/32	Valid	RIR databaseARIN	604 95%	67

AS-SET

PeeringDB's irr_as_set for AS17185: ARIN::AS-QUONIX. 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 (AS17185 isn't in the set, or no route object for AS17185 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	AS17185 in it	Not covered
ARIN::AS-QUONIX	ARIN1 member set in no database: AS-MTMACCESSSA	6	1	77	Yes	0

Name

Database

ASNs

Sets

Route objects

AS17185 in it

Not covered

ARIN::AS-QUONIX

ARIN1 member set in no database: AS-MTMACCESSSA

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: none1
AS-SET: missing member1
Route object: not announced1

Change	Prefix or set	Detail	Full-table peers
ROA: none	76.8.48.0/20	No ROA covers it. Add a ROA for AS17185, maxLength 20.	671 of 673
AS-SET: missing member	ARIN::AS-QUONIX	AS-QUONIX (ARIN) lists AS-MTMACCESSSA; no IRR database read has it.

Change

Prefix or set

Detail

Full-table peers

ROA: none

76.8.48.0/20

No ROA covers it. Add a ROA for AS17185, maxLength 20.

671 of 673

AS-SET: missing member

ARIN::AS-QUONIX

AS-QUONIX (ARIN) lists AS-MTMACCESSSA; no IRR database read has it.

Route objects not announced

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


2605:8300::/32	RADB	No ROA

2605:8300::/32

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.