ASN LANDING PAGE

AS201931

LBNET LBnet.cz s.r.o.

Last updated · Jul 20, 2026

Country

Total prefixes

3

IPv4 prefixes

2

IPv6 prefixes

1

ASN summary

How to read the scale of AS201931

LBNET LBnet.cz s.r.o. currently reports 3 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?

LBNET LBnet.cz s.r.o. 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 AS201931 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

AS201931 ASN lookupAS201931 BGPAS201931 peersAS201931 prefixesAS201931 upstreamsLBNET LBnet.cz s.r.o. 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
185.217.232.0/23AS201931
185.217.234.0/24AS201931
2a07:6882::/32AS201931

Related ASN pages

Related lookups and next steps

Frequently asked questions about this ASN page

What does AS201931 represent?

AS201931 is an autonomous system number. The current source associates it with LBNET LBnet.cz s.r.o. 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 AS201931 page?

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

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

Related topics