Country
—
ASN LANDING PAGE
AS-PTD - PenTeleData Inc.
Last updated · Apr 4, 2026
Country
—
Total prefixes
28
IPv4 prefixes
27
IPv6 prefixes
1
AS-PTD - PenTeleData Inc. currently shows 28 prefixes and 59 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.
AS-PTD - PenTeleData Inc. 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.
AS397369
AS397369
—
AS394893
AS394893
—
AS14369
AS14369
—
AS14789
AS14789
—
AS29899
AS29899
—
AS19839
AS19839
—
AS398191
AS398191
—
AS16478
AS16478
—
AS395631
AS395631
—
AS16548
AS16548
—
AS14928
AS14928
—
AS22841
AS22841
—
AS62720
AS62720
—
AS394305
AS394305
—
AS63289
AS63289
—
AS19096
AS19096
—
AS394884
AS394884
—
AS27621
AS27621
—
AS53775
AS53775
—
AS396462
AS396462
—
AS399437
AS399437
—
AS21516
AS21516
—
AS6128
AS6128
—
AS396020
AS396020
—
AS30153
AS30153
—
AS396269
AS396269
—
AS15239
AS15239
—
AS32162
AS32162
—
AS14773
AS14773
—
AS22580
AS22580
—
AS27246
AS27246
—
AS46350
AS46350
—
AS400400
AS400400
—
AS53718
AS53718
—
AS40591
AS40591
—
AS401728
AS401728
—
AS6169
AS6169
—
AS6461
AS6461
—
AS3356
AS3356
—
AS3257
AS3257
—
AS6939
AS6939
—
AS19151
AS19151
—
AS286
AS286
—
AS1828
AS1828
—
AS49544
AS49544
—
AS37468
AS37468
—
AS137409
AS137409
—
AS6057
AS6057
—
AS13786
AS13786
—
AS24482
AS24482
—
AS52320
AS52320
—
AS36236
AS36236
—
AS37721
AS37721
—
AS835
AS835
—
AS7195
AS7195
—
AS6204
AS6204
—
AS35280
AS35280
—
AS60171
AS60171
—
AS58057
AS58057
—
| Prefix | Name | Country |
|---|---|---|
| 104.36.124.0/22 | AS3737 | — |
| 146.12.0.0/17 | AS3737 | — |
| 204.186.0.0/16 | AS3737 | — |
| 204.186.176.0/24 | AS3737 | — |
| 204.186.192.0/21 | AS3737 | — |
| 207.44.0.0/17 | AS3737 | — |
| 209.173.0.0/19 | AS3737 | — |
| 209.50.128.0/19 | AS3737 | — |
| 209.50.150.0/24 | AS3737 | — |
| 216.144.160.0/19 | AS3737 | — |
| 216.49.0.0/18 | AS3737 | — |
| 24.102.128.0/17 | AS3737 | — |
| 24.102.192.0/19 | AS3737 | — |
| 24.115.0.0/16 | AS3737 | — |
| 24.152.192.0/18 | AS3737 | — |
| 24.229.0.0/16 | AS3737 | — |
| 24.238.32.0/19 | AS3737 | — |
| 24.238.64.0/19 | AS3737 | — |
| 24.246.224.0/19 | AS3737 | — |
| 24.55.128.0/19 | AS3737 | — |
| 2606:9400::/32 | AS3737 | — |
| 50.29.128.0/17 | AS3737 | — |
| 64.67.0.0/16 | AS3737 | — |
| 66.152.128.0/19 | AS3737 | — |
| 69.12.12.0/22 | AS3737 | — |
| 70.15.0.0/16 | AS3737 | — |
| 70.44.0.0/16 | AS3737 | — |
| 75.97.0.0/16 | AS3737 | — |
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.
AS3737 is an autonomous system number used to identify an independently operated network. The current page associates it with AS-PTD - PenTeleData Inc. 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 AS3737. 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 AS3737, 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.