Skip to main content

AS270470

ASN270470

LN TELECOM

Registry

Authoritative registration data

AS number
270470
Name
ASN270470
Organisation
LN TELECOM
Country
Flag of Brazil BR Brazil
RIR
—
Registered
Source:asn:rdap retrieved

IPv4 prefixes

7

IPv6 prefixes

3

Total announced

10

Announced prefixes

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

Prefixes announced by AS270470
24.152.8.0/22 IPv4 /22 not checked
24.152.10.0/23 IPv4 /23 RPKI valid
24.152.8.0/23 IPv4 /23 RPKI valid
24.152.10.0/24 IPv4 /24 not checked
24.152.11.0/24 IPv4 /24 RPKI valid
24.152.8.0/24 IPv4 /24 RPKI valid
24.152.9.0/24 IPv4 /24 RPKI valid
2804:6c78::/32 IPv6 /32 not checked
2804:6c78:8000::/33 IPv6 /33 RPKI valid
2804:6c78::/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 AS270470
Address families
IX.br (PTT.br) Cascavel: Main 10,000 Mbps IPv4 · IPv6
IX.br (PTT.br) Curitiba: ATM/MPLA 10,000 Mbps IPv4 · IPv6
IX.br (PTT.br) Florianópolis: ATM/MPLA 10,000 Mbps IPv4 · IPv6
IX.br (PTT.br) Porto Alegre: 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 AS270470 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

7 networks seen before AS270470 in AS paths

Observed upstreams
Families
AS263495 ASN263495 236 1,170
v4 v6
AS53062 ASN53062 453 645
v4 v6
AS6939 HURRICANE 130 508
v4 v6
AS35280 F5 7 38
v4 v6
AS137409 GSLNETWORKS-AS-AP 8 28
v4 v6
AS6057 6057 3 22
v4 v6
AS39120 CONVERGENZE-AS 1 4
v4 v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS270470 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

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