Country
—
ASN LANDING PAGE
AS25513
ASN-MGTS-USPD PJSC Moscow city telephone network
Last updated · Jul 20, 2026
Total prefixes
56
IPv4 prefixes
0
IPv6 prefixes
0
ASN summary
How to read the scale of AS25513
ASN-MGTS-USPD PJSC Moscow city telephone network currently reports 56 prefixes and 22 upstream, downstream, or peer relationships. These counts describe the current dataset; they do not by themselves prove network quality, reach, or service use.
What can an ASN page answer?
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.
How should you read the organization and region fields?
ASN-MGTS-USPD PJSC Moscow city telephone network 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.
How should you verify the AS25513 result?
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.
How to verify this ASN result
AS25513 ASN lookupAS25513 BGPAS25513 peersAS25513 prefixesAS25513 upstreamsASN-MGTS-USPD PJSC Moscow city telephone network ASN
Upstreams
Detailed data for this ASN is not available right now.
Downstreams
AS29285
AS29285
—
AS34500
AS34500
—
AS58071
AS58071
—
AS199502
AS199502
—
AS5548
AS5548
—
AS39415
AS39415
—
AS44232
AS44232
—
AS58072
AS58072
—
AS199093
AS199093
—
AS219445
AS219445
—
AS56537
AS56537
—
AS210989
AS210989
—
AS211532
AS211532
—
AS198712
AS198712
—
AS56483
AS56483
—
AS210239
AS210239
—
AS211247
AS211247
—
AS51893
AS51893
—
AS8901
AS8901
—
AS43993
AS43993
—
Peers
Prefix inventory
| Prefix | Name | Country |
|---|---|---|
| 109.252.0.0/16 | AS25513 | — |
| 128.0.128.0/20 | AS25513 | — |
| 158.255.128.0/18 | AS25513 | — |
| 178.170.246.0/24 | AS25513 | — |
| 185.2.124.0/23 | AS25513 | — |
| 194.135.108.0/22 | AS25513 | — |
| 194.135.112.0/22 | AS25513 | — |
| 194.135.120.0/22 | AS25513 | — |
| 194.135.208.0/20 | AS25513 | — |
| 194.135.224.0/20 | AS25513 | — |
| 194.135.240.0/21 | AS25513 | — |
| 194.135.4.0/22 | AS25513 | — |
| 194.135.40.0/22 | AS25513 | — |
| 194.135.52.0/22 | AS25513 | — |
| 194.135.60.0/22 | AS25513 | — |
| 194.135.64.0/21 | AS25513 | — |
| 194.135.72.0/22 | AS25513 | — |
| 194.135.8.0/21 | AS25513 | — |
| 194.135.96.0/22 | AS25513 | — |
| 194.165.20.0/23 | AS25513 | — |
| 194.226.19.0/24 | AS25513 | — |
| 195.9.0.0/16 | AS25513 | — |
| 217.112.16.0/20 | AS25513 | — |
| 217.26.0.0/20 | AS25513 | — |
| 2a00:1370::/32 | AS25513 | — |
| 2a03:6505:6000::/48 | AS25513 | — |
| 2a03:6505:6001::/48 | AS25513 | — |
| 2a03:af60::/32 | AS25513 | — |
| 37.190.0.0/17 | AS25513 | — |
| 37.230.157.0/24 | AS25513 | — |
| 46.138.0.0/16 | AS25513 | — |
| 46.175.200.0/24 | AS25513 | — |
| 46.175.201.0/24 | AS25513 | — |
| 46.175.202.0/23 | AS25513 | — |
| 46.175.204.0/23 | AS25513 | — |
| 46.175.206.0/24 | AS25513 | — |
| 46.175.207.0/24 | AS25513 | — |
| 62.112.96.0/19 | AS25513 | — |
| 79.139.128.0/17 | AS25513 | — |
| 79.139.128.0/22 | AS25513 | — |
Related ASN pages
AS15169 · Google
Review Google network organization fields, prefixes, peers, upstreams, and downstreams.
AS13335 · Cloudflare
Review Cloudflare network organization fields, prefixes, peers, upstreams, and downstreams.
AS8075 · Microsoft
Review Microsoft network organization fields, prefixes, peers, upstreams, and downstreams.
AS16509 · Amazon
Review Amazon network organization fields, prefixes, peers, upstreams, and downstreams.
Related lookups and next steps
Frequently asked questions about this ASN page
What does AS25513 represent?
AS25513 is an autonomous system number. The current source associates it with ASN-MGTS-USPD PJSC Moscow city telephone network and the region field an unknown region; those values add network context but do not prove a specific service, physical location, or quality level.
What are peers, upstreams, and prefixes useful for on the AS25513 page?
They help explain the scale, interconnection depth, and route structure of AS25513. Richer peering and upstream data often indicate broader network reach, but they should still be interpreted together with prefixes and related IP landing pages.
What should you do after reviewing AS25513?
Open a concrete IP page to check how the address maps into AS25513, then compare the prefix, source labels, and query time. Verify operator or service claims with the relevant registry or network operator.
Related topics
BGP and ASN Basics Guide
Use real IP and ASN pages to understand ASNs, BGP prefixes, peers, upstreams, and downstreams, including the limits of each snapshot.
Routing Troubleshooting and Network Analysis
Build troubleshooting context from an IP, BGP prefix, ASN, and public network relationships without treating static route data as a packet path.
Cloud Network and ASN Comparison
Compare representative cloud and edge networks by ASN, announced prefixes, peers, upstreams, and downstreams without inferring a specific host or customer workload.