ASN LANDING PAGE

AS217

UMN-SYSTEM - University of Minnesota

Last updated · Jul 20, 2026

Country

Total prefixes

6

IPv4 prefixes

5

IPv6 prefixes

1

ASN summary

How to read the scale of AS217

UMN-SYSTEM - University of Minnesota currently reports 6 prefixes and 1 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?

UMN-SYSTEM - University of Minnesota 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 AS217 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

AS217 ASN lookupAS217 BGPAS217 peersAS217 prefixesAS217 upstreamsUMN-SYSTEM - University of Minnesota 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
128.101.0.0/16AS217
131.212.0.0/16AS217
134.84.0.0/16AS217
146.57.0.0/16AS217
160.94.0.0/16AS217
2001:470:22::/48AS217

Related ASN pages

Related lookups and next steps

Frequently asked questions about this ASN page

What does AS217 represent?

AS217 is an autonomous system number. The current source associates it with UMN-SYSTEM - University of Minnesota 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 AS217 page?

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

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

Related topics