Country
—
ASN LANDING PAGE
ULAKNET - National Academic Network and Information Center
Last updated · Apr 4, 2026
Country
—
Total prefixes
36
IPv4 prefixes
34
IPv6 prefixes
2
ULAKNET - National Academic Network and Information Center currently shows 36 prefixes and 28 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.
ULAKNET - National Academic Network and Information Center 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.
AS24922
AS24922
—
AS1967
AS1967
—
AS9095
AS9095
—
AS5474
AS5474
—
AS207263
AS207263
—
AS31689
AS31689
—
AS24614
AS24614
—
AS8678
AS8678
—
AS8456
AS8456
—
AS12777
AS12777
—
AS205782
AS205782
—
AS213309
AS213309
—
AS2592
AS2592
—
AS8466
AS8466
—
AS42626
AS42626
—
AS48811
AS48811
—
AS206887
AS206887
—
AS211249
AS211249
—
AS210690
AS210690
—
AS15843
AS15843
—
AS212167
AS212167
—
AS44639
AS44639
—
AS201632
AS201632
—
AS215977
AS215977
—
AS8674
AS8674
—
| Prefix | Name | Country |
|---|---|---|
| 161.9.128.0/17 | AS8517 | — |
| 161.9.142.0/24 | AS8517 | — |
| 185.7.0.0/22 | AS8517 | — |
| 193.140.0.0/16 | AS8517 | — |
| 193.140.140.0/24 | AS8517 | — |
| 193.255.0.0/16 | AS8517 | — |
| 193.255.16.0/24 | AS8517 | — |
| 193.255.17.0/24 | AS8517 | — |
| 193.255.18.0/24 | AS8517 | — |
| 193.255.19.0/24 | AS8517 | — |
| 193.255.20.0/24 | AS8517 | — |
| 193.255.21.0/24 | AS8517 | — |
| 193.255.22.0/24 | AS8517 | — |
| 193.255.24.0/24 | AS8517 | — |
| 193.255.25.0/24 | AS8517 | — |
| 193.255.26.0/24 | AS8517 | — |
| 193.255.27.0/24 | AS8517 | — |
| 193.255.28.0/24 | AS8517 | — |
| 193.255.32.0/24 | AS8517 | — |
| 193.255.33.0/24 | AS8517 | — |
| 193.255.35.0/24 | AS8517 | — |
| 193.255.36.0/24 | AS8517 | — |
| 194.27.0.0/16 | AS8517 | — |
| 194.27.140.0/24 | AS8517 | — |
| 194.27.141.0/24 | AS8517 | — |
| 194.27.142.0/24 | AS8517 | — |
| 194.27.228.0/22 | AS8517 | — |
| 194.27.232.0/22 | AS8517 | — |
| 194.27.236.0/23 | AS8517 | — |
| 194.27.43.0/24 | AS8517 | — |
| 2001:a98:600::/48 | AS8517 | — |
| 2001:a98::/32 | AS8517 | — |
| 79.123.128.0/17 | AS8517 | — |
| 95.183.128.0/17 | AS8517 | — |
| 95.183.178.0/24 | AS8517 | — |
| 95.183.179.0/24 | AS8517 | — |
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.
AS8517 is an autonomous system number used to identify an independently operated network. The current page associates it with ULAKNET - National Academic Network and Information Center 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 AS8517. 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 AS8517, 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.