Skip to main content

AS265938

ASN265938

LAR TELECOMUNICACOES LTDA - ME

Registry

Authoritative registration data

AS number
265938
Name
ASN265938
Organisation
LAR TELECOMUNICACOES LTDA - ME
Country
Flag of Brazil BR Brazil
RIR
—
Registered
Source:asn:rdap retrieved

IPv4 prefixes

3

IPv6 prefixes

2

Total announced

5

Announced prefixes

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

Prefixes announced by AS265938
164.163.44.0/22 IPv4 /22 RPKI valid
164.163.44.0/23 IPv4 /23 not checked
164.163.46.0/23 IPv4 /23 RPKI valid
2804:4028::/32 IPv6 /32 RPKI valid
2804:4028:100::/40 IPv6 /40 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 AS265938
Address families
IX.br (PTT.br) Curitiba: ATM/MPLA 20,000 Mbps IPv4 · IPv6
IX.br (PTT.br) São Paulo: ATM/MPLA 20,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 AS265938 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

7 networks seen before AS265938 in AS paths

Observed upstreams
Families
AS14840 ASN14840 1,978 6,805
v4 v6
AS6939 HURRICANE 181 567
v4 v6
AS263512 ASN263512 199 265
v4
AS6057 6057 10 32
v4 v6
AS137409 GSLNETWORKS-AS-AP 12 29
v4 v6
AS7195 7195 4 10
v4
AS61626 ASN61626 1 1
v4

No rows match “”.

Showing – of

Observed downstreams

5 networks seen after AS265938 in AS paths

Observed downstreams
Families
AS264126 ASN264126 591 2,719
v4 v6
AS265477 ASN265477 728 2,289
v4 v6
AS269513 ASN269513 301 675
v4
AS270875 ASN270875 463 601
v4 v6
AS263512 ASN263512 18 22
v4

No rows match “”.

Showing – of

Uncertain adjacencies

22 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.