ASN LANDING PAGE

AS50389

PHOENIXNAP-DE PHOENIX NAP, LLC.

Last updated · Jul 20, 2026

Country

Total prefixes

4

IPv4 prefixes

2

IPv6 prefixes

2

ASN summary

How to read the scale of AS50389

PHOENIXNAP-DE PHOENIX NAP, LLC. currently reports 4 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?

PHOENIXNAP-DE PHOENIX NAP, LLC. 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 AS50389 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

AS50389 ASN lookupAS50389 BGPAS50389 peersAS50389 prefixesAS50389 upstreamsPHOENIXNAP-DE PHOENIX NAP, LLC. 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
131.153.73.0/24AS50389
131.153.88.0/24AS50389
2a00:8860:300::/48AS50389
2a01:b960:2303::/48AS50389

Related ASN pages

Related lookups and next steps

Frequently asked questions about this ASN page

What does AS50389 represent?

AS50389 is an autonomous system number. The current source associates it with PHOENIXNAP-DE PHOENIX NAP, LLC. 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 AS50389 page?

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

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

Related topics