Country
—
ASN LANDING PAGE
Adylnet Telecom
Last updated · Apr 4, 2026
Country
—
Total prefixes
9
IPv4 prefixes
7
IPv6 prefixes
2
Adylnet Telecom currently shows 9 prefixes and 80 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.
Adylnet 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.
AS266181
AS266181
—
AS267470
AS267470
—
AS53169
AS53169
—
AS265198
AS265198
—
AS61609
AS61609
—
AS28605
AS28605
—
AS263656
AS263656
—
AS263384
AS263384
—
AS269656
AS269656
—
AS52600
AS52600
—
AS271247
AS271247
—
AS265264
AS265264
—
AS61765
AS61765
—
AS264216
AS264216
—
AS61893
AS61893
—
AS262741
AS262741
—
AS267507
AS267507
—
AS61914
AS61914
—
AS268321
AS268321
—
AS262587
AS262587
—
AS53230
AS53230
—
AS266534
AS266534
—
AS262985
AS262985
—
AS263442
AS263442
—
AS269427
AS269427
—
AS263018
AS263018
—
AS52610
AS52610
—
AS262458
AS262458
—
AS263948
AS263948
—
AS265141
AS265141
—
AS268762
AS268762
—
AS266037
AS266037
—
AS264434
AS264434
—
AS53174
AS53174
—
AS268218
AS268218
—
AS61729
AS61729
—
AS266632
AS266632
—
AS269140
AS269140
—
AS52799
AS52799
—
AS267033
AS267033
—
AS8167
AS8167
—
AS13786
AS13786
—
AS174
AS174
—
AS7195
AS7195
—
AS2914
AS2914
—
AS3356
AS3356
—
AS6939
AS6939
—
AS34549
AS34549
—
AS35280
AS35280
—
AS34927
AS34927
—
AS10429
AS10429
—
AS34019
AS34019
—
AS8298
AS8298
—
AS5405
AS5405
—
AS34177
AS34177
—
AS3214
AS3214
—
AS39351
AS39351
—
AS9002
AS9002
—
AS29632
AS29632
—
AS1103
AS1103
—
AS35625
AS35625
—
AS25091
AS25091
—
AS50304
AS50304
—
AS8758
AS8758
—
AS199524
AS199524
—
AS60503
AS60503
—
AS264409
AS264409
—
AS60068
AS60068
—
AS29075
AS29075
—
AS29691
AS29691
—
AS24482
AS24482
—
AS14907
AS14907
—
AS4230
AS4230
—
AS269956
AS269956
—
AS270014
AS270014
—
AS49544
AS49544
—
AS50763
AS50763
—
AS20485
AS20485
—
AS25160
AS25160
—
AS22652
AS22652
—
| Prefix | Name | Country |
|---|---|---|
| 177.221.184.0/22 | AS28283 | — |
| 177.72.224.0/21 | AS28283 | — |
| 187.0.0.0/20 | AS28283 | — |
| 187.103.224.0/19 | AS28283 | — |
| 189.14.224.0/20 | AS28283 | — |
| 200.240.224.0/19 | AS28283 | — |
| 201.148.244.0/22 | AS28283 | — |
| 2804:378::/32 | AS28283 | — |
| 2804:624::/32 | AS28283 | — |
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.
AS28283 is an autonomous system number used to identify an independently operated network. The current page associates it with Adylnet 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 AS28283. 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 AS28283, 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.