Country
—
ASN LANDING PAGE
AS400342
EDGENAT-CLOUD - EDGENAT CLOUD
Last updated · Jul 20, 2026
Total prefixes
40
IPv4 prefixes
9
IPv6 prefixes
31
ASN summary
How to read the scale of AS400342
EDGENAT-CLOUD - EDGENAT CLOUD currently reports 40 prefixes and 4 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?
EDGENAT-CLOUD - EDGENAT CLOUD 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 AS400342 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
AS400342 ASN lookupAS400342 BGPAS400342 peersAS400342 prefixesAS400342 upstreamsEDGENAT-CLOUD - EDGENAT CLOUD ASN
Upstreams
Detailed data for this ASN is not available right now.
Downstreams
Detailed data for this ASN is not available right now.
Peers
Prefix inventory
| Prefix | Name | Country |
|---|---|---|
| 103.135.44.0/24 | AS400342 | — |
| 103.145.106.0/24 | AS400342 | — |
| 112.196.222.0/24 | AS400342 | — |
| 151.243.95.0/24 | AS400342 | — |
| 155.117.148.0/24 | AS400342 | — |
| 189.24.98.0/24 | AS400342 | — |
| 23.177.136.0/24 | AS400342 | — |
| 23.178.184.0/24 | AS400342 | — |
| 2402:1da0:ff00::/40 | AS400342 | — |
| 2a0c:6984:8000::/33 | AS400342 | — |
| 2a0c:6984::/33 | AS400342 | — |
| 2a0c:6985:8000::/33 | AS400342 | — |
| 2a0c:6985::/33 | AS400342 | — |
| 2a0c:6986:8000::/33 | AS400342 | — |
| 2a0c:6986::/33 | AS400342 | — |
| 2a0c:6987:8000::/33 | AS400342 | — |
| 2a0c:6987::/33 | AS400342 | — |
| 2a0d:b147:8000::/33 | AS400342 | — |
| 2a0d:b147::/33 | AS400342 | — |
| 2a11:c943:8000::/33 | AS400342 | — |
| 2a11:c943::/33 | AS400342 | — |
| 2a12:5f41:8000::/33 | AS400342 | — |
| 2a12:5f41::/33 | AS400342 | — |
| 2a12:ec4:8000::/33 | AS400342 | — |
| 2a12:ec4::/33 | AS400342 | — |
| 2a12:ec5:8000::/33 | AS400342 | — |
| 2a12:ec5::/33 | AS400342 | — |
| 2a12:ec6:8000::/33 | AS400342 | — |
| 2a12:ec6::/33 | AS400342 | — |
| 2a12:ec7:8000::/33 | AS400342 | — |
| 2a12:ec7::/33 | AS400342 | — |
| 2a14:4604:8000::/33 | AS400342 | — |
| 2a14:4604::/33 | AS400342 | — |
| 2a14:4605:8000::/33 | AS400342 | — |
| 2a14:4605::/33 | AS400342 | — |
| 2a14:4606:8000::/33 | AS400342 | — |
| 2a14:4606::/33 | AS400342 | — |
| 2a14:4607:8000::/33 | AS400342 | — |
| 2a14:4607::/33 | AS400342 | — |
| 45.135.161.0/24 | AS400342 | — |
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 AS400342 represent?
AS400342 is an autonomous system number. The current source associates it with EDGENAT-CLOUD - EDGENAT CLOUD 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 AS400342 page?
They help explain the scale, interconnection depth, and route structure of AS400342. 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 AS400342?
Open a concrete IP page to check how the address maps into AS400342, then compare the prefix, source labels, and query time. Verify operator or service claims with the relevant registry or network operator.
Related topics
Public DNS vs CDN and Anycast Guide
Explain the role differences in Public DNS vs CDN and Anycast and show exactly how far public IP, ASN, and BGP evidence can support the comparison.
CDN, Anycast, and Edge Network Guide
Explain why CDN and Anycast addresses can receive different Geo labels and use ASN plus BGP prefixes to interpret edge networks.
IP Geolocation Accuracy and Mismatch Guide
Explain why IP Geo databases can disagree on a city or country and how ASN, BGP prefix, source, and query time frame the estimate.
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.