Country
—
ASN LANDING PAGE
NEDEL TELECOM
Last updated · Apr 4, 2026
Country
—
Total prefixes
54
IPv4 prefixes
23
IPv6 prefixes
31
NEDEL TELECOM currently shows 54 prefixes and 34 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.
NEDEL 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.
AS28146
AS28146
—
AS53062
AS53062
—
AS6939
AS6939
—
AS53085
AS53085
—
AS6057
AS6057
—
AS14840
AS14840
—
AS6424
AS6424
—
AS22548
AS22548
—
AS24482
AS24482
—
AS28634
AS28634
—
AS29049
AS29049
—
AS35280
AS35280
—
AS36236
AS36236
—
AS39120
AS39120
—
AS51185
AS51185
—
AS60503
AS60503
—
AS61573
AS61573
—
AS198150
AS198150
—
AS262427
AS262427
—
AS263152
AS263152
—
AS263237
AS263237
—
AS264479
AS264479
—
AS271253
AS271253
—
AS37721
AS37721
—
AS199524
AS199524
—
AS28624
AS28624
—
AS52863
AS52863
—
AS52873
AS52873
—
AS265964
AS265964
—
AS267259
AS267259
—
AS270547
AS270547
—
| Prefix | Name | Country |
|---|---|---|
| 168.196.44.0/22 | AS262360 | — |
| 168.196.44.0/23 | AS262360 | — |
| 168.196.46.0/23 | AS262360 | — |
| 177.125.240.0/21 | AS262360 | — |
| 177.125.240.0/22 | AS262360 | — |
| 177.125.240.0/23 | AS262360 | — |
| 177.125.242.0/23 | AS262360 | — |
| 177.125.244.0/22 | AS262360 | — |
| 177.125.244.0/23 | AS262360 | — |
| 177.125.246.0/23 | AS262360 | — |
| 177.223.112.0/20 | AS262360 | — |
| 177.223.112.0/22 | AS262360 | — |
| 177.223.112.0/23 | AS262360 | — |
| 177.223.114.0/23 | AS262360 | — |
| 177.223.116.0/22 | AS262360 | — |
| 177.223.116.0/23 | AS262360 | — |
| 177.223.118.0/23 | AS262360 | — |
| 177.223.120.0/22 | AS262360 | — |
| 177.223.120.0/23 | AS262360 | — |
| 177.223.122.0/23 | AS262360 | — |
| 177.223.124.0/22 | AS262360 | — |
| 177.223.124.0/23 | AS262360 | — |
| 177.223.126.0/23 | AS262360 | — |
| 2804:1410:1000::/36 | AS262360 | — |
| 2804:1410:2000::/35 | AS262360 | — |
| 2804:1410:2000::/36 | AS262360 | — |
| 2804:1410:3000::/36 | AS262360 | — |
| 2804:1410:4000::/34 | AS262360 | — |
| 2804:1410:4000::/35 | AS262360 | — |
| 2804:1410:4000::/36 | AS262360 | — |
| 2804:1410:5000::/36 | AS262360 | — |
| 2804:1410:6000::/35 | AS262360 | — |
| 2804:1410:6000::/36 | AS262360 | — |
| 2804:1410:7000::/36 | AS262360 | — |
| 2804:1410:8000::/33 | AS262360 | — |
| 2804:1410:8000::/34 | AS262360 | — |
| 2804:1410:8000::/35 | AS262360 | — |
| 2804:1410:8000::/36 | AS262360 | — |
| 2804:1410:9000::/36 | AS262360 | — |
| 2804:1410::/32 | AS262360 | — |
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.
AS262360 is an autonomous system number used to identify an independently operated network. The current page associates it with NEDEL 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 AS262360. 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 AS262360, 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.