Country
—
ASN LANDING PAGE
i3B-AS oja.at GmbH
Last updated · Apr 10, 2026
Country
—
Total prefixes
46
IPv4 prefixes
43
IPv6 prefixes
3
i3B-AS oja.at GmbH currently shows 46 prefixes and 53 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.
i3B-AS oja.at GmbH 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.
AS8540
AS8540
—
AS6939
AS6939
—
AS33891
AS33891
—
AS34549
AS34549
—
AS34019
AS34019
—
AS34927
AS34927
—
AS35280
AS35280
—
AS6057
AS6057
—
AS29632
AS29632
—
AS34177
AS34177
—
AS35625
AS35625
—
AS8298
AS8298
—
AS5405
AS5405
—
AS13030
AS13030
—
AS20485
AS20485
—
AS14840
AS14840
—
AS12779
AS12779
—
AS24482
AS24482
—
AS42541
AS42541
—
AS48919
AS48919
—
AS58057
AS58057
—
AS58299
AS58299
—
AS64475
AS64475
—
AS212024
AS212024
—
AS264479
AS264479
—
AS3223
AS3223
—
AS6424
AS6424
—
AS8529
AS8529
—
AS15547
AS15547
—
AS25220
AS25220
—
AS29140
AS29140
—
AS35360
AS35360
—
AS199524
AS199524
—
AS559
AS559
—
AS680
AS680
—
AS13004
AS13004
—
AS20932
AS20932
—
AS25160
AS25160
—
AS52320
AS52320
—
AS56987
AS56987
—
| Prefix | Name | Country |
|---|---|---|
| 193.47.156.0/24 | AS39912 | — |
| 194.34.226.0/24 | AS39912 | — |
| 195.140.136.0/22 | AS39912 | — |
| 195.16.224.0/21 | AS39912 | — |
| 195.16.232.0/22 | AS39912 | — |
| 195.16.236.0/23 | AS39912 | — |
| 195.16.238.0/24 | AS39912 | — |
| 195.16.241.0/24 | AS39912 | — |
| 195.16.242.0/23 | AS39912 | — |
| 195.16.245.0/24 | AS39912 | — |
| 195.16.246.0/23 | AS39912 | — |
| 195.16.251.0/24 | AS39912 | — |
| 195.16.253.0/24 | AS39912 | — |
| 195.16.254.0/23 | AS39912 | — |
| 213.139.252.0/22 | AS39912 | — |
| 2a00:e98::/32 | AS39912 | — |
| 2a01:100::/32 | AS39912 | — |
| 2a01:f8::/32 | AS39912 | — |
| 37.186.0.0/22 | AS39912 | — |
| 37.186.16.0/21 | AS39912 | — |
| 37.186.4.0/24 | AS39912 | — |
| 37.186.6.0/23 | AS39912 | — |
| 37.186.8.0/21 | AS39912 | — |
| 77.220.112.0/22 | AS39912 | — |
| 77.220.120.0/21 | AS39912 | — |
| 77.220.96.0/20 | AS39912 | — |
| 78.142.112.0/22 | AS39912 | — |
| 78.142.116.0/23 | AS39912 | — |
| 78.142.122.0/23 | AS39912 | — |
| 78.142.124.0/22 | AS39912 | — |
| 78.142.64.0/23 | AS39912 | — |
| 78.142.68.0/22 | AS39912 | — |
| 78.142.72.0/21 | AS39912 | — |
| 78.142.96.0/20 | AS39912 | — |
| 81.94.48.0/22 | AS39912 | — |
| 81.94.52.0/23 | AS39912 | — |
| 81.94.54.0/24 | AS39912 | — |
| 81.94.56.0/21 | AS39912 | — |
| 91.206.224.0/23 | AS39912 | — |
| 92.42.16.0/22 | AS39912 | — |
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.
AS39912 is an autonomous system number used to identify an independently operated network. The current page associates it with i3B-AS oja.at GmbH 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 AS39912. 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 AS39912, 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.