Country
—
ASN LANDING PAGE
AS35773
ICONNECT-AS - iConnect Ltd.
Last updated · Apr 4, 2026
Total prefixes
6
IPv4 prefixes
5
IPv6 prefixes
1
ASN summary
How to read the scale of AS35773
ICONNECT-AS - iConnect Ltd. currently shows 6 prefixes and 41 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.
When is an ASN page most useful?
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.
How should you read the country, organization, and role of AS35773?
ICONNECT-AS - iConnect Ltd. 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.
What should you inspect next after the AS35773 page?
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.
Search intents this ASN page helps cover
AS35773 ASN lookupAS35773 BGPAS35773 peersAS35773 prefixesAS35773 upstreamsICONNECT-AS - iConnect Ltd. ASN
Upstreams
Detailed data for this ASN is not available right now.
Downstreams
Peers
AS57463
AS57463
—
AS12615
AS12615
—
AS61071
AS61071
—
AS59900
AS59900
—
AS6939
AS6939
—
AS29084
AS29084
—
AS34019
AS34019
—
AS34549
AS34549
—
AS14840
AS14840
—
AS25091
AS25091
—
AS50673
AS50673
—
AS58057
AS58057
—
AS206499
AS206499
—
AS3170
AS3170
—
AS3214
AS3214
—
AS8298
AS8298
—
AS9198
AS9198
—
AS20764
AS20764
—
AS24482
AS24482
—
AS34854
AS34854
—
AS34872
AS34872
—
AS35598
AS35598
—
AS37721
AS37721
—
AS39122
AS39122
—
AS39351
AS39351
—
AS49673
AS49673
—
AS52055
AS52055
—
AS62167
AS62167
—
AS199524
AS199524
—
AS200612
AS200612
—
AS212483
AS212483
—
AS212508
AS212508
—
AS5405
AS5405
—
AS8218
AS8218
—
AS8280
AS8280
—
AS9044
AS9044
—
AS13004
AS13004
—
AS15958
AS15958
—
AS24961
AS24961
—
AS39120
AS39120
—
Prefix inventory
| Prefix | Name | Country |
|---|---|---|
| 109.160.112.0/24 | AS35773 | — |
| 195.214.248.0/21 | AS35773 | — |
| 2a13:d880::/29 | AS35773 | — |
| 46.245.237.0/24 | AS35773 | — |
| 84.54.148.0/24 | AS35773 | — |
| 84.54.150.0/24 | AS35773 | — |
Related ASN pages
AS15169 · Google
A strong reference ASN for Google DNS, Google Cloud, and global network footprint analysis.
AS13335 · Cloudflare
Useful for analyzing CDN, Anycast, WAF, and large-scale edge network behavior.
AS8075 · Microsoft
Helpful when comparing Azure, enterprise backbone, and large-cloud routing patterns.
AS16509 · Amazon
A useful ASN landing page for understanding AWS and large cloud-network ownership.
Related lookups and next steps
WHOIS vs ASN Ownership Guide
Continue from this ASN into the differences between WHOIS ownership and ASN ownership.
Routing Troubleshooting and Network Analysis
Continue from this ASN into route troubleshooting and network analysis.
Cloud Network and ASN Comparison
Useful when you want to compare this ASN against larger cloud and edge networks.
WHOIS and IP Ownership Guide
Continue from the ASN page into WHOIS and ownership verification.
Frequently asked questions about this ASN page
What does AS35773 represent?
AS35773 is an autonomous system number used to identify an independently operated network. The current page associates it with ICONNECT-AS - iConnect Ltd. in an unknown region, which helps determine whether it behaves like a cloud provider, ISP, CDN, or enterprise backbone.
What are peers, upstreams, and prefixes useful for on the AS35773 page?
They help explain the scale, interconnection depth, and route structure of AS35773. 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 AS35773?
The best next step is usually to return to a concrete IP landing page to see how a specific address maps into AS35773, then continue into cloud, WHOIS, or routing topic pages to understand the network in a broader context.
Related topics
WHOIS vs ASN Ownership Guide
Understand why WHOIS ownership and ASN ownership can differ, and how to combine both when deciding who really owns or operates an IP.
WHOIS and IP Ownership Guide
Use WHOIS, ASN, prefixes, and organization data to determine who ultimately owns an IP, range, or resolved domain target.
BGP and ASN Basics Guide
Learn what ASN, BGP routes, prefixes, upstreams, downstreams, and peers mean, then explore real ASN pages.
Cloud Network and ASN Comparison
Compare large cloud and edge networks such as Google, Cloudflare, Microsoft, and Amazon through their ASN landing pages.