ASN LANDING PAGE

AS53112

AS53112 - SULNET TELECOM

Last updated · Jul 20, 2026

Country

Total prefixes

10

IPv4 prefixes

6

IPv6 prefixes

4

ASN summary

How to read the scale of AS53112

AS53112 - SULNET TELECOM currently reports 10 prefixes and 7 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?

AS53112 - SULNET TELECOM 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 AS53112 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

AS53112 ASN lookupAS53112 BGPAS53112 peersAS53112 prefixesAS53112 upstreamsAS53112 - SULNET TELECOM ASN

Upstreams

Detailed data for this ASN is not available right now.

Prefix inventory

PrefixNameCountry
138.97.4.0/22AS53112
143.255.60.0/22AS53112
170.231.72.0/22AS53112
177.23.8.0/21AS53112
187.109.16.0/20AS53112
189.90.144.0/20AS53112
2804:d0c:7e01::/48AS53112
2804:d0c:8000::/40AS53112
2804:d0c::/32AS53112
2804:d0c::/36AS53112

Related ASN pages

Related lookups and next steps

Frequently asked questions about this ASN page

What does AS53112 represent?

AS53112 is an autonomous system number. The current source associates it with AS53112 - SULNET TELECOM 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 AS53112 page?

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

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

Related topics