ASN LANDING PAGE

AS3390

UMKCNET - University of Missouri - Kansas City

Last updated · Jul 20, 2026

Country

Total prefixes

6

IPv4 prefixes

5

IPv6 prefixes

1

ASN summary

How to read the scale of AS3390

UMKCNET - University of Missouri - Kansas City 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?

UMKCNET - University of Missouri - Kansas 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 AS3390 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

AS3390 ASN lookupAS3390 BGPAS3390 peersAS3390 prefixesAS3390 upstreamsUMKCNET - University of Missouri - Kansas 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
134.193.0.0/16AS3390
204.56.0.0/21AS3390
204.76.182.0/23AS3390
204.76.184.0/22AS3390
204.76.188.0/23AS3390
2610:e0:a040::/44AS3390

Related ASN pages

Related lookups and next steps

Frequently asked questions about this ASN page

What does AS3390 represent?

AS3390 is an autonomous system number. The current source associates it with UMKCNET - University of Missouri - Kansas 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 AS3390 page?

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

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

Related topics