Country
—
ASN LANDING PAGE
TIMENET-AS TIMENET SPA
Last updated · Apr 10, 2026
Country
—
Total prefixes
35
IPv4 prefixes
35
IPv6 prefixes
0
TIMENET-AS TIMENET SPA currently shows 35 prefixes and 43 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.
TIMENET-AS TIMENET SPA 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.
AS41327
AS41327
—
AS12874
AS12874
—
AS3257
AS3257
—
AS3269
AS3269
—
AS9002
AS9002
—
AS6939
AS6939
—
AS6762
AS6762
—
AS3303
AS3303
—
AS8218
AS8218
—
AS25091
AS25091
—
AS24961
AS24961
—
AS12779
AS12779
—
AS5405
AS5405
—
AS50877
AS50877
—
AS51185
AS51185
—
AS5394
AS5394
—
AS12637
AS12637
—
AS14840
AS14840
—
AS15605
AS15605
—
AS20912
AS20912
—
AS39120
AS39120
—
AS57111
AS57111
—
AS286
AS286
—
AS4455
AS4455
—
AS6204
AS6204
—
AS8660
AS8660
—
AS13237
AS13237
—
AS20811
AS20811
—
AS24482
AS24482
—
AS49544
AS49544
—
AS49605
AS49605
—
AS49709
AS49709
—
AS56987
AS56987
—
AS59919
AS59919
—
AS60171
AS60171
—
AS137409
AS137409
—
AS198150
AS198150
—
AS212483
AS212483
—
AS214443
AS214443
—
AS216309
AS216309
—
| Prefix | Name | Country |
|---|---|---|
| 109.238.16.0/20 | AS51580 | — |
| 141.105.152.0/21 | AS51580 | — |
| 145.14.160.0/19 | AS51580 | — |
| 178.218.148.0/22 | AS51580 | — |
| 178.250.64.0/21 | AS51580 | — |
| 185.121.148.0/22 | AS51580 | — |
| 185.139.28.0/22 | AS51580 | — |
| 185.143.152.0/22 | AS51580 | — |
| 185.143.152.0/24 | AS51580 | — |
| 185.180.180.0/23 | AS51580 | — |
| 185.180.182.0/23 | AS51580 | — |
| 185.208.19.0/24 | AS51580 | — |
| 185.212.16.0/22 | AS51580 | — |
| 185.29.73.0/24 | AS51580 | — |
| 185.29.74.0/24 | AS51580 | — |
| 185.29.75.0/24 | AS51580 | — |
| 185.5.180.0/22 | AS51580 | — |
| 185.55.88.0/22 | AS51580 | — |
| 193.176.238.0/24 | AS51580 | — |
| 193.176.246.0/24 | AS51580 | — |
| 194.110.56.0/22 | AS51580 | — |
| 31.193.16.0/20 | AS51580 | — |
| 31.193.18.0/24 | AS51580 | — |
| 46.17.152.0/21 | AS51580 | — |
| 5.172.96.0/24 | AS51580 | — |
| 5.172.97.0/24 | AS51580 | — |
| 5.172.98.0/24 | AS51580 | — |
| 5.172.99.0/24 | AS51580 | — |
| 80.66.208.0/20 | AS51580 | — |
| 81.173.100.0/22 | AS51580 | — |
| 81.173.100.0/24 | AS51580 | — |
| 89.105.76.0/22 | AS51580 | — |
| 89.105.76.0/23 | AS51580 | — |
| 89.105.78.0/23 | AS51580 | — |
| 91.220.83.0/24 | AS51580 | — |
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.
AS51580 is an autonomous system number used to identify an independently operated network. The current page associates it with TIMENET-AS TIMENET SPA 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 AS51580. 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 AS51580, 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.