Skip to main content

AS262518

ASN262518

LWSA S/A

Registry

Authoritative registration data

AS number
262518
Name
ASN262518
Organisation
LWSA S/A
Country
Flag of Brazil BR Brazil
RIR
—
Registered
Source:asn:rdap retrieved

IPv4 prefixes

11

IPv6 prefixes

2

Total announced

13

Announced prefixes

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

Prefixes announced by AS262518
177.67.112.0/21 IPv4 /21 not checked
177.67.120.0/21 IPv4 /21 RPKI valid
177.67.112.0/22 IPv4 /22 not checked
177.67.116.0/22 IPv4 /22 not checked
177.67.120.0/22 IPv4 /22 RPKI valid
177.67.124.0/22 IPv4 /22 not checked
138.122.172.0/23 IPv4 /23 not checked
138.122.174.0/23 IPv4 /23 RPKI valid
177.67.118.0/23 IPv4 /23 not checked
138.122.174.0/24 IPv4 /24 not checked
138.122.175.0/24 IPv4 /24 not checked
2804:580::/32 IPv6 /32 not checked
2804:580::/33 IPv6 /33 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 AS262518
Address families
IX.br (PTT.br) São Paulo: ATM/MPLA 40,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 AS262518 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

9 networks seen before AS262518 in AS paths

Observed upstreams
Families
AS4230 ASN4230 448 1,684
v4
AS27715 ASN27715 276 1,639
v4
AS263541 ASN263541 279 414
v4
AS6939 HURRICANE 111 285
v6
AS35280 F5 6 17
v4 v6
AS137409 GSLNETWORKS-AS-AP 5 13
v4 v6
AS6057 6057 2 10
v4 v6
AS61626 ASN61626 1 5
v4 v6
AS39120 CONVERGENZE-AS 1 2
v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS262518 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

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