Country
—
ASN LANDING PAGE
FINK-TELECOM-SERVICES - Andreas Fink trading as Fink Telecom Services GmbH
Last updated · Apr 4, 2026
Country
—
Total prefixes
22
IPv4 prefixes
16
IPv6 prefixes
6
FINK-TELECOM-SERVICES - Andreas Fink trading as Fink Telecom Services GmbH currently shows 22 prefixes and 50 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.
FINK-TELECOM-SERVICES - Andreas Fink trading as Fink Telecom Services GmbH 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.
AS6939
AS6939
—
AS13030
AS13030
—
AS6204
AS6204
—
AS210538
AS210538
—
AS5405
AS5405
—
AS8218
AS8218
—
AS1257
AS1257
—
AS9002
AS9002
—
AS34019
AS34019
—
AS24482
AS24482
—
AS24961
AS24961
—
AS20764
AS20764
—
AS35280
AS35280
—
AS33891
AS33891
—
AS56430
AS56430
—
AS6057
AS6057
—
AS12310
AS12310
—
AS25091
AS25091
—
AS29075
AS29075
—
AS34177
AS34177
—
AS39351
AS39351
—
AS209823
AS209823
—
AS1764
AS1764
—
AS8283
AS8283
—
AS14840
AS14840
—
AS15830
AS15830
—
AS35360
AS35360
—
AS47147
AS47147
—
AS49434
AS49434
—
AS56987
AS56987
—
AS58299
AS58299
—
AS62167
AS62167
—
AS1828
AS1828
—
AS6758
AS6758
—
AS8298
AS8298
—
AS12779
AS12779
—
AS15547
AS15547
—
AS16347
AS16347
—
AS25160
AS25160
—
AS25220
AS25220
—
| Prefix | Name | Country |
|---|---|---|
| 2001:4b28::/29 | AS6775 | — |
| 2001:4b28::/32 | AS6775 | — |
| 2a01:528::/29 | AS6775 | — |
| 2a01:528::/32 | AS6775 | — |
| 2a01:528:e::/48 | AS6775 | — |
| 2a12:f380::/29 | AS6775 | — |
| 45.143.188.0/22 | AS6775 | — |
| 79.134.224.0/19 | AS6775 | — |
| 79.134.235.0/24 | AS6775 | — |
| 79.134.246.0/24 | AS6775 | — |
| 79.134.247.0/24 | AS6775 | — |
| 79.134.250.0/23 | AS6775 | — |
| 79.134.250.0/24 | AS6775 | — |
| 79.134.251.0/24 | AS6775 | — |
| 79.134.254.0/23 | AS6775 | — |
| 79.134.254.0/24 | AS6775 | — |
| 79.134.255.0/24 | AS6775 | — |
| 85.209.172.0/22 | AS6775 | — |
| 85.209.172.0/24 | AS6775 | — |
| 85.209.173.0/24 | AS6775 | — |
| 85.209.174.0/24 | AS6775 | — |
| 85.209.175.0/24 | AS6775 | — |
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.
AS6775 is an autonomous system number used to identify an independently operated network. The current page associates it with FINK-TELECOM-SERVICES - Andreas Fink trading as Fink Telecom Services GmbH 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 AS6775. 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 AS6775, 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.