Skip to main content

AS270764

ASN270764

Ecxon Datacenter LTDA

Registry

Authoritative registration data

AS number
270764
Name
ASN270764
Organisation
Ecxon Datacenter LTDA
Country
Flag of Brazil BR Brazil
RIR
—
Registered
Source:asn:rdap retrieved

IPv4 prefixes

8

IPv6 prefixes

3

Total announced

11

Announced prefixes

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

Prefixes announced by AS270764
104.234.119.0/24 IPv4 /24 not checked
172.84.94.0/24 IPv4 /24 not checked
181.215.236.0/24 IPv4 /24 not checked
181.215.253.0/24 IPv4 /24 not checked
181.215.254.0/24 IPv4 /24 not checked
189.127.164.0/24 IPv4 /24 not checked
189.127.165.0/24 IPv4 /24 not checked
45.40.99.0/24 IPv4 /24 not checked
2804:7110:4000::/48 IPv6 /48 not checked
2804:7110:5100::/48 IPv6 /48 RPKI valid
2804:7110:7100::/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 AS270764
Address families
IX.br (PTT.br) Porto Alegre: ATM/MPLA 10,000 Mbps IPv4 · IPv6
IX.br (PTT.br) São Paulo: ATM/MPLA 100,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 AS270764 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

8 networks seen before AS270764 in AS paths

Observed upstreams
Families
AS13335 CLOUDFLARENET 237 2,414
v4
AS6939 HURRICANE 126 549
v6
AS174 COGENT-174 43 136
v6
AS3356 LEVEL3 32 104
v6
AS60068 CDN77 6 24
v6
AS6057 6057 2 6
v6
AS61626 ASN61626 1 3
v6
AS137409 GSLNETWORKS-AS-AP 1 3
v6

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS270764 in AS paths

Observed downstreams
Families
AS213344 FlameHost 6 6
v6

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.