Skip to main content

AS269659

ASN269659

RD TORRESNET TELECOM LTDA

Registry

Authoritative registration data

AS number
269659
Name
ASN269659
Organisation
RD TORRESNET TELECOM LTDA
Country
Flag of Brazil BR Brazil
RIR
—
Registered
Source:asn:rdap retrieved

IPv4 prefixes

7

IPv6 prefixes

1

Total announced

8

Announced prefixes

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

Prefixes announced by AS269659
45.191.24.0/22 IPv4 /22 not checked
45.191.24.0/23 IPv4 /23 not checked
45.191.26.0/23 IPv4 /23 not checked
45.191.24.0/24 IPv4 /24 not checked
45.191.25.0/24 IPv4 /24 not checked
45.191.26.0/24 IPv4 /24 not checked
45.191.27.0/24 IPv4 /24 not checked
2804:67ec::/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

Internet Exchange memberships listed for AS269659
Address families
IX.br (PTT.br) Fortaleza: ATM/MPLA 20,000 Mbps IPv4 · IPv6
IX.br (PTT.br) São Paulo: ATM/MPLA 1,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 AS269659 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

9 networks seen before AS269659 in AS paths

Observed upstreams
Families
AS264969 ASN264969 225 572
v4
AS6939 HURRICANE 115 432
v4 v6
AS265038 ASN265038 236 355
v4 v6
AS52965 ASN52965 77 126
v4 v6
AS14840 ASN14840 2 20
v4
AS6057 6057 2 16
v4 v6
AS137409 GSLNETWORKS-AS-AP 3 9
v4 v6
AS61626 ASN61626 1 4
v4 v6
AS39120 CONVERGENZE-AS 1 1
v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS269659 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

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