Skip to main content

AS265249

ASN265249

TCM TELECOM LTDA

Registry

Authoritative registration data

AS number
265249
Name
ASN265249
Organisation
TCM TELECOM LTDA
Country
Flag of Brazil BR Brazil
RIR
—
Registered
Source:asn:rdap retrieved

IPv4 prefixes

3

IPv6 prefixes

2

Total announced

5

Announced prefixes

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

Prefixes announced by AS265249
168.0.112.0/23 IPv4 /23 not checked
168.0.112.0/24 IPv4 /24 not checked
168.0.113.0/24 IPv4 /24 not checked
2804:2ce4::/32 IPv6 /32 not checked
2804:2ce4:4000::/34 IPv6 /34 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 AS265249
Address families
IX.br (PTT.br) Fortaleza: ATM/MPLA 18,000 Mbps IPv4 · IPv6
IX.br (PTT.br) Natal: ATM/MPLA 10,000 Mbps IPv4 · IPv6
IX.br (PTT.br) São Paulo: ATM/MPLA 18,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 AS265249 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

7 networks seen before AS265249 in AS paths

Observed upstreams
Families
AS14840 ASN14840 278 1,379
v4 v6
AS61568 ASN61568 132 198
v4 v6
AS262293 ASN262293 49 170
v4
AS6057 6057 7 23
v4 v6
AS35280 F5 5 15
v4 v6
AS61626 ASN61626 3 11
v4 v6
AS7195 7195 1 1
v6

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS265249 in AS paths

Observed downstreams
Families
AS264561 ASN264561 162 1,218
v4

No rows match “”.

Showing – of

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.