Country
—
ASN LANDING PAGE
AS207301
JACKMX Roman Sartov
Last updated · Jul 20, 2026
Total prefixes
6
IPv4 prefixes
2
IPv6 prefixes
4
ASN summary
How to read the scale of AS207301
JACKMX Roman Sartov currently reports 6 prefixes and 23 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?
JACKMX Roman Sartov 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 AS207301 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
AS207301 ASN lookupAS207301 BGPAS207301 peersAS207301 prefixesAS207301 upstreamsJACKMX Roman Sartov ASN
Upstreams
Detailed data for this ASN is not available right now.
Downstreams
Detailed data for this ASN is not available right now.
Peers
AS30886
AS30886
—
AS8772
AS8772
—
AS211509
AS211509
—
AS48648
AS48648
—
AS44324
AS44324
—
AS199995
AS199995
—
AS6768
AS6768
—
AS50581
AS50581
—
AS49824
AS49824
—
AS3
AS3
—
AS112
AS112
—
AS25152
AS25152
—
AS29632
AS29632
—
AS43309
AS43309
—
AS48438
AS48438
—
AS48957
AS48957
—
AS56485
AS56485
—
AS202939
AS202939
—
AS204508
AS204508
—
AS207656
AS207656
—
AS210490
AS210490
—
AS214022
AS214022
—
AS215887
AS215887
—
Prefix inventory
| Prefix | Name | Country |
|---|---|---|
| 2a0c:b641:780::/44 | AS207301 | — |
| 2a0c:b641:780::/48 | AS207301 | — |
| 2a0c:b641:781::/48 | AS207301 | — |
| 2a0c:b641:782::/48 | AS207301 | — |
| 44.30.72.0/24 | AS207301 | — |
| 91.197.70.0/24 | AS207301 | — |
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 AS207301 represent?
AS207301 is an autonomous system number. The current source associates it with JACKMX Roman Sartov 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 AS207301 page?
They help explain the scale, interconnection depth, and route structure of AS207301. 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 AS207301?
Open a concrete IP page to check how the address maps into AS207301, 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.