Country
—
ASN LANDING PAGE
ACCESSKENYA-KE
Last updated · Apr 4, 2026
Country
—
Total prefixes
73
IPv4 prefixes
71
IPv6 prefixes
2
ACCESSKENYA-KE currently shows 73 prefixes and 36 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.
ACCESSKENYA-KE 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.
AS12556
AS12556
—
AS328201
AS328201
—
AS328637
AS328637
—
AS37166
AS37166
—
AS329341
AS329341
—
AS32806
AS32806
—
AS328087
AS328087
—
AS37535
AS37535
—
AS328978
AS328978
—
AS36904
AS36904
—
AS329026
AS329026
—
AS327753
AS327753
—
AS37319
AS37319
—
AS37156
AS37156
—
AS328089
AS328089
—
AS37019
AS37019
—
AS329562
AS329562
—
AS36948
AS36948
—
AS328132
AS328132
—
AS327766
AS327766
—
AS328846
AS328846
—
AS329239
AS329239
—
AS329002
AS329002
—
| Prefix | Name | Country |
|---|---|---|
| 196.200.16.0/20 | AS15808 | — |
| 196.200.16.0/24 | AS15808 | — |
| 196.200.20.0/24 | AS15808 | — |
| 196.207.16.0/20 | AS15808 | — |
| 196.207.20.0/24 | AS15808 | — |
| 196.207.23.0/24 | AS15808 | — |
| 196.207.31.0/24 | AS15808 | — |
| 197.254.0.0/17 | AS15808 | — |
| 197.254.0.0/18 | AS15808 | — |
| 197.254.0.0/20 | AS15808 | — |
| 197.254.10.0/24 | AS15808 | — |
| 197.254.101.0/24 | AS15808 | — |
| 197.254.124.0/24 | AS15808 | — |
| 197.254.125.0/24 | AS15808 | — |
| 197.254.126.0/24 | AS15808 | — |
| 197.254.127.0/24 | AS15808 | — |
| 197.254.16.0/20 | AS15808 | — |
| 197.254.32.0/20 | AS15808 | — |
| 197.254.39.0/24 | AS15808 | — |
| 197.254.48.0/20 | AS15808 | — |
| 197.254.64.0/18 | AS15808 | — |
| 197.254.64.0/20 | AS15808 | — |
| 197.254.77.0/24 | AS15808 | — |
| 197.254.78.0/24 | AS15808 | — |
| 197.254.79.0/24 | AS15808 | — |
| 197.254.80.0/20 | AS15808 | — |
| 197.254.87.0/24 | AS15808 | — |
| 197.254.89.0/24 | AS15808 | — |
| 197.254.90.0/24 | AS15808 | — |
| 197.254.92.0/24 | AS15808 | — |
| 197.254.93.0/24 | AS15808 | — |
| 2c0f:fe88::/32 | AS15808 | — |
| 2c0f:ff90::/32 | AS15808 | — |
| 41.206.32.0/19 | AS15808 | — |
| 41.206.48.0/23 | AS15808 | — |
| 41.206.48.0/24 | AS15808 | — |
| 41.215.0.0/17 | AS15808 | — |
| 41.215.0.0/20 | AS15808 | — |
| 41.215.100.0/24 | AS15808 | — |
| 41.215.105.0/24 | AS15808 | — |
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.
AS15808 is an autonomous system number used to identify an independently operated network. The current page associates it with ACCESSKENYA-KE 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 AS15808. 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 AS15808, 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.