Skip to main content

AS39937

LTECH

LTech Solutions, Ltd.

Registry

Authoritative registration data

AS number
39937
Name
LTECH
Organisation
LTech Solutions, Ltd.
Country
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

4

IPv6 prefixes

1

Total announced

5

Announced prefixes

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

Prefixes announced by AS39937
216.120.143.0/24 IPv4 /24 not checked
23.160.120.0/24 IPv4 /24 not checked
23.160.121.0/24 IPv4 /24 not checked
23.160.122.0/24 IPv4 /24 not checked
2607:5240::/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 AS39937
Address families
NEO-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 AS39937 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

5 networks seen before AS39937 in AS paths

Observed upstreams
Families
AS396238 191 783
v4 v6
AS6597 261 375
v4 v6
AS1299 TWELVE99 76 334
v4 v6
AS6939 HURRICANE 217 316
v6
AS19009 22 73
v4 v6

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS39937 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 4
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.