Country
—
ASN LANDING PAGE
AS29196
ENGINEER-NETWORKS-TELECOM-RU-AS - LLC "INZHENERNYE SETI - TELEKOM"
Last updated · Apr 4, 2026
Total prefixes
3
IPv4 prefixes
3
IPv6 prefixes
0
ASN summary
How to read the scale of AS29196
ENGINEER-NETWORKS-TELECOM-RU-AS - LLC "INZHENERNYE SETI - TELEKOM" currently shows 3 prefixes and 39 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 AS29196?
ENGINEER-NETWORKS-TELECOM-RU-AS - LLC "INZHENERNYE SETI - TELEKOM" 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 AS29196 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
AS29196 ASN lookupAS29196 BGPAS29196 peersAS29196 prefixesAS29196 upstreamsENGINEER-NETWORKS-TELECOM-RU-AS - LLC "INZHENERNYE SETI - TELEKOM" ASN
Upstreams
Detailed data for this ASN is not available right now.
Downstreams
Peers
AS3216
AS3216
—
AS20485
AS20485
—
AS9002
AS9002
—
AS6939
AS6939
—
AS9049
AS9049
—
AS48642
AS48642
—
AS50673
AS50673
—
AS8218
AS8218
—
AS41327
AS41327
—
AS56911
AS56911
—
AS3170
AS3170
—
AS13004
AS13004
—
AS15958
AS15958
—
AS44901
AS44901
—
AS205112
AS205112
—
AS208972
AS208972
—
AS215638
AS215638
—
AS56655
AS56655
—
AS6204
AS6204
—
AS6663
AS6663
—
AS9198
AS9198
—
AS24482
AS24482
—
AS29049
AS29049
—
AS37721
AS37721
—
AS39351
AS39351
—
AS42295
AS42295
—
AS48678
AS48678
—
AS48919
AS48919
—
AS49673
AS49673
—
AS60171
AS60171
—
AS200612
AS200612
—
AS209823
AS209823
—
AS35598
AS35598
—
AS43727
AS43727
—
Prefix inventory
| Prefix | Name | Country |
|---|---|---|
| 185.253.136.0/22 | AS29196 | — |
| 195.69.216.0/22 | AS29196 | — |
| 91.239.112.0/24 | AS29196 | — |
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 AS29196 represent?
AS29196 is an autonomous system number used to identify an independently operated network. The current page associates it with ENGINEER-NETWORKS-TELECOM-RU-AS - LLC "INZHENERNYE SETI - TELEKOM" 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 AS29196 page?
They help explain the scale, interconnection depth, and route structure of AS29196. 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 AS29196?
The best next step is usually to return to a concrete IP landing page to see how a specific address maps into AS29196, 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.