Country
—
ASN LANDING PAGE
SYNLINQ - Oliver Horscht is trading as "SYNLINQ"
Last updated · Apr 4, 2026
Country
—
Total prefixes
108
IPv4 prefixes
93
IPv6 prefixes
15
SYNLINQ - Oliver Horscht is trading as "SYNLINQ" currently shows 108 prefixes and 48 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.
SYNLINQ - Oliver Horscht is trading as "SYNLINQ" 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.
AS174
AS174
—
AS60068
AS60068
—
AS33891
AS33891
—
AS2914
AS2914
—
AS3257
AS3257
—
AS6453
AS6453
—
AS6939
AS6939
—
AS20764
AS20764
—
AS50629
AS50629
—
AS34927
AS34927
—
AS49434
AS49434
—
AS205112
AS205112
—
AS9002
AS9002
—
AS28917
AS28917
—
AS29632
AS29632
—
AS35280
AS35280
—
AS199524
AS199524
—
AS286
AS286
—
AS6204
AS6204
—
AS209823
AS209823
—
AS29691
AS29691
—
AS30781
AS30781
—
AS34019
AS34019
—
AS48362
AS48362
—
AS3214
AS3214
—
AS5405
AS5405
—
AS8298
AS8298
—
AS34549
AS34549
—
AS39351
AS39351
—
AS8218
AS8218
—
AS559
AS559
—
AS1764
AS1764
—
AS1828
AS1828
—
AS5713
AS5713
—
AS6424
AS6424
—
AS8529
AS8529
—
AS8758
AS8758
—
AS12779
AS12779
—
AS14840
AS14840
—
AS17639
AS17639
—
| Prefix | Name | Country |
|---|---|---|
| 103.252.88.0/22 | AS44486 | — |
| 109.122.10.0/24 | AS44486 | — |
| 109.122.27.0/24 | AS44486 | — |
| 109.71.253.0/24 | AS44486 | — |
| 151.244.232.0/24 | AS44486 | — |
| 154.43.52.0/22 | AS44486 | — |
| 154.47.144.0/22 | AS44486 | — |
| 176.100.32.0/24 | AS44486 | — |
| 176.100.33.0/24 | AS44486 | — |
| 176.100.34.0/24 | AS44486 | — |
| 176.100.35.0/24 | AS44486 | — |
| 176.100.38.0/24 | AS44486 | — |
| 176.116.18.0/24 | AS44486 | — |
| 176.118.193.0/24 | AS44486 | — |
| 185.115.205.0/24 | AS44486 | — |
| 185.132.55.0/24 | AS44486 | — |
| 185.14.95.0/24 | AS44486 | — |
| 185.229.248.0/24 | AS44486 | — |
| 185.245.61.0/24 | AS44486 | — |
| 185.53.249.0/24 | AS44486 | — |
| 192.35.206.0/24 | AS44486 | — |
| 193.105.200.0/24 | AS44486 | — |
| 193.33.167.0/24 | AS44486 | — |
| 198.135.220.0/24 | AS44486 | — |
| 204.11.1.0/24 | AS44486 | — |
| 212.104.211.0/24 | AS44486 | — |
| 212.11.93.0/24 | AS44486 | — |
| 212.87.214.0/23 | AS44486 | — |
| 2a00:ccc1:100::/40 | AS44486 | — |
| 2a04:e8c0:19::/48 | AS44486 | — |
| 2a04:e8c0::/29 | AS44486 | — |
| 2a09:71c0::/29 | AS44486 | — |
| 2a0c:75c0:3::/48 | AS44486 | — |
| 2a0c:75c0::/29 | AS44486 | — |
| 2a0c:75c0::/48 | AS44486 | — |
| 2a0c:a300::/29 | AS44486 | — |
| 2a0e:66c0::/29 | AS44486 | — |
| 2a0e:6a80::/29 | AS44486 | — |
| 2a10:b680::/32 | AS44486 | — |
| 2a12:bec0:df0::/44 | AS44486 | — |
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.
AS44486 is an autonomous system number used to identify an independently operated network. The current page associates it with SYNLINQ - Oliver Horscht is trading as "SYNLINQ" 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 AS44486. 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 AS44486, 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.