Skip to main content

AS264596

ASN264596

ALFA TELECOMUNICACOES

Registry

Authoritative registration data

AS number
264596
Name
ASN264596
Organisation
ALFA TELECOMUNICACOES
Country
Flag of Brazil BR Brazil
RIR
—
Registered
Source:asn:rdap retrieved

IPv4 prefixes

5

IPv6 prefixes

4

Total announced

9

Announced prefixes

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

Prefixes announced by AS264596
138.59.40.0/22 IPv4 /22 not checked
138.59.40.0/24 IPv4 /24 RPKI valid
138.59.41.0/24 IPv4 /24 not checked
138.59.42.0/24 IPv4 /24 not checked
138.59.43.0/24 IPv4 /24 not checked
2804:222c::/32 IPv6 /32 not checked
2804:222c:100::/40 IPv6 /40 not checked
2804:222c:200::/40 IPv6 /40 not checked
2804:222c:300::/40 IPv6 /40 not checked

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 AS264596
Address families
IX.br (PTT.br) Rio de Janeiro: ATM/MPLA 10,000 Mbps IPv4 · IPv6
IX.br (PTT.br) São Paulo: 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 AS264596 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

9 networks seen before AS264596 in AS paths

Observed upstreams
Families
AS263009 ASN263009 691 975
v4 v6
AS6939 HURRICANE 113 559
v6
AS137409 GSLNETWORKS-AS-AP 8 44
v4 v6
AS35280 F5 6 22
v6
AS6057 6057 2 16
v4 v6
AS61626 ASN61626 1 8
v4 v6
AS39120 CONVERGENZE-AS 1 7
v4 v6
AS9498 BBIL-AP 1 4
v4
AS7195 7195 1 3
v6

No rows match “”.

Showing – of

Observed downstreams

3 networks seen after AS264596 in AS paths

Observed downstreams
Families
AS272426 ASN272426 251 328
v4
AS264025 ASN264025 101 142
v6
AS269337 ASN269337 1 12
v6

No rows match “”.

Showing – of

Uncertain adjacencies

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