Skip to main content

AS265356

ASN265356

NET PLANETY INFOTELECOM LTDA ME

Registry

Authoritative registration data

AS number
265356
Name
ASN265356
Organisation
NET PLANETY INFOTELECOM LTDA ME
Country
Flag of Brazil BR Brazil
RIR
—
Registered
Source:asn:rdap retrieved

IPv4 prefixes

3

IPv6 prefixes

3

Total announced

6

Announced prefixes

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

Prefixes announced by AS265356
168.181.124.0/22 IPv4 /22 not checked
168.181.124.0/23 IPv4 /23 not checked
168.181.126.0/23 IPv4 /23 not checked
2804:2ea0::/32 IPv6 /32 RPKI valid
2804:2ea0:8000::/33 IPv6 /33 RPKI valid
2804:2ea0::/33 IPv6 /33 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 AS265356
Address families
IX.br (PTT.br) Vitória: ATM/MPLA 10,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 AS265356 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

1 networks seen before AS265356 in AS paths

Observed upstreams
Families
AS269115 ASN269115 379 718
v4 v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS265356 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
AS14840 ASN14840 1 16
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.