ASN LANDING PAGE

AS394232

TELKEL-MTL - TelKel inc.

Last updated · Jul 20, 2026

Country

Total prefixes

10

IPv4 prefixes

8

IPv6 prefixes

2

ASN summary

How to read the scale of AS394232

TELKEL-MTL - TelKel inc. currently reports 10 prefixes and 3 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?

TELKEL-MTL - TelKel inc. 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 AS394232 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

AS394232 ASN lookupAS394232 BGPAS394232 peersAS394232 prefixesAS394232 upstreamsTELKEL-MTL - TelKel inc. ASN

Upstreams

Detailed data for this ASN is not available right now.

Prefix inventory

PrefixNameCountry
130.12.87.0/24AS394232
199.4.190.0/24AS394232
23.134.32.0/24AS394232
23.178.0.0/24AS394232
23.178.1.0/24AS394232
23.252.224.0/20AS394232
23.252.228.0/24AS394232
2604:d040::/32AS394232
2606:7480::/32AS394232
69.57.223.0/24AS394232

Related ASN pages

Related lookups and next steps

Frequently asked questions about this ASN page

What does AS394232 represent?

AS394232 is an autonomous system number. The current source associates it with TELKEL-MTL - TelKel inc. 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 AS394232 page?

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

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

Related topics