Country
—
ASN LANDING PAGE
MTNSAT-ASN-02 - MTNSAT Holdings LLC
Last updated · Jul 20, 2026
Country
—
Total prefixes
59
IPv4 prefixes
50
IPv6 prefixes
9
MTNSAT-ASN-02 - MTNSAT Holdings LLC currently reports 59 prefixes and 40 upstream, downstream, or peer relationships. These counts describe the current dataset; they do not by themselves prove network quality, reach, or service use.
An ASN page shows the public organization label, country or region, BGP prefixes, and available peer and upstream relationships. It adds network context but cannot confirm a website host, physical facility, security status, or service quality.
MTNSAT-ASN-02 - MTNSAT Holdings LLC is currently associated with an unknown region. These values come from public network sources and are useful lookup clues; an organization label, registration region, and actual service location may differ.
The page shows ASN data returned by the current upstream query; interpret it with the update time. Open representative IP pages from the same network and compare prefixes, source labels, and query times. Verify operator or service claims with the relevant registry or network operator.
Detailed data for this ASN is not available right now.
Detailed data for this ASN is not available right now.
AS52468
AS52468
—
AS400110
AS400110
—
AS1299
AS1299
—
AS6939
AS6939
—
AS3356
AS3356
—
AS3257
AS3257
—
AS54309
AS54309
—
AS174
AS174
—
AS37100
AS37100
—
AS15808
AS15808
—
AS5405
AS5405
—
AS8218
AS8218
—
AS29632
AS29632
—
AS24961
AS24961
—
AS137409
AS137409
—
AS286
AS286
—
AS4455
AS4455
—
AS5392
AS5392
—
AS5394
AS5394
—
AS6204
AS6204
—
AS8529
AS8529
—
AS8660
AS8660
—
AS9009
AS9009
—
AS12637
AS12637
—
AS12779
AS12779
—
AS13237
AS13237
—
AS15605
AS15605
—
AS24482
AS24482
—
AS28716
AS28716
—
AS31543
AS31543
—
AS49544
AS49544
—
AS49605
AS49605
—
AS49709
AS49709
—
AS50877
AS50877
—
AS51185
AS51185
—
AS53013
AS53013
—
AS57111
AS57111
—
AS59919
AS59919
—
AS60171
AS60171
—
AS198150
AS198150
—
| Prefix | Name | Country |
|---|---|---|
| 158.247.12.0/22 | AS32806 | — |
| 176.52.170.0/24 | AS32806 | — |
| 176.52.171.0/24 | AS32806 | — |
| 185.38.32.0/22 | AS32806 | — |
| 190.103.128.0/21 | AS32806 | — |
| 190.103.136.0/22 | AS32806 | — |
| 190.103.140.0/23 | AS32806 | — |
| 190.103.142.0/24 | AS32806 | — |
| 192.187.0.0/24 | AS32806 | — |
| 192.187.1.0/24 | AS32806 | — |
| 192.187.2.0/24 | AS32806 | — |
| 192.187.3.0/24 | AS32806 | — |
| 200.12.216.0/21 | AS32806 | — |
| 204.179.65.0/24 | AS32806 | — |
| 208.114.116.0/24 | AS32806 | — |
| 208.114.117.0/24 | AS32806 | — |
| 208.114.118.0/24 | AS32806 | — |
| 208.114.119.0/24 | AS32806 | — |
| 208.114.120.0/24 | AS32806 | — |
| 208.114.121.0/24 | AS32806 | — |
| 208.114.96.0/19 | AS32806 | — |
| 212.21.32.0/19 | AS32806 | — |
| 216.130.32.0/20 | AS32806 | — |
| 216.130.32.0/24 | AS32806 | — |
| 216.130.36.0/24 | AS32806 | — |
| 216.130.43.0/24 | AS32806 | — |
| 216.130.44.0/23 | AS32806 | — |
| 216.130.47.0/24 | AS32806 | — |
| 216.7.144.0/20 | AS32806 | — |
| 216.7.146.0/24 | AS32806 | — |
| 216.7.148.0/24 | AS32806 | — |
| 216.7.159.0/24 | AS32806 | — |
| 2604:9900:1::/48 | AS32806 | — |
| 2604:9900:4::/48 | AS32806 | — |
| 2604:9900:6::/48 | AS32806 | — |
| 2604:9900:7::/48 | AS32806 | — |
| 2604:9900:8::/48 | AS32806 | — |
| 2604:9900:9::/48 | AS32806 | — |
| 2604:9900::/48 | AS32806 | — |
| 2604:9900:a::/48 | AS32806 | — |
Review Google network organization fields, prefixes, peers, upstreams, and downstreams.
Review Cloudflare network organization fields, prefixes, peers, upstreams, and downstreams.
Review Microsoft network organization fields, prefixes, peers, upstreams, and downstreams.
Review Amazon network organization fields, prefixes, peers, upstreams, and downstreams.
AS32806 is an autonomous system number. The current source associates it with MTNSAT-ASN-02 - MTNSAT Holdings LLC and the region field an unknown region; those values add network context but do not prove a specific service, physical location, or quality level.
They help explain the scale, interconnection depth, and route structure of AS32806. Richer peering and upstream data often indicate broader network reach, but they should still be interpreted together with prefixes and related IP landing pages.
Open a concrete IP page to check how the address maps into AS32806, then compare the prefix, source labels, and query time. Verify operator or service claims with the relevant registry or network operator.
Use real IP and ASN pages to understand ASNs, BGP prefixes, peers, upstreams, and downstreams, including the limits of each snapshot.
Build troubleshooting context from an IP, BGP prefix, ASN, and public network relationships without treating static route data as a packet path.
Compare representative cloud and edge networks by ASN, announced prefixes, peers, upstreams, and downstreams without inferring a specific host or customer workload.