ASN LANDING PAGE

AS396839

TEKTONIC-PHL - TekTonic

Last updated · Jul 20, 2026

Country

Total prefixes

6

IPv4 prefixes

5

IPv6 prefixes

1

ASN summary

How to read the scale of AS396839

TEKTONIC-PHL - TekTonic currently reports 6 prefixes and 2 upstream, downstream, or peer relationships. These counts describe the current dataset; they do not by themselves prove network quality, reach, or service use.

What can an ASN page answer?

An ASN page shows the public organization label, country or region, BGP prefixes, and available peer and upstream relationships. It adds network context but cannot confirm a website host, physical facility, security status, or service quality.

How should you read the organization and region fields?

TEKTONIC-PHL - TekTonic is currently associated with an unknown region. These values come from public network sources and are useful lookup clues; an organization label, registration region, and actual service location may differ.

How should you verify the AS396839 result?

The page shows ASN data returned by the current upstream query; interpret it with the update time. Open representative IP pages from the same network and compare prefixes, source labels, and query times. Verify operator or service claims with the relevant registry or network operator.

How to verify this ASN result

AS396839 ASN lookupAS396839 BGPAS396839 peersAS396839 prefixesAS396839 upstreamsTEKTONIC-PHL - TekTonic ASN

Upstreams

Detailed data for this ASN is not available right now.

Downstreams

Detailed data for this ASN is not available right now.

Prefix inventory

PrefixNameCountry
108.161.142.0/23AS396839
108.161.142.0/24AS396839
108.161.143.0/24AS396839
2606:4300:1::/48AS396839
38.123.149.0/24AS396839
72.18.84.0/23AS396839

Related ASN pages

Related lookups and next steps

Frequently asked questions about this ASN page

What does AS396839 represent?

AS396839 is an autonomous system number. The current source associates it with TEKTONIC-PHL - TekTonic and the region field an unknown region; those values add network context but do not prove a specific service, physical location, or quality level.

What are peers, upstreams, and prefixes useful for on the AS396839 page?

They help explain the scale, interconnection depth, and route structure of AS396839. Richer peering and upstream data often indicate broader network reach, but they should still be interpreted together with prefixes and related IP landing pages.

What should you do after reviewing AS396839?

Open a concrete IP page to check how the address maps into AS396839, then compare the prefix, source labels, and query time. Verify operator or service claims with the relevant registry or network operator.

Related topics