ASN LANDING PAGE

AS393662

SYMPLYFI-CORENET - SymplyFi

Last updated · Jul 20, 2026

Country

Total prefixes

5

IPv4 prefixes

5

IPv6 prefixes

0

ASN summary

How to read the scale of AS393662

SYMPLYFI-CORENET - SymplyFi currently reports 5 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?

SYMPLYFI-CORENET - SymplyFi 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 AS393662 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

AS393662 ASN lookupAS393662 BGPAS393662 peersAS393662 prefixesAS393662 upstreamsSYMPLYFI-CORENET - SymplyFi 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
160.20.230.0/23AS393662
160.20.230.0/24AS393662
160.20.231.0/24AS393662
172.110.156.0/24AS393662
172.110.157.0/24AS393662

Related ASN pages

Related lookups and next steps

Frequently asked questions about this ASN page

What does AS393662 represent?

AS393662 is an autonomous system number. The current source associates it with SYMPLYFI-CORENET - SymplyFi 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 AS393662 page?

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

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

Related topics