Skip to main content

AS264750

264750

Autonomous System AS264750 from DO-TNSR-LACNIC

Registry

Authoritative registration data

AS number
264750
Name
264750
Organisation
Autonomous System AS264750 from DO-TNSR-LACNIC
Country
—
RIR
LACNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

12

IPv6 prefixes

3

Total announced

15

Announced prefixes

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

Prefixes announced by AS264750
156.248.192.0/18 IPv4 /18 not checked
38.189.192.0/18 IPv4 /18 not checked
38.196.0.0/18 IPv4 /18 not checked
205.137.48.0/20 IPv4 /20 not checked
38.74.208.0/20 IPv4 /20 not checked
143.137.80.0/22 IPv4 /22 not checked
168.232.108.0/22 IPv4 /22 not checked
170.239.164.0/22 IPv4 /22 not checked
170.244.80.0/22 IPv4 /22 not checked
170.79.144.0/22 IPv4 /22 not checked
170.82.24.0/22 IPv4 /22 not checked
192.141.128.0/22 IPv4 /22 not checked
2803:3640::/32 IPv6 /32 RPKI valid
2803:e820::/32 IPv6 /32 not checked
2803:f8c0::/32 IPv6 /32 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 AS264750 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

1 networks seen before AS264750 in AS paths

Observed upstreams
Families
AS64126 64126 436 4,918
v4 v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS264750 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
AS265721 265721 1 9
v4

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.