Skip to main content

AS270630

ASN270630

LOLNET TELECOMUNICAÇÕES

Registry

Authoritative registration data

AS number
270630
Name
ASN270630
Organisation
LOLNET TELECOMUNICAÇÕES
Country
Flag of Brazil BR Brazil
RIR
—
Registered
Source:asn:rdap retrieved

IPv4 prefixes

3

IPv6 prefixes

4

Total announced

7

Announced prefixes

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

Prefixes announced by AS270630
177.70.244.0/23 IPv4 /23 not checked
177.70.244.0/24 IPv4 /24 not checked
177.70.245.0/24 IPv4 /24 not checked
2804:6ef8::/35 IPv6 /35 not checked
2804:6ef8:1000::/37 IPv6 /37 RPKI valid
2804:6ef8:1::/48 IPv6 /48 not checked
2804:6ef8:3::/48 IPv6 /48 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 AS270630
Address families
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 AS270630 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

8 networks seen before AS270630 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 127 318
v4 v6
AS3356 LEVEL3 69 122
v4 v6
AS11432 ASN11432 78 95
v4
AS35280 F5 3 24
v4 v6
AS53052 ASN53052 19 23
v6
AS272713 ASN272713 7 23
v4 v6
AS6057 6057 2 14
v4 v6
AS61626 ASN61626 1 5
v4 v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS270630 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

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.