ASN LANDING PAGE

AS54017

UCARE-MN - UCare Minnesota

Last updated · Jul 20, 2026

Country

Total prefixes

2

IPv4 prefixes

2

IPv6 prefixes

0

ASN summary

How to read the scale of AS54017

UCARE-MN - UCare Minnesota currently reports 2 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?

UCARE-MN - UCare 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 AS54017 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

AS54017 ASN lookupAS54017 BGPAS54017 peersAS54017 prefixesAS54017 upstreamsUCARE-MN - UCare 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
192.31.189.0/24AS54017
64.22.93.0/24AS54017

Related ASN pages

Related lookups and next steps

Frequently asked questions about this ASN page

What does AS54017 represent?

AS54017 is an autonomous system number. The current source associates it with UCARE-MN - UCare 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 AS54017 page?

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

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

Related topics