Country
—
ASN LANDING PAGE
IP TELECOM
Last updated · Apr 4, 2026
Country
—
Total prefixes
18
IPv4 prefixes
5
IPv6 prefixes
13
IP TELECOM currently shows 18 prefixes and 47 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.
IP TELECOM 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.
AS174
AS174
—
AS1299
AS1299
—
AS6939
AS6939
—
AS52468
AS52468
—
AS37468
AS37468
—
AS3257
AS3257
—
AS9498
AS9498
—
AS64049
AS64049
—
AS9002
AS9002
—
AS13335
AS13335
—
AS7195
AS7195
—
AS20485
AS20485
—
AS137409
AS137409
—
AS32787
AS32787
—
AS31133
AS31133
—
AS14840
AS14840
—
AS16735
AS16735
—
AS7713
AS7713
—
AS20764
AS20764
—
AS9318
AS9318
—
AS7049
AS7049
—
AS4800
AS4800
—
AS12741
AS12741
—
AS61832
AS61832
—
AS31500
AS31500
—
AS20473
AS20473
—
AS30844
AS30844
—
AS1828
AS1828
—
AS29049
AS29049
—
AS35598
AS35598
—
AS271253
AS271253
—
AS37662
AS37662
—
AS262589
AS262589
—
AS267613
AS267613
—
AS37100
AS37100
—
AS17557
AS17557
—
AS35280
AS35280
—
AS15830
AS15830
—
AS24482
AS24482
—
AS5405
AS5405
—
| Prefix | Name | Country |
|---|---|---|
| 138.122.60.0/22 | AS61573 | — |
| 138.122.60.0/24 | AS61573 | — |
| 138.122.61.0/24 | AS61573 | — |
| 138.122.62.0/24 | AS61573 | — |
| 138.122.63.0/24 | AS61573 | — |
| 2804:25e4:300::/48 | AS61573 | — |
| 2804:25e4:500::/40 | AS61573 | — |
| 2804:25e4:600::/48 | AS61573 | — |
| 2804:25e4:700::/40 | AS61573 | — |
| 2804:25e4:700::/48 | AS61573 | — |
| 2804:25e4:706::/48 | AS61573 | — |
| 2804:25e4:709::/48 | AS61573 | — |
| 2804:25e4:70a::/48 | AS61573 | — |
| 2804:25e4:70b::/48 | AS61573 | — |
| 2804:25e4:70d::/48 | AS61573 | — |
| 2804:25e4:800::/40 | AS61573 | — |
| 2804:25e4::/32 | AS61573 | — |
| 2804:25e4::/40 | AS61573 | — |
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.
AS61573 is an autonomous system number used to identify an independently operated network. The current page associates it with IP TELECOM 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 AS61573. 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 AS61573, 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.