ASN LANDING PAGE

AS198713

GALAS-NET Piotr Galas

Last updated · Jul 20, 2026

Country

Total prefixes

2

IPv4 prefixes

2

IPv6 prefixes

0

ASN summary

How to read the scale of AS198713

GALAS-NET Piotr Galas currently reports 2 prefixes and 4 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?

GALAS-NET Piotr Galas 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 AS198713 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

AS198713 ASN lookupAS198713 BGPAS198713 peersAS198713 prefixesAS198713 upstreamsGALAS-NET Piotr Galas 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
176.112.112.0/21AS198713
91.237.112.0/23AS198713

Related ASN pages

Related lookups and next steps

Frequently asked questions about this ASN page

What does AS198713 represent?

AS198713 is an autonomous system number. The current source associates it with GALAS-NET Piotr Galas 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 AS198713 page?

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

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

Related topics