Skip to main content

AS263154

ASN263154

AVANCAR INTERNET

Registry

Authoritative registration data

AS number
263154
Name
ASN263154
Organisation
AVANCAR INTERNET
Country
Flag of Brazil BR Brazil
RIR
—
Registered
Source:asn:rdap retrieved

IPv4 prefixes

4

IPv6 prefixes

1

Total announced

5

Announced prefixes

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

Prefixes announced by AS263154
177.93.168.0/21 IPv4 /21 not checked
138.59.236.0/22 IPv4 /22 not checked
170.247.44.0/22 IPv4 /22 not checked
170.254.196.0/22 IPv4 /22 not checked
2804:178c::/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 AS263154
Address families
IX.br (PTT.br) São Paulo: ATM/MPLA 50,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 AS263154 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

7 networks seen before AS263154 in AS paths

Observed upstreams
Families
AS52468 52468 233 649
v4 v6
AS6939 HURRICANE 20 64
v4 v6
AS33891 CORE-BACKBONE 4 21
v4
AS1031 PEER1-1031 6 17
v4
AS3303 SWISSCOM 3 9
v4
AS53013 ASN53013 3 8
v4 v6
AS6057 6057 2 8
v4

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS263154 in AS paths

Observed downstreams
Families
AS263164 6 8
v6

No rows match “”.

Showing – of

Uncertain adjacencies

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