Country
—
ASN LANDING PAGE
OARNET-AS - OARnet
Last updated · Apr 4, 2026
Country
—
Total prefixes
83
IPv4 prefixes
81
IPv6 prefixes
2
OARNET-AS - OARnet currently shows 83 prefixes and 59 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.
OARNET-AS - OARnet 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.
AS36794
AS36794
—
AS46491
AS46491
—
AS29709
AS29709
—
AS62724
AS62724
—
AS30712
AS30712
—
AS7925
AS7925
—
AS17135
AS17135
—
AS29941
AS29941
—
AS31921
AS31921
—
AS55194
AS55194
—
AS40252
AS40252
—
AS32666
AS32666
—
AS159
AS159
—
AS32234
AS32234
—
AS14200
AS14200
—
AS14734
AS14734
—
AS53568
AS53568
—
AS22968
AS22968
—
AS33254
AS33254
—
AS16426
AS16426
—
AS30499
AS30499
—
AS31777
AS31777
—
AS32178
AS32178
—
AS40553
AS40553
—
AS33030
AS33030
—
AS36368
AS36368
—
AS36831
AS36831
—
AS394061
AS394061
—
AS11446
AS11446
—
AS22320
AS22320
—
AS25822
AS25822
—
AS26247
AS26247
—
AS32513
AS32513
—
AS20126
AS20126
—
AS33167
AS33167
—
AS40732
AS40732
—
AS11050
AS11050
—
AS13501
AS13501
—
AS26898
AS26898
—
AS30290
AS30290
—
| Prefix | Name | Country |
|---|---|---|
| 130.108.0.0/16 | AS600 | — |
| 131.187.0.0/16 | AS600 | — |
| 131.238.28.0/24 | AS600 | — |
| 136.227.0.0/18 | AS600 | — |
| 136.227.128.0/21 | AS600 | — |
| 136.227.60.0/24 | AS600 | — |
| 140.141.0.0/17 | AS600 | — |
| 140.220.0.0/16 | AS600 | — |
| 140.228.0.0/20 | AS600 | — |
| 143.246.0.0/17 | AS600 | — |
| 144.50.0.0/16 | AS600 | — |
| 146.85.0.0/19 | AS600 | — |
| 146.85.160.0/19 | AS600 | — |
| 146.85.224.0/19 | AS600 | — |
| 146.85.32.0/19 | AS600 | — |
| 156.63.208.0/24 | AS600 | — |
| 157.134.0.0/16 | AS600 | — |
| 163.11.0.0/16 | AS600 | — |
| 192.131.123.0/24 | AS600 | — |
| 192.148.235.0/24 | AS600 | — |
| 192.148.236.0/22 | AS600 | — |
| 192.148.237.0/24 | AS600 | — |
| 192.148.240.0/21 | AS600 | — |
| 192.148.241.0/24 | AS600 | — |
| 192.148.248.0/22 | AS600 | — |
| 192.148.251.0/24 | AS600 | — |
| 192.150.115.0/24 | AS600 | — |
| 192.153.26.0/23 | AS600 | — |
| 192.153.28.0/22 | AS600 | — |
| 192.153.31.0/24 | AS600 | — |
| 192.153.32.0/21 | AS600 | — |
| 192.153.32.0/24 | AS600 | — |
| 192.153.40.0/23 | AS600 | — |
| 192.153.40.0/24 | AS600 | — |
| 192.232.16.0/20 | AS600 | — |
| 192.232.19.0/24 | AS600 | — |
| 192.68.223.0/24 | AS600 | — |
| 192.88.192.0/22 | AS600 | — |
| 192.88.193.0/24 | AS600 | — |
| 192.88.195.0/24 | AS600 | — |
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.
AS600 is an autonomous system number used to identify an independently operated network. The current page associates it with OARNET-AS - OARnet 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 AS600. 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 AS600, 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.