Country
—
ASN LANDING PAGE
IN-BERLIN-AS - Individual Network Berlin ("IN-Berlin") e.V.
Last updated · Apr 4, 2026
Country
—
Total prefixes
13
IPv4 prefixes
7
IPv6 prefixes
6
IN-BERLIN-AS - Individual Network Berlin ("IN-Berlin") e.V. currently shows 13 prefixes and 64 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.
IN-BERLIN-AS - Individual Network Berlin ("IN-Berlin") e.V. 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.
AS208135
AS208135
—
AS59645
AS59645
—
AS57024
AS57024
—
AS47496
AS47496
—
AS212520
AS212520
—
AS48387
AS48387
—
AS60802
AS60802
—
AS60729
AS60729
—
AS200490
AS200490
—
AS207510
AS207510
—
AS213341
AS213341
—
AS213997
AS213997
—
AS213674
AS213674
—
AS205740
AS205740
—
AS49933
AS49933
—
AS205591
AS205591
—
AS215236
AS215236
—
AS200273
AS200273
—
AS211939
AS211939
—
AS21158
AS21158
—
AS200827
AS200827
—
AS201701
AS201701
—
AS112
AS112
—
AS204082
AS204082
—
AS5405
AS5405
—
AS33891
AS33891
—
AS9002
AS9002
—
AS6939
AS6939
—
AS13030
AS13030
—
AS50629
AS50629
—
AS3320
AS3320
—
AS29632
AS29632
—
AS9136
AS9136
—
AS34019
AS34019
—
AS8298
AS8298
—
AS37468
AS37468
—
AS8218
AS8218
—
AS49434
AS49434
—
AS37100
AS37100
—
AS39351
AS39351
—
AS14907
AS14907
—
AS25091
AS25091
—
AS680
AS680
—
AS1140
AS1140
—
AS205112
AS205112
—
AS1103
AS1103
—
AS3333
AS3333
—
AS20485
AS20485
—
AS29140
AS29140
—
AS56987
AS56987
—
AS204092
AS204092
—
AS212483
AS212483
—
AS553
AS553
—
AS20932
AS20932
—
AS24482
AS24482
—
AS24961
AS24961
—
AS42541
AS42541
—
AS62167
AS62167
—
AS64475
AS64475
—
AS199938
AS199938
—
AS45489
AS45489
—
AS49544
AS49544
—
AS17639
AS17639
—
AS25220
AS25220
—
| Prefix | Name | Country |
|---|---|---|
| 185.177.204.0/22 | AS29670 | — |
| 192.109.21.0/24 | AS29670 | — |
| 192.109.42.0/24 | AS29670 | — |
| 192.109.82.0/24 | AS29670 | — |
| 193.29.188.0/24 | AS29670 | — |
| 193.96.24.0/24 | AS29670 | — |
| 2001:67c:1400::/45 | AS29670 | — |
| 2001:67c:1403::/48 | AS29670 | — |
| 2001:67c:fb8::/48 | AS29670 | — |
| 2001:bf0:c000::/35 | AS29670 | — |
| 2001:bf6::/32 | AS29670 | — |
| 217.197.80.0/20 | AS29670 | — |
| 2a0a:4580::/29 | AS29670 | — |
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.
AS29670 is an autonomous system number used to identify an independently operated network. The current page associates it with IN-BERLIN-AS - Individual Network Berlin ("IN-Berlin") e.V. 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 AS29670. 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 AS29670, 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.