Skip to main content

AS262475

ASN262475

TIVIT TERCEIRIZAÇÃO DE PROCESSOS, SERV. E TEC. S/A

Registry

Authoritative registration data

AS number
262475
Name
ASN262475
Organisation
TIVIT TERCEIRIZAÇÃO DE PROCESSOS, SERV. E TEC. S/A
Country
Flag of Brazil BR Brazil
RIR
—
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

1

Total announced

2

Announced prefixes

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

Prefixes announced by AS262475
177.53.176.0/22 IPv4 /22 not checked
2804:4e0::/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 AS262475
Address families
IX.br (PTT.br) Fortaleza: 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 AS262475 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

5 networks seen before AS262475 in AS paths

Observed upstreams
Families
AS16685 ASN16685 277 341
v4
AS6939 HURRICANE 126 167
v6
AS14840 ASN14840 2 5
v6
AS6057 6057 2 2
v6
AS7195 7195 2 2
v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS262475 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

3 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS28624 ASN28624 1 1
v6
AS52873 ASN52873 1 1
v6
AS61573 ASN61573 1 1
v6

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.