Country
—
ASN LANDING PAGE
AS263152 - MIGO TELECOM
Last updated · Jul 20, 2026
Country
—
Total prefixes
120
IPv4 prefixes
43
IPv6 prefixes
77
AS263152 - MIGO TELECOM currently reports 120 prefixes and 47 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.
AS263152 - MIGO TELECOM 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.
AS6939
AS6939
—
AS174
AS174
—
AS53013
AS53013
—
AS268624
AS268624
—
AS264409
AS264409
—
AS9498
AS9498
—
AS701
AS701
—
AS20764
AS20764
—
AS137409
AS137409
—
AS13335
AS13335
—
AS5405
AS5405
—
AS7195
AS7195
—
AS58453
AS58453
—
AS32787
AS32787
—
AS16735
AS16735
—
AS14840
AS14840
—
AS64049
AS64049
—
AS57304
AS57304
—
AS3303
AS3303
—
AS52468
AS52468
—
AS53062
AS53062
—
AS52320
AS52320
—
AS7049
AS7049
—
AS61568
AS61568
—
AS31500
AS31500
—
AS12552
AS12552
—
AS4230
AS4230
—
AS262287
AS262287
—
AS37468
AS37468
—
AS29119
AS29119
—
AS35280
AS35280
—
AS37100
AS37100
—
AS15830
AS15830
—
AS28283
AS28283
—
AS28917
AS28917
—
AS23764
AS23764
—
AS13786
AS13786
—
AS267613
AS267613
—
AS24482
AS24482
—
AS16276
AS16276
—
| Prefix | Name | Country |
|---|---|---|
| 138.59.32.0/22 | AS263152 | — |
| 138.59.32.0/23 | AS263152 | — |
| 138.59.32.0/24 | AS263152 | — |
| 138.59.33.0/24 | AS263152 | — |
| 138.59.34.0/23 | AS263152 | — |
| 138.59.34.0/24 | AS263152 | — |
| 138.59.35.0/24 | AS263152 | — |
| 143.202.100.0/22 | AS263152 | — |
| 143.202.100.0/23 | AS263152 | — |
| 143.202.100.0/24 | AS263152 | — |
| 143.202.101.0/24 | AS263152 | — |
| 143.202.102.0/23 | AS263152 | — |
| 143.202.102.0/24 | AS263152 | — |
| 143.202.103.0/24 | AS263152 | — |
| 170.233.64.0/22 | AS263152 | — |
| 170.233.64.0/23 | AS263152 | — |
| 170.233.64.0/24 | AS263152 | — |
| 170.233.65.0/24 | AS263152 | — |
| 170.233.66.0/24 | AS263152 | — |
| 170.233.67.0/24 | AS263152 | — |
| 170.245.108.0/22 | AS263152 | — |
| 170.245.108.0/23 | AS263152 | — |
| 170.245.108.0/24 | AS263152 | — |
| 170.245.109.0/24 | AS263152 | — |
| 170.245.110.0/23 | AS263152 | — |
| 170.245.110.0/24 | AS263152 | — |
| 170.245.111.0/24 | AS263152 | — |
| 177.92.248.0/21 | AS263152 | — |
| 177.92.248.0/22 | AS263152 | — |
| 177.92.248.0/23 | AS263152 | — |
| 177.92.248.0/24 | AS263152 | — |
| 177.92.249.0/24 | AS263152 | — |
| 177.92.250.0/23 | AS263152 | — |
| 177.92.250.0/24 | AS263152 | — |
| 177.92.251.0/24 | AS263152 | — |
| 177.92.252.0/22 | AS263152 | — |
| 177.92.252.0/23 | AS263152 | — |
| 177.92.252.0/24 | AS263152 | — |
| 177.92.253.0/24 | AS263152 | — |
| 177.92.254.0/23 | AS263152 | — |
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.
AS263152 is an autonomous system number. The current source associates it with AS263152 - MIGO TELECOM 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 AS263152. 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 AS263152, 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.