Country
—
ASN LANDING PAGE
AS196714
TNETKOM-AS - Thueringer Netkom GmbH
Last updated · Apr 4, 2026
Total prefixes
9
IPv4 prefixes
6
IPv6 prefixes
3
ASN summary
How to read the scale of AS196714
TNETKOM-AS - Thueringer Netkom GmbH currently shows 9 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.
When is an ASN page most useful?
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.
How should you read the country, organization, and role of AS196714?
TNETKOM-AS - Thueringer Netkom 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.
What should you inspect next after the AS196714 page?
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.
Search intents this ASN page helps cover
AS196714 ASN lookupAS196714 BGPAS196714 peersAS196714 prefixesAS196714 upstreamsTNETKOM-AS - Thueringer Netkom GmbH ASN
Upstreams
Detailed data for this ASN is not available right now.
Downstreams
Peers
AS13237
AS13237
—
AS8220
AS8220
—
AS199284
AS199284
—
AS6939
AS6939
—
AS34549
AS34549
—
AS34019
AS34019
—
AS20764
AS20764
—
AS35280
AS35280
—
AS3214
AS3214
—
AS8298
AS8298
—
AS9002
AS9002
—
AS34927
AS34927
—
AS6057
AS6057
—
AS5405
AS5405
—
AS52320
AS52320
—
AS14840
AS14840
—
AS20485
AS20485
—
AS24961
AS24961
—
AS29632
AS29632
—
AS29691
AS29691
—
AS34177
AS34177
—
AS37100
AS37100
—
AS37468
AS37468
—
AS39351
AS39351
—
AS205112
AS205112
—
AS12779
AS12779
—
AS25091
AS25091
—
AS25220
AS25220
—
AS34288
AS34288
—
AS35360
AS35360
—
AS39120
AS39120
—
AS48919
AS48919
—
AS51184
AS51184
—
AS56987
AS56987
—
AS58057
AS58057
—
AS58299
AS58299
—
AS61573
AS61573
—
AS64475
AS64475
—
AS198150
AS198150
—
AS199938
AS199938
—
Prefix inventory
| Prefix | Name | Country |
|---|---|---|
| 109.73.16.0/20 | AS196714 | — |
| 171.33.184.0/21 | AS196714 | — |
| 185.38.11.0/24 | AS196714 | — |
| 185.38.8.0/22 | AS196714 | — |
| 2a02:2250::/32 | AS196714 | — |
| 2a04:7440::/30 | AS196714 | — |
| 2a04:8480::/30 | AS196714 | — |
| 31.3.80.0/21 | AS196714 | — |
| 91.137.0.0/18 | AS196714 | — |
Related ASN pages
AS15169 · Google
A strong reference ASN for Google DNS, Google Cloud, and global network footprint analysis.
AS13335 · Cloudflare
Useful for analyzing CDN, Anycast, WAF, and large-scale edge network behavior.
AS8075 · Microsoft
Helpful when comparing Azure, enterprise backbone, and large-cloud routing patterns.
AS16509 · Amazon
A useful ASN landing page for understanding AWS and large cloud-network ownership.
Related lookups and next steps
WHOIS vs ASN Ownership Guide
Continue from this ASN into the differences between WHOIS ownership and ASN ownership.
Routing Troubleshooting and Network Analysis
Continue from this ASN into route troubleshooting and network analysis.
Cloud Network and ASN Comparison
Useful when you want to compare this ASN against larger cloud and edge networks.
WHOIS and IP Ownership Guide
Continue from the ASN page into WHOIS and ownership verification.
Frequently asked questions about this ASN page
What does AS196714 represent?
AS196714 is an autonomous system number used to identify an independently operated network. The current page associates it with TNETKOM-AS - Thueringer Netkom GmbH in an unknown region, which helps determine whether it behaves like a cloud provider, ISP, CDN, or enterprise backbone.
What are peers, upstreams, and prefixes useful for on the AS196714 page?
They help explain the scale, interconnection depth, and route structure of AS196714. Richer peering and upstream data often indicate broader network reach, but they should still be interpreted together with prefixes and related IP landing pages.
What should you do after reviewing AS196714?
The best next step is usually to return to a concrete IP landing page to see how a specific address maps into AS196714, then continue into cloud, WHOIS, or routing topic pages to understand the network in a broader context.
Related topics
WHOIS vs ASN Ownership Guide
Understand why WHOIS ownership and ASN ownership can differ, and how to combine both when deciding who really owns or operates an IP.
WHOIS and IP Ownership Guide
Use WHOIS, ASN, prefixes, and organization data to determine who ultimately owns an IP, range, or resolved domain target.
BGP and ASN Basics Guide
Learn what ASN, BGP routes, prefixes, upstreams, downstreams, and peers mean, then explore real ASN pages.
Cloud Network and ASN Comparison
Compare large cloud and edge networks such as Google, Cloudflare, Microsoft, and Amazon through their ASN landing pages.