Skip to main content

AS264017

ASN264017

WLAN SOLUCOES TECNOLOGICAS

Registry

Authoritative registration data

AS number
264017
Name
ASN264017
Organisation
WLAN SOLUCOES TECNOLOGICAS
Country
Flag of Brazil BR Brazil
RIR
Registered
Source:asn:rdap retrieved

IPv4 prefixes

5

IPv6 prefixes

3

Total announced

8

Announced prefixes

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

Prefixes announced by AS264017
138.219.168.0/22 IPv4 /22 not checked
138.219.168.0/23 IPv4 /23 not checked
138.219.170.0/23 IPv4 /23 not checked
138.219.170.0/24 IPv4 /24 not checked
138.219.171.0/24 IPv4 /24 not checked
2804:2978::/32 IPv6 /32 not checked
2804:2978:1000::/36 IPv6 /36 not checked
2804:2978::/36 IPv6 /36 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 AS264017
Address families
IX.br (PTT.br) São Paulo: ATM/MPLA 20,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 AS264017 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

14 networks seen before AS264017 in AS paths

Observed upstreams
Families
AS28649 ASN28649 556 5,741
v4
AS52925 ASN52925 347 1,897
v4 v6
AS267613 347 808
v4 v6
AS271253 ASN271253 329 533
v4 v6
AS6939 HURRICANE 127 319
v4 v6
AS35280 F5 7 17
v4 v6
AS6057 6057 4 10
v4 v6
AS137409 GSLNETWORKS-AS-AP 3 9
v4 v6
AS7195 7195 2 4
v6
AS24961 MYLOC-AS 2 4
v4
AS1031 PEER1-1031 2 3
v4
AS39120 CONVERGENZE-AS 1 2
v6
AS61626 ASN61626 1 2
v6
AS264409 ASN264409 1 1
v4

No rows match “”.

Showing of

Observed downstreams

2 networks seen after AS264017 in AS paths

Observed downstreams
Families
AS14463 ASN14463 312 6,851
v4 v6
AS263897 94 129
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.