Country
—
ASN LANDING PAGE
MILECOM-AS - JSC "ER-Telecom Holding"
Last updated · Apr 4, 2026
Country
—
Total prefixes
6
IPv4 prefixes
5
IPv6 prefixes
1
MILECOM-AS - JSC "ER-Telecom Holding" currently shows 6 prefixes and 80 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.
MILECOM-AS - JSC "ER-Telecom Holding" 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.
AS203493
AS203493
—
AS31257
AS31257
—
AS42385
AS42385
—
AS39785
AS39785
—
AS61031
AS61031
—
AS33991
AS33991
—
AS39927
AS39927
—
AS47909
AS47909
—
AS211379
AS211379
—
AS60625
AS60625
—
AS48327
AS48327
—
AS31695
AS31695
—
AS52175
AS52175
—
AS208573
AS208573
—
AS56451
AS56451
—
AS47530
AS47530
—
AS57277
AS57277
—
AS50029
AS50029
—
AS57812
AS57812
—
AS12418
AS12418
—
AS21030
AS21030
—
AS49814
AS49814
—
AS56776
AS56776
—
AS61976
AS61976
—
AS51764
AS51764
—
AS29547
AS29547
—
AS47370
AS47370
—
AS201786
AS201786
—
AS209592
AS209592
—
AS33892
AS33892
—
AS42773
AS42773
—
AS34573
AS34573
—
AS50427
AS50427
—
AS60388
AS60388
—
AS42139
AS42139
—
AS51612
AS51612
—
AS48507
AS48507
—
AS42574
AS42574
—
AS56707
AS56707
—
AS205711
AS205711
—
AS1299
AS1299
—
AS9049
AS9049
—
AS28917
AS28917
—
AS9002
AS9002
—
AS13094
AS13094
—
AS35598
AS35598
—
AS34549
AS34549
—
AS6939
AS6939
—
AS3214
AS3214
—
AS8298
AS8298
—
AS5405
AS5405
—
AS34927
AS34927
—
AS34177
AS34177
—
AS51873
AS51873
—
AS8758
AS8758
—
AS29691
AS29691
—
AS25160
AS25160
—
AS35625
AS35625
—
AS48362
AS48362
—
AS264479
AS264479
—
AS34019
AS34019
—
AS6057
AS6057
—
AS35360
AS35360
—
AS21412
AS21412
—
AS37497
AS37497
—
AS559
AS559
—
AS24482
AS24482
—
AS29075
AS29075
—
AS58057
AS58057
—
AS206356
AS206356
—
AS553
AS553
—
AS25220
AS25220
—
AS271253
AS271253
—
AS18106
AS18106
—
AS210937
AS210937
—
AS29140
AS29140
—
AS47147
AS47147
—
AS48919
AS48919
—
AS199938
AS199938
—
AS39351
AS39351
—
| Prefix | Name | Country |
|---|---|---|
| 185.214.184.0/22 | AS48858 | — |
| 2a0b:9fc0::/48 | AS48858 | — |
| 62.78.80.0/20 | AS48858 | — |
| 91.235.92.0/22 | AS48858 | — |
| 91.235.92.0/24 | AS48858 | — |
| 91.235.94.0/24 | AS48858 | — |
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.
AS48858 is an autonomous system number used to identify an independently operated network. The current page associates it with MILECOM-AS - JSC "ER-Telecom Holding" 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 AS48858. 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 AS48858, 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.