ASN LANDING PAGE

AS394286

CITY-OF-JOHNSON-CITY - City of Johnson City

Last updated · Jul 20, 2026

Country

Total prefixes

1

IPv4 prefixes

1

IPv6 prefixes

0

ASN summary

How to read the scale of AS394286

CITY-OF-JOHNSON-CITY - City of Johnson City currently reports 1 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?

CITY-OF-JOHNSON-CITY - City of Johnson City 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 AS394286 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

AS394286 ASN lookupAS394286 BGPAS394286 peersAS394286 prefixesAS394286 upstreamsCITY-OF-JOHNSON-CITY - City of Johnson City 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
64.66.252.0/24AS394286

Related ASN pages

Related lookups and next steps

Frequently asked questions about this ASN page

What does AS394286 represent?

AS394286 is an autonomous system number. The current source associates it with CITY-OF-JOHNSON-CITY - City of Johnson City 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 AS394286 page?

They help explain the scale, interconnection depth, and route structure of AS394286. 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 AS394286?

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

Related topics