Network · data from 2026-11-12

AS25819 Collier Technologies

Registry name: COLLIER-TECHNOLOGIES-LLC - Collier Technologies LLC, US · PeeringDB

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

8IPv6 routes 87.5% RPKI valid · 12.5% with a route object

3RPKI invalid 0 origin · 3 maxLength

1No ROA 9 with no route object for this origin

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

2Route objects not announced registered with origin AS25819, seen from no peer

Announced routes

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


23.181.112.0/29	Invalid: maxLength	Nonecovered by 23.181.112.0/24	1 0%low visibility	1
23.181.112.16/28	Invalid: maxLength	Nonecovered by 23.181.112.0/24	1 0%low visibility	1
2602:fc6d::108/128	Invalid: maxLength	Nonecovered by 2602:fc6d::/40	1 0%low visibility	1
44.32.94.0/23	No ROA	Other IRR onlyALTDB	668 99%	67
2602:fc6d:f5::/48	Valid	Nonecovered by 2602:fc6d::/40	635 100%	69
2602:fc6d:7:7::/64	Valid	Nonecovered by 2602:fc6d::/40	3 0%low visibility	3
2602:fc6d:3a::/64	Valid	Nonecovered by 2602:fc6d::/40	3 0%low visibility	3
2602:fc6d:f5:3a::/64	Valid	Nonecovered by 2602:fc6d::/40	3 0%low visibility	3
2602:fc6d:f5:1337::/64	Valid	Nonecovered by 2602:fc6d::/40	3 0%low visibility	3
2602:fc6d:f6::/64	Valid	Nonecovered by 2602:fc6d::/40	3 0%low visibility	3
23.181.112.0/24	Valid	RIR databaseALTDB, ARIN	668 99%	67
2602:fc6d::/40	Valid	RIR databaseALTDB, ARIN, RADB	635 100%	69

23.181.112.0/29

Invalid: maxLength

Nonecovered by 23.181.112.0/24

1 0%low visibility

23.181.112.16/28

Invalid: maxLength

Nonecovered by 23.181.112.0/24

1 0%low visibility

2602:fc6d::108/128

Invalid: maxLength

Nonecovered by 2602:fc6d::/40

1 0%low visibility

44.32.94.0/23

No ROA

Other IRR onlyALTDB

668 99%

2602:fc6d:f5::/48

Valid

Nonecovered by 2602:fc6d::/40

635 100%

2602:fc6d:7:7::/64

Valid

Nonecovered by 2602:fc6d::/40

3 0%low visibility

2602:fc6d:3a::/64

Valid

Nonecovered by 2602:fc6d::/40

3 0%low visibility

2602:fc6d:f5:3a::/64

Valid

Nonecovered by 2602:fc6d::/40

3 0%low visibility

2602:fc6d:f5:1337::/64

Valid

Nonecovered by 2602:fc6d::/40

3 0%low visibility

2602:fc6d:f6::/64

Valid

Nonecovered by 2602:fc6d::/40

3 0%low visibility

23.181.112.0/24

Valid

RIR databaseALTDB, ARIN

668 99%

2602:fc6d::/40

Valid

RIR databaseALTDB, ARIN, RADB

635 100%

AS-SET

PeeringDB's irr_as_set for AS25819: AS-25819. 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 (AS25819 isn't in the set, or no route object for AS25819 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	AS25819 in it	Not covered
AS-25819	In no IRR database read today.

Name

Database

ASNs

Sets

Route objects

AS25819 in it

Not covered

AS-25819

In no IRR database read today.

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

ROA: maxLength3
ROA: none1
Route object: none9
Route object: RIR1
AS-SET: not found1
Route object: not announced2

