Skip to main content

AS59815

TRINITY-AS

ORG-KL262-RIPE

Registry

Authoritative registration data

AS number
59815
Name
TRINITY-AS
Organisation
ORG-KL262-RIPE
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

16

IPv6 prefixes

0

Total announced

16

Announced prefixes

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

Prefixes announced by AS59815
31.6.96.0/19 IPv4 /19 not checked
5.104.32.0/19 IPv4 /19 not checked
109.75.192.0/20 IPv4 /20 not checked
31.6.112.0/20 IPv4 /20 not checked
31.6.96.0/20 IPv4 /20 not checked
5.104.32.0/20 IPv4 /20 not checked
5.104.48.0/20 IPv4 /20 not checked
178.209.88.0/21 IPv4 /21 not checked
178.209.92.0/22 IPv4 /22 not checked
185.42.40.0/22 IPv4 /22 not checked
185.70.128.0/22 IPv4 /22 not checked
217.64.144.0/22 IPv4 /22 not checked
178.209.90.0/23 IPv4 /23 not checked
185.70.130.0/23 IPv4 /23 not checked
178.209.88.0/24 IPv4 /24 not checked
185.70.129.0/24 IPv4 /24 not checked

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

No Internet Exchange memberships found

The exchange directory has no current membership records for this AS.

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 AS59815 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

20 networks seen before AS59815 in AS paths

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS59815 in AS paths

Observed downstreams
Families
AS25299 TRINITY-AS 1,037 2,946
v4

No rows match “”.

Showing – of

Uncertain adjacencies

13 adjacencies that may be an artefact of collector peering

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.