Country
—
ASN LANDING PAGE
KEYWEB-AS - Keyweb AG
Last updated · Apr 4, 2026
Country
—
Total prefixes
37
IPv4 prefixes
36
IPv6 prefixes
1
KEYWEB-AS - Keyweb AG currently shows 37 prefixes and 43 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.
KEYWEB-AS - Keyweb AG 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.
AS33891
AS33891
—
AS6939
AS6939
—
AS174
AS174
—
AS3223
AS3223
—
AS5405
AS5405
—
AS34549
AS34549
—
AS3214
AS3214
—
AS35625
AS35625
—
AS13030
AS13030
—
AS20764
AS20764
—
AS34019
AS34019
—
AS35280
AS35280
—
AS29691
AS29691
—
AS34927
AS34927
—
AS39351
AS39351
—
AS48362
AS48362
—
AS8298
AS8298
—
AS25091
AS25091
—
AS29075
AS29075
—
AS137409
AS137409
—
AS6057
AS6057
—
AS12779
AS12779
—
AS20485
AS20485
—
AS34177
AS34177
—
AS37100
AS37100
—
AS37468
AS37468
—
AS41327
AS41327
—
AS52320
AS52320
—
AS8218
AS8218
—
AS14840
AS14840
—
AS553
AS553
—
AS559
AS559
—
AS1267
AS1267
—
AS3212
AS3212
—
AS6424
AS6424
—
AS8758
AS8758
—
AS14630
AS14630
—
AS15958
AS15958
—
AS21412
AS21412
—
AS24961
AS24961
—
| Prefix | Name | Country |
|---|---|---|
| 130.117.189.0/24 | AS31103 | — |
| 193.7.184.0/24 | AS31103 | — |
| 195.160.228.0/24 | AS31103 | — |
| 195.160.229.0/24 | AS31103 | — |
| 195.160.230.0/24 | AS31103 | — |
| 195.160.231.0/24 | AS31103 | — |
| 2001:1b60::/29 | AS31103 | — |
| 217.114.208.0/20 | AS31103 | — |
| 62.141.48.0/21 | AS31103 | — |
| 62.141.56.0/22 | AS31103 | — |
| 62.141.60.0/23 | AS31103 | — |
| 84.19.160.0/19 | AS31103 | — |
| 84.19.174.0/24 | AS31103 | — |
| 84.19.182.0/24 | AS31103 | — |
| 84.19.188.0/24 | AS31103 | — |
| 87.118.114.0/24 | AS31103 | — |
| 87.118.126.0/24 | AS31103 | — |
| 87.118.64.0/18 | AS31103 | — |
| 87.118.67.0/24 | AS31103 | — |
| 87.118.68.0/24 | AS31103 | — |
| 87.118.86.0/24 | AS31103 | — |
| 87.118.90.0/24 | AS31103 | — |
| 87.118.91.0/24 | AS31103 | — |
| 87.118.92.0/24 | AS31103 | — |
| 91.213.60.0/24 | AS31103 | — |
| 95.169.160.0/24 | AS31103 | — |
| 95.169.161.0/24 | AS31103 | — |
| 95.169.169.0/24 | AS31103 | — |
| 95.169.181.0/24 | AS31103 | — |
| 95.169.182.0/24 | AS31103 | — |
| 95.169.183.0/24 | AS31103 | — |
| 95.169.184.0/22 | AS31103 | — |
| 95.169.186.0/24 | AS31103 | — |
| 95.169.187.0/24 | AS31103 | — |
| 95.169.188.0/24 | AS31103 | — |
| 95.169.189.0/24 | AS31103 | — |
| 95.169.190.0/23 | AS31103 | — |
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.
AS31103 is an autonomous system number used to identify an independently operated network. The current page associates it with KEYWEB-AS - Keyweb AG 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 AS31103. 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 AS31103, 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.