Country
—
ASN LANDING PAGE
TANGO-PROXIMUS_NXT - Proximus Luxembourg S.A.
Last updated · Apr 4, 2026
Country
—
Total prefixes
33
IPv4 prefixes
24
IPv6 prefixes
9
TANGO-PROXIMUS_NXT - Proximus Luxembourg S.A. currently shows 33 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.
TANGO-PROXIMUS_NXT - Proximus Luxembourg S.A. 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.
AS6774
AS6774
—
AS174
AS174
—
AS1299
AS1299
—
AS3356
AS3356
—
AS2914
AS2914
—
AS6939
AS6939
—
AS6453
AS6453
—
AS13030
AS13030
—
AS34549
AS34549
—
AS6461
AS6461
—
AS50304
AS50304
—
AS5405
AS5405
—
AS6057
AS6057
—
AS8298
AS8298
—
AS34177
AS34177
—
AS24961
AS24961
—
AS20764
AS20764
—
AS4637
AS4637
—
AS29691
AS29691
—
AS8758
AS8758
—
AS12779
AS12779
—
AS14907
AS14907
—
AS39351
AS39351
—
AS41327
AS41327
—
AS34019
AS34019
—
AS60068
AS60068
—
AS48362
AS48362
—
AS50673
AS50673
—
AS34927
AS34927
—
AS51185
AS51185
—
AS8426
AS8426
—
AS24482
AS24482
—
AS25160
AS25160
—
AS50763
AS50763
—
AS199524
AS199524
—
AS680
AS680
—
AS3399
AS3399
—
AS14840
AS14840
—
AS35360
AS35360
—
AS45049
AS45049
—
| Prefix | Name | Country |
|---|---|---|
| 185.3.44.0/22 | AS56665 | — |
| 185.40.60.0/22 | AS56665 | — |
| 212.66.64.0/19 | AS56665 | — |
| 212.66.67.0/24 | AS56665 | — |
| 212.66.76.0/24 | AS56665 | — |
| 2a00:4180:1000::/36 | AS56665 | — |
| 2a00:4180:1::/48 | AS56665 | — |
| 2a00:4180:2::/48 | AS56665 | — |
| 2a00:4180:3::/48 | AS56665 | — |
| 2a04:81c0::/29 | AS56665 | — |
| 2a04:81c4:1000::/40 | AS56665 | — |
| 2a04:81c4:10::/44 | AS56665 | — |
| 2a04:81c4:1100::/40 | AS56665 | — |
| 2a04:81c4::/44 | AS56665 | — |
| 31.204.88.0/24 | AS56665 | — |
| 31.204.90.0/23 | AS56665 | — |
| 31.204.92.0/22 | AS56665 | — |
| 94.252.0.0/17 | AS56665 | — |
| 94.252.0.0/21 | AS56665 | — |
| 94.252.112.0/21 | AS56665 | — |
| 94.252.120.0/21 | AS56665 | — |
| 94.252.16.0/21 | AS56665 | — |
| 94.252.24.0/21 | AS56665 | — |
| 94.252.32.0/21 | AS56665 | — |
| 94.252.40.0/21 | AS56665 | — |
| 94.252.48.0/21 | AS56665 | — |
| 94.252.56.0/21 | AS56665 | — |
| 94.252.64.0/21 | AS56665 | — |
| 94.252.72.0/21 | AS56665 | — |
| 94.252.8.0/21 | AS56665 | — |
| 94.252.80.0/21 | AS56665 | — |
| 94.252.88.0/21 | AS56665 | — |
| 94.252.96.0/20 | AS56665 | — |
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.
AS56665 is an autonomous system number used to identify an independently operated network. The current page associates it with TANGO-PROXIMUS_NXT - Proximus Luxembourg S.A. 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 AS56665. 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 AS56665, 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.