Skip to main content

AS270706

ASN270706

LAN TELECOM INTERNET BANDA LARGA LTDA

Registry

Authoritative registration data

AS number
270706
Name
ASN270706
Organisation
LAN TELECOM INTERNET BANDA LARGA LTDA
Country
Flag of Brazil BR Brazil
RIR
—
Registered
Source:asn:rdap retrieved

IPv4 prefixes

7

IPv6 prefixes

1

Total announced

8

Announced prefixes

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

Prefixes announced by AS270706
189.127.152.0/22 IPv4 /22 not checked
189.127.152.0/23 IPv4 /23 not checked
189.127.154.0/23 IPv4 /23 not checked
189.127.152.0/24 IPv4 /24 not checked
189.127.153.0/24 IPv4 /24 not checked
189.127.154.0/24 IPv4 /24 not checked
189.127.155.0/24 IPv4 /24 not checked
2804:701c::/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 AS270706
Address families
IX.br (PTT.br) Belém: ATM/MPLA 10,000 Mbps IPv4 · IPv6
IX.br (PTT.br) Fortaleza: ATM/MPLA 10,000 Mbps IPv4 · IPv6
IX.br (PTT.br) São Paulo: ATM/MPLA 10,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 AS270706 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

7 networks seen before AS270706 in AS paths

Observed upstreams
Families
AS266101 ASN266101 551 2,328
v4
AS26615 ASN26615 357 559
v4 v6
AS10429 ASN10429 232 383
v4 v6
AS6939 HURRICANE 131 287
v4
AS6057 6057 8 19
v4 v6
AS137409 GSLNETWORKS-AS-AP 10 16
v4 v6
AS61626 ASN61626 4 5
v4 v6

No rows match “”.

Showing – of

Observed downstreams

3 networks seen after AS270706 in AS paths

Observed downstreams
Families
AS266101 ASN266101 376 595
v4
AS272167 ASN272167 282 359
v4 v6
AS268693 ASN268693 53 146
v4 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.