Change	Prefix or set	Detail	Full-table peers
ROA: maxLength	23.181.112.0/29	ROA 23.181.112.0/24 AS25819 has maxLength 24; the route is a /29. Raise the maxLength, or add a ROA for 23.181.112.0/29.	1 of 673
Route object: none	23.181.112.0/29	No route object for it. A route object for 23.181.112.0/24 with origin AS25819 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS25819 in the RIR database for the space.	1 of 673
ROA: maxLength	23.181.112.16/28	ROA 23.181.112.0/24 AS25819 has maxLength 24; the route is a /28. Raise the maxLength, or add a ROA for 23.181.112.16/28.	1 of 673
Route object: none	23.181.112.16/28	No route object for it. A route object for 23.181.112.0/24 with origin AS25819 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS25819 in the RIR database for the space.	1 of 673
ROA: maxLength	2602:fc6d::108/128	ROA 2602:fc6d::/40 AS25819 has maxLength 64; the route is a /128. Raise the maxLength, or add a ROA for 2602:fc6d::108/128.	1 of 636
Route object: none	2602:fc6d::108/128	No route object for it. A route object for 2602:fc6d::/40 with origin AS25819 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS25819 in the RIR database for the space.	1 of 636
ROA: none	44.32.94.0/23	No ROA covers it. Add a ROA for AS25819, maxLength 23.	668 of 673
Route object: RIR	44.32.94.0/23	Route object only in ALTDB. Add it in the RIR database for the space.	668 of 673
Route object: none	2602:fc6d:f5::/48	No route object for it. A route object for 2602:fc6d::/40 with origin AS25819 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25819 in the RIR database for the space.	635 of 636
Route object: none	2602:fc6d:7:7::/64	No route object for it. A route object for 2602:fc6d::/40 with origin AS25819 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS25819 in the RIR database for the space.	3 of 636
Route object: none	2602:fc6d:3a::/64	No route object for it. A route object for 2602:fc6d::/40 with origin AS25819 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS25819 in the RIR database for the space.	3 of 636
Route object: none	2602:fc6d:f5:3a::/64	No route object for it. A route object for 2602:fc6d::/40 with origin AS25819 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS25819 in the RIR database for the space.	3 of 636
Route object: none	2602:fc6d:f5:1337::/64	No route object for it. A route object for 2602:fc6d::/40 with origin AS25819 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS25819 in the RIR database for the space.	3 of 636
Route object: none	2602:fc6d:f6::/64	No route object for it. A route object for 2602:fc6d::/40 with origin AS25819 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS25819 in the RIR database for the space.	3 of 636
AS-SET: not found	AS-25819	PeeringDB names AS-25819; no IRR database read has it.

Change

Prefix or set

Detail

Full-table peers

ROA: maxLength

23.181.112.0/29

ROA 23.181.112.0/24 AS25819 has maxLength 24; the route is a /29. Raise the maxLength, or add a ROA for 23.181.112.0/29.

1 of 673

Route object: none

23.181.112.0/29

No route object for it. A route object for 23.181.112.0/24 with origin AS25819 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS25819 in the RIR database for the space.

1 of 673

ROA: maxLength

23.181.112.16/28

ROA 23.181.112.0/24 AS25819 has maxLength 24; the route is a /28. Raise the maxLength, or add a ROA for 23.181.112.16/28.

1 of 673

Route object: none

23.181.112.16/28

1 of 673

ROA: maxLength

2602:fc6d::108/128

ROA 2602:fc6d::/40 AS25819 has maxLength 64; the route is a /128. Raise the maxLength, or add a ROA for 2602:fc6d::108/128.

1 of 636

Route object: none

2602:fc6d::108/128

No route object for it. A route object for 2602:fc6d::/40 with origin AS25819 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS25819 in the RIR database for the space.

1 of 636

ROA: none

44.32.94.0/23

No ROA covers it. Add a ROA for AS25819, maxLength 23.

668 of 673

Route object: RIR

44.32.94.0/23

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

668 of 673

Route object: none

2602:fc6d:f5::/48

No route object for it. A route object for 2602:fc6d::/40 with origin AS25819 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25819 in the RIR database for the space.

635 of 636

Route object: none

2602:fc6d:7:7::/64

3 of 636

Route object: none

2602:fc6d:3a::/64

3 of 636

Route object: none

2602:fc6d:f5:3a::/64

3 of 636

Route object: none

2602:fc6d:f5:1337::/64

3 of 636

Route object: none

2602:fc6d:f6::/64

3 of 636

AS-SET: not found

AS-25819

PeeringDB names AS-25819; no IRR database read has it.

Route objects not announced

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


44.32.94.0/24	RADB	No ROA
44.32.95.0/24	RADB	No ROA

44.32.94.0/24

RADB

No ROA

44.32.95.0/24

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.