Network · data from 2026-11-12

AS400282 UPX LLC

Registry name: UPX - UPX US LLC, US · PeeringDB

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

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

0RPKI invalid 0 origin · 0 maxLength

0No ROA 1 with no route object for this origin

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

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

Announced routes

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


2606:9840:102::/48	Valid	Nonecovered by 2606:9840::/32	635 100%	67
23.139.8.0/24	Valid	Other IRR onlyRADB	667 99%	67
2606:9840::/32	Valid	Other IRR onlyRADB	623 98%	67

AS-SET

PeeringDB's irr_as_set for AS400282: AS-UPX. 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 (AS400282 isn't in the set, or no route object for AS400282 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	AS400282 in it	Not covered
AS-UPX	RADB4 member sets in no database: AS-263596, AS-268983, AS-269288, AS-273470	1,453	138	58,368	Yes	0

Name

Database

ASNs

Sets

Route objects

AS400282 in it

Not covered

AS-UPX

RADB4 member sets in no database: AS-263596, AS-268983, AS-269288, AS-273470

1,453

138

58,368

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

Route object: none1
Route object: RIR2
AS-SET: missing member4

Change	Prefix or set	Detail	Full-table peers
Route object: none	2606:9840:102::/48	No route object for it. A route object for 2606:9840::/32 with origin AS400282 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400282 in the RIR database for the space.	635 of 636
Route object: RIR	23.139.8.0/24	Route object only in RADB. Add it in the RIR database for the space.	667 of 673
Route object: RIR	2606:9840::/32	Route object only in RADB. Add it in the RIR database for the space.	623 of 636
AS-SET: missing member	AS-UPX	AS-UPX (RADB) lists AS-263596; no IRR database read has it.
AS-SET: missing member	AS-UPX	AS-UPX (RADB) lists AS-268983; no IRR database read has it.
AS-SET: missing member	AS-UPX	AS-UPX (RADB) lists AS-269288; no IRR database read has it.
AS-SET: missing member	AS-UPX	AS-UPX (RADB) lists AS-273470; no IRR database read has it.

Change

Prefix or set

Detail

Full-table peers

Route object: none

2606:9840:102::/48

No route object for it. A route object for 2606:9840::/32 with origin AS400282 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400282 in the RIR database for the space.

635 of 636

Route object: RIR

23.139.8.0/24

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

667 of 673

Route object: RIR

2606:9840::/32

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

623 of 636

AS-SET: missing member

AS-UPX

AS-UPX (RADB) lists AS-263596; no IRR database read has it.

AS-SET: missing member

AS-UPX

AS-UPX (RADB) lists AS-268983; no IRR database read has it.

AS-SET: missing member

AS-UPX

AS-UPX (RADB) lists AS-269288; no IRR database read has it.

AS-SET: missing member

AS-UPX

AS-UPX (RADB) lists AS-273470; no IRR database read has it.

Route objects not announced

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