Skip to main content

AS63027

LANICOM-NET

Lanicom, LLC

Registry

Authoritative registration data

AS number
63027
Name
LANICOM-NET
Organisation
Lanicom, LLC
Country
—
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

4

IPv6 prefixes

2

Total announced

6

Announced prefixes

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

Prefixes announced by AS63027
136.175.66.0/23 IPv4 /23 not checked
161.129.190.0/24 IPv4 /24 not checked
23.148.88.0/24 IPv4 /24 not checked
70.60.61.0/24 IPv4 /24 not checked
2602:fd0a::/36 IPv6 /36 not checked
2620:132::/44 IPv6 /44 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 AS63027
Address families
DET-iX 10,000 Mbps IPv4 · IPv6
Ohio IX: Ohio IX Public Peering LAN 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 AS63027 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

3 networks seen before AS63027 in AS paths

Observed upstreams
Families
AS174 COGENT-174 276 1,479
v4 v6
AS10796 TWC-10796-MIDWEST 144 421
v6
AS6939 HURRICANE 21 92
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS63027 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS20205 AMPLEX 1 6
v4 v6

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.