Country
—
ASN LANDING PAGE
T-HT - Hrvatski Telekom d.d.
Last updated · Apr 4, 2026
Country
—
Total prefixes
48
IPv4 prefixes
46
IPv6 prefixes
2
T-HT - Hrvatski Telekom d.d. currently shows 48 prefixes and 54 upstream, downstream, or peer relationships. Larger prefix inventories often indicate broader network footprint, but they should still be read together with country and peering context.
ASN landing pages are more useful than a single IP page when you want cloud provider attribution, routing research, infrastructure comparison, or network topology analysis at the organization level.
T-HT - Hrvatski Telekom d.d. is currently associated with an unknown region. Country data is only a starting point; the more important signals are the organization name, website, prefix volume, and peering relationships that reveal whether the network behaves like a cloud platform, ISP, CDN, or enterprise backbone.
This page is currently showing live ASN data that can be used for peer, prefix, and network scale analysis. The most useful next step is usually to return to a related IP landing page, then compare that concrete address with this ASN profile and with broader topic pages for routing, cloud attribution, or WHOIS ownership analysis.
Detailed data for this ASN is not available right now.
AS8585
AS8585
—
AS13046
AS13046
—
AS25144
AS25144
—
AS9146
AS9146
—
AS20875
AS20875
—
AS35567
AS35567
—
AS214427
AS214427
—
AS25365
AS25365
—
AS211191
AS211191
—
AS44377
AS44377
—
AS203463
AS203463
—
AS200990
AS200990
—
AS15719
AS15719
—
AS197823
AS197823
—
AS21323
AS21323
—
AS30841
AS30841
—
AS35128
AS35128
—
AS50410
AS50410
—
AS201987
AS201987
—
AS59866
AS59866
—
AS215045
AS215045
—
AS199433
AS199433
—
AS61094
AS61094
—
AS210485
AS210485
—
AS59786
AS59786
—
AS44260
AS44260
—
AS42488
AS42488
—
AS196622
AS196622
—
AS43394
AS43394
—
AS212453
AS212453
—
AS209434
AS209434
—
AS207517
AS207517
—
AS197716
AS197716
—
AS35225
AS35225
—
AS35416
AS35416
—
AS204163
AS204163
—
AS49498
AS49498
—
AS58312
AS58312
—
AS203876
AS203876
—
AS201850
AS201850
—
| Prefix | Name | Country |
|---|---|---|
| 178.160.0.0/17 | AS5391 | — |
| 178.160.0.0/18 | AS5391 | — |
| 188.125.0.0/20 | AS5391 | — |
| 194.152.192.0/18 | AS5391 | — |
| 195.29.0.0/16 | AS5391 | — |
| 195.29.0.0/18 | AS5391 | — |
| 195.29.128.0/18 | AS5391 | — |
| 195.29.192.0/18 | AS5391 | — |
| 195.29.64.0/18 | AS5391 | — |
| 213.202.71.0/24 | AS5391 | — |
| 2a00:c30::/29 | AS5391 | — |
| 2a00:c30::/32 | AS5391 | — |
| 31.216.192.0/19 | AS5391 | — |
| 31.217.0.0/17 | AS5391 | — |
| 31.217.0.0/19 | AS5391 | — |
| 31.217.32.0/19 | AS5391 | — |
| 31.217.64.0/19 | AS5391 | — |
| 31.217.96.0/19 | AS5391 | — |
| 46.188.128.0/17 | AS5391 | — |
| 46.188.128.0/19 | AS5391 | — |
| 46.188.160.0/19 | AS5391 | — |
| 46.188.192.0/20 | AS5391 | — |
| 46.188.208.0/21 | AS5391 | — |
| 46.188.224.0/19 | AS5391 | — |
| 78.0.0.0/16 | AS5391 | — |
| 78.1.0.0/16 | AS5391 | — |
| 78.2.0.0/16 | AS5391 | — |
| 78.3.0.0/16 | AS5391 | — |
| 83.131.0.0/16 | AS5391 | — |
| 83.131.0.0/18 | AS5391 | — |
| 83.131.8.0/24 | AS5391 | — |
| 87.252.128.0/19 | AS5391 | — |
| 87.252.128.0/20 | AS5391 | — |
| 87.252.144.0/22 | AS5391 | — |
| 87.252.148.0/23 | AS5391 | — |
| 87.252.150.0/24 | AS5391 | — |
| 87.252.152.0/22 | AS5391 | — |
| 89.172.0.0/16 | AS5391 | — |
| 93.136.0.0/16 | AS5391 | — |
| 93.137.0.0/16 | AS5391 | — |
A strong reference ASN for Google DNS, Google Cloud, and global network footprint analysis.
Useful for analyzing CDN, Anycast, WAF, and large-scale edge network behavior.
Helpful when comparing Azure, enterprise backbone, and large-cloud routing patterns.
A useful ASN landing page for understanding AWS and large cloud-network ownership.
Continue from this ASN into the differences between WHOIS ownership and ASN ownership.
Continue from this ASN into route troubleshooting and network analysis.
Useful when you want to compare this ASN against larger cloud and edge networks.
Continue from the ASN page into WHOIS and ownership verification.
AS5391 is an autonomous system number used to identify an independently operated network. The current page associates it with T-HT - Hrvatski Telekom d.d. in an unknown region, which helps determine whether it behaves like a cloud provider, ISP, CDN, or enterprise backbone.
They help explain the scale, interconnection depth, and route structure of AS5391. Richer peering and upstream data often indicate broader network reach, but they should still be interpreted together with prefixes and related IP landing pages.
The best next step is usually to return to a concrete IP landing page to see how a specific address maps into AS5391, then continue into cloud, WHOIS, or routing topic pages to understand the network in a broader context.
Understand why WHOIS ownership and ASN ownership can differ, and how to combine both when deciding who really owns or operates an IP.
Use WHOIS, ASN, prefixes, and organization data to determine who ultimately owns an IP, range, or resolved domain target.
Learn what ASN, BGP routes, prefixes, upstreams, downstreams, and peers mean, then explore real ASN pages.
Compare large cloud and edge networks such as Google, Cloudflare, Microsoft, and Amazon through their ASN landing pages.