Skip to main content

AS266385

ASN266385

TR Servicos de Telecomunicacoes LTDA-ME

Registry

Authoritative registration data

AS number
266385
Name
ASN266385
Organisation
TR Servicos de Telecomunicacoes LTDA-ME
Country
Flag of Brazil BR Brazil
RIR
—
Registered
Source:asn:rdap retrieved

IPv4 prefixes

3

IPv6 prefixes

4

Total announced

7

Announced prefixes

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

Prefixes announced by AS266385
170.80.224.0/22 IPv4 /22 not checked
170.80.224.0/23 IPv4 /23 not checked
170.80.226.0/23 IPv4 /23 not checked
2804:3708::/32 IPv6 /32 RPKI valid
2804:3708:8000::/33 IPv6 /33 RPKI valid
2804:3708::/33 IPv6 /33 RPKI valid
2804:3708:8040::/42 IPv6 /42 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 AS266385
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 AS266385 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

6 networks seen before AS266385 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 62 234
v4 v6
AS53062 ASN53062 193 225
v4 v6
AS22381 ASN22381 101 140
v4 v6
AS35280 F5 3 22
v4 v6
AS6057 6057 3 13
v4 v6
AS61626 ASN61626 1 5
v4 v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS266385 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

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