Country
—
ASN LANDING PAGE
SK-TELEKOM - Slovak Telekom, a.s.
Last updated · Apr 4, 2026
Country
—
Total prefixes
44
IPv4 prefixes
36
IPv6 prefixes
8
SK-TELEKOM - Slovak Telekom, a.s. currently shows 44 prefixes and 52 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.
SK-TELEKOM - Slovak Telekom, a.s. 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.
AS43542
AS43542
—
AS13036
AS13036
—
AS201603
AS201603
—
AS60829
AS60829
—
AS39904
AS39904
—
AS201841
AS201841
—
AS29148
AS29148
—
AS204690
AS204690
—
AS49117
AS49117
—
AS50881
AS50881
—
AS56955
AS56955
—
AS214945
AS214945
—
AS12767
AS12767
—
AS202876
AS202876
—
AS207696
AS207696
—
AS35096
AS35096
—
AS47749
AS47749
—
AS203208
AS203208
—
AS198494
AS198494
—
AS12344
AS12344
—
AS196861
AS196861
—
AS214396
AS214396
—
AS30929
AS30929
—
AS200355
AS200355
—
AS21433
AS21433
—
AS48298
AS48298
—
AS202564
AS202564
—
AS48907
AS48907
—
AS44234
AS44234
—
AS30898
AS30898
—
AS210117
AS210117
—
AS211731
AS211731
—
AS57788
AS57788
—
AS48574
AS48574
—
AS201447
AS201447
—
AS208329
AS208329
—
AS25093
AS25093
—
AS34475
AS34475
—
AS56891
AS56891
—
AS202830
AS202830
—
| Prefix | Name | Country |
|---|---|---|
| 178.40.0.0/15 | AS6855 | — |
| 185.58.102.0/24 | AS6855 | — |
| 185.58.103.0/24 | AS6855 | — |
| 193.200.143.0/24 | AS6855 | — |
| 193.201.110.0/24 | AS6855 | — |
| 193.84.245.0/24 | AS6855 | — |
| 193.84.7.0/24 | AS6855 | — |
| 193.84.96.0/24 | AS6855 | — |
| 193.84.97.0/24 | AS6855 | — |
| 193.84.98.0/23 | AS6855 | — |
| 194.154.224.0/19 | AS6855 | — |
| 194.169.224.0/24 | AS6855 | — |
| 194.48.241.0/24 | AS6855 | — |
| 194.50.215.0/24 | AS6855 | — |
| 195.146.128.0/19 | AS6855 | — |
| 195.146.130.0/24 | AS6855 | — |
| 195.216.240.0/24 | AS6855 | — |
| 195.91.0.0/17 | AS6855 | — |
| 2001:678:c14::/48 | AS6855 | — |
| 2001:67c:16c0::/48 | AS6855 | — |
| 2001:67c:1bc4::/48 | AS6855 | — |
| 2001:67c:2cc0::/48 | AS6855 | — |
| 2001:67c:2f9c::/48 | AS6855 | — |
| 212.5.192.0/19 | AS6855 | — |
| 213.160.160.0/19 | AS6855 | — |
| 213.81.128.0/17 | AS6855 | — |
| 2a00:12a8::/29 | AS6855 | — |
| 2a00:6bc0::/40 | AS6855 | — |
| 2a01:5f7::/32 | AS6855 | — |
| 78.98.0.0/15 | AS6855 | — |
| 84.47.0.0/17 | AS6855 | — |
| 85.239.68.0/24 | AS6855 | — |
| 85.239.69.0/24 | AS6855 | — |
| 85.239.80.0/23 | AS6855 | — |
| 85.239.82.0/23 | AS6855 | — |
| 85.239.84.0/22 | AS6855 | — |
| 85.248.31.0/24 | AS6855 | — |
| 85.248.74.0/24 | AS6855 | — |
| 87.197.0.0/16 | AS6855 | — |
| 91.127.0.0/16 | AS6855 | — |
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.
AS6855 is an autonomous system number used to identify an independently operated network. The current page associates it with SK-TELEKOM - Slovak Telekom, a.s. 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 AS6855. 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 AS6855, 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.