Skip to main content

AS25819

COLLIER-TECHNOLOGIES-LLC

Collier Technologies LLC

Registry

Authoritative registration data

AS number
25819
Name
COLLIER-TECHNOLOGIES-LLC
Organisation
Collier Technologies LLC
Country
—
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

2

Total announced

4

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS25819
44.32.94.0/23 IPv4 /23 RPKI not found
23.181.112.0/24 IPv4 /24 not checked
2602:fc6d::/40 IPv6 /40 RPKI valid
2602:fc6d:f5::/48 IPv6 /48 RPKI valid

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS25819
Address families
SIX Seattle (Jumbo): MTU 9000 1,000 Mbps IPv4 · IPv6
SIX Seattle: MTU 1500 1,000 Mbps IPv4 · IPv6

No rows match “”.

Showing – of

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS25819 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

3 networks seen before AS25819 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 227 636
v4 v6
AS3130 RGNET-SEA 193 296
v4 v6
AS20473 AS-VULTR 148 192
v4 v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS25819 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS49544 i3Dnet 1 4
v4 v6

No rows match “”.

Showing – of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.