Country
—
ASN LANDING PAGE
RITTERNET - Ritter Communications
Last updated · Apr 4, 2026
Country
—
Total prefixes
92
IPv4 prefixes
89
IPv6 prefixes
3
RITTERNET - Ritter Communications currently shows 92 prefixes and 51 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.
RITTERNET - Ritter Communications 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.
AS21852
AS21852
—
AS22413
AS22413
—
AS31942
AS31942
—
AS14770
AS14770
—
AS400446
AS400446
—
AS46986
AS46986
—
AS399331
AS399331
—
AS20030
AS20030
—
AS18889
AS18889
—
AS53435
AS53435
—
AS21725
AS21725
—
AS47041
AS47041
—
AS395422
AS395422
—
AS2933
AS2933
—
AS35894
AS35894
—
AS46760
AS46760
—
AS46283
AS46283
—
AS396305
AS396305
—
AS400002
AS400002
—
AS395041
AS395041
—
AS36095
AS36095
—
AS398192
AS398192
—
AS14693
AS14693
—
AS46792
AS46792
—
AS16788
AS16788
—
AS399493
AS399493
—
AS22408
AS22408
—
AS398159
AS398159
—
AS32955
AS32955
—
AS400146
AS400146
—
AS396093
AS396093
—
| Prefix | Name | Country |
|---|---|---|
| 162.245.44.0/22 | AS23404 | — |
| 162.245.44.0/24 | AS23404 | — |
| 162.245.45.0/24 | AS23404 | — |
| 162.245.47.0/24 | AS23404 | — |
| 198.148.28.0/22 | AS23404 | — |
| 198.148.28.0/24 | AS23404 | — |
| 198.148.31.0/24 | AS23404 | — |
| 199.38.124.0/22 | AS23404 | — |
| 207.65.41.0/24 | AS23404 | — |
| 207.65.47.0/24 | AS23404 | — |
| 207.65.56.0/22 | AS23404 | — |
| 207.65.57.0/24 | AS23404 | — |
| 207.65.58.0/24 | AS23404 | — |
| 207.65.59.0/24 | AS23404 | — |
| 216.163.0.0/19 | AS23404 | — |
| 216.163.0.0/24 | AS23404 | — |
| 216.163.18.0/24 | AS23404 | — |
| 216.163.19.0/24 | AS23404 | — |
| 216.163.2.0/24 | AS23404 | — |
| 216.163.21.0/24 | AS23404 | — |
| 216.163.22.0/24 | AS23404 | — |
| 216.163.23.0/24 | AS23404 | — |
| 216.163.24.0/24 | AS23404 | — |
| 216.163.26.0/24 | AS23404 | — |
| 216.163.29.0/24 | AS23404 | — |
| 216.163.31.0/24 | AS23404 | — |
| 216.163.4.0/24 | AS23404 | — |
| 216.163.6.0/24 | AS23404 | — |
| 216.163.7.0/24 | AS23404 | — |
| 2607:fa08:800::/40 | AS23404 | — |
| 2607:fa08:900::/40 | AS23404 | — |
| 2607:fa08::/32 | AS23404 | — |
| 64.178.176.0/24 | AS23404 | — |
| 64.178.180.0/24 | AS23404 | — |
| 64.178.184.0/24 | AS23404 | — |
| 64.178.185.0/24 | AS23404 | — |
| 64.178.187.0/24 | AS23404 | — |
| 64.178.190.0/24 | AS23404 | — |
| 64.178.191.0/24 | AS23404 | — |
| 64.233.128.0/19 | AS23404 | — |
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.
AS23404 is an autonomous system number used to identify an independently operated network. The current page associates it with RITTERNET - Ritter Communications 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 AS23404. 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 AS23404, 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.