Country
—
ASN LANDING PAGE
NSS S.A.
Last updated · Apr 4, 2026
Country
—
Total prefixes
422
IPv4 prefixes
363
IPv6 prefixes
59
NSS S.A. currently shows 422 prefixes and 46 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.
NSS S.A. 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.
AS52376
AS52376
—
AS273044
AS273044
—
AS264619
AS264619
—
AS61493
AS61493
—
AS267913
AS267913
—
AS270105
AS270105
—
AS262249
AS262249
—
AS267710
AS267710
—
AS13335
AS13335
—
AS19889
AS19889
—
AS27690
AS27690
—
AS27691
AS27691
—
AS52321
AS52321
—
AS52270
AS52270
—
AS10277
AS10277
—
AS27898
AS27898
—
AS52283
AS52283
—
AS15034
AS15034
—
AS263769
AS263769
—
AS273240
AS273240
—
AS7340
AS7340
—
AS27692
AS27692
—
AS264743
AS264743
—
AS273865
AS273865
—
AS20321
AS20321
—
AS264678
AS264678
—
AS266660
AS266660
—
AS269766
AS269766
—
AS273050
AS273050
—
AS264622
AS264622
—
AS267681
AS267681
—
AS28052
AS28052
—
AS264638
AS264638
—
AS262264
AS262264
—
AS40703
AS40703
—
AS266705
AS266705
—
AS27711
AS27711
—
AS262192
AS262192
—
AS16921
AS16921
—
AS262201
AS262201
—
| Prefix | Name | Country |
|---|---|---|
| 186.189.224.0/20 | AS16814 | — |
| 186.189.224.0/22 | AS16814 | — |
| 186.189.228.0/22 | AS16814 | — |
| 186.189.232.0/22 | AS16814 | — |
| 186.189.236.0/22 | AS16814 | — |
| 186.189.248.0/22 | AS16814 | — |
| 190.2.0.0/19 | AS16814 | — |
| 190.2.0.0/22 | AS16814 | — |
| 190.2.0.0/24 | AS16814 | — |
| 190.2.10.0/24 | AS16814 | — |
| 190.2.11.0/24 | AS16814 | — |
| 190.2.12.0/22 | AS16814 | — |
| 190.2.12.0/24 | AS16814 | — |
| 190.2.13.0/24 | AS16814 | — |
| 190.2.14.0/24 | AS16814 | — |
| 190.2.15.0/24 | AS16814 | — |
| 190.2.16.0/22 | AS16814 | — |
| 190.2.16.0/24 | AS16814 | — |
| 190.2.18.0/24 | AS16814 | — |
| 190.2.2.0/24 | AS16814 | — |
| 190.2.20.0/22 | AS16814 | — |
| 190.2.24.0/22 | AS16814 | — |
| 190.2.24.0/24 | AS16814 | — |
| 190.2.28.0/22 | AS16814 | — |
| 190.2.29.0/24 | AS16814 | — |
| 190.2.32.0/19 | AS16814 | — |
| 190.2.32.0/22 | AS16814 | — |
| 190.2.32.0/24 | AS16814 | — |
| 190.2.33.0/24 | AS16814 | — |
| 190.2.34.0/24 | AS16814 | — |
| 190.2.35.0/24 | AS16814 | — |
| 190.2.36.0/22 | AS16814 | — |
| 190.2.36.0/24 | AS16814 | — |
| 190.2.37.0/24 | AS16814 | — |
| 190.2.38.0/24 | AS16814 | — |
| 190.2.39.0/24 | AS16814 | — |
| 190.2.4.0/22 | AS16814 | — |
| 190.2.40.0/22 | AS16814 | — |
| 190.2.40.0/24 | AS16814 | — |
| 190.2.41.0/24 | AS16814 | — |
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.
AS16814 is an autonomous system number used to identify an independently operated network. The current page associates it with NSS S.A. 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 AS16814. 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 AS16814, 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.