Skip to main content

AS265008

ASN265008

T.I Connect LTDA

Registry

Authoritative registration data

AS number
265008
Name
ASN265008
Organisation
T.I Connect LTDA
Country
Flag of Brazil BR Brazil
RIR
Registered
Source:asn:rdap retrieved

IPv4 prefixes

3

IPv6 prefixes

7

Total announced

10

Announced prefixes

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

Prefixes announced by AS265008
170.0.60.0/22 IPv4 /22 not checked
170.0.60.0/23 IPv4 /23 not checked
170.0.62.0/23 IPv4 /23 not checked
2804:3158::/32 IPv6 /32 RPKI not found
2804:3158:8000::/33 IPv6 /33 RPKI not found
2804:3158::/33 IPv6 /33 RPKI not found
2804:3158:4000::/34 IPv6 /34 RPKI not found
2804:3158:8000::/34 IPv6 /34 RPKI not found
2804:3158::/34 IPv6 /34 RPKI not found
2804:3158:c000::/34 IPv6 /34 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 AS265008
Address families
IX.br (PTT.br) Fortaleza: ATM/MPLA 1,500 Mbps IPv4 · IPv6
IX.br (PTT.br) São Paulo: ATM/MPLA 2,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 AS265008 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

10 networks seen before AS265008 in AS paths

Observed upstreams
Families
AS266129 ASN266129 604 2,307
v4 v6
AS6939 HURRICANE 110 316
v4 v6
AS264288 ASN264288 158 244
v4 v6
AS52965 ASN52965 61 82
v4
AS35280 F5 8 22
v4 v6
AS137409 GSLNETWORKS-AS-AP 6 12
v4
AS6057 6057 3 10
v4 v6
AS1031 PEER1-1031 1 4
v4
AS39120 CONVERGENZE-AS 1 2
v4
AS61626 ASN61626 1 2
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS265008 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

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