Country
—
ASN LANDING PAGE
SERVLINK TELECOM LTDA - ME
Last updated · Apr 4, 2026
Country
—
Total prefixes
32
IPv4 prefixes
6
IPv6 prefixes
26
SERVLINK TELECOM LTDA - ME currently shows 32 prefixes and 44 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.
SERVLINK TELECOM LTDA - ME 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.
AS265462
AS265462
—
AS266379
AS266379
—
AS265447
AS265447
—
AS270954
AS270954
—
AS273417
AS273417
—
AS265486
AS265486
—
AS267666
AS267666
—
AS271441
AS271441
—
AS268585
AS268585
—
AS273717
AS273717
—
AS266635
AS266635
—
AS266376
AS266376
—
AS266505
AS266505
—
AS268711
AS268711
—
AS271766
AS271766
—
AS272542
AS272542
—
AS26615
AS26615
—
AS266229
AS266229
—
AS52924
AS52924
—
AS269330
AS269330
—
AS267160
AS267160
—
AS270427
AS270427
—
AS268809
AS268809
—
AS268705
AS268705
—
AS269411
AS269411
—
AS52766
AS52766
—
AS269704
AS269704
—
AS265935
AS265935
—
AS14840
AS14840
—
| Prefix | Name | Country |
|---|---|---|
| 170.84.84.0/22 | AS264996 | — |
| 170.84.84.0/23 | AS264996 | — |
| 170.84.86.0/23 | AS264996 | — |
| 2804:3124:10::/45 | AS264996 | — |
| 2804:3124:18::/45 | AS264996 | — |
| 2804:3124:4013::/48 | AS264996 | — |
| 2804:3124:4014::/48 | AS264996 | — |
| 2804:3124:4100::/40 | AS264996 | — |
| 2804:3124:4200::/40 | AS264996 | — |
| 2804:3124:4300::/40 | AS264996 | — |
| 2804:3124:5::/48 | AS264996 | — |
| 2804:3124:6::/48 | AS264996 | — |
| 2804:3124:8000::/33 | AS264996 | — |
| 2804:3124:8000::/34 | AS264996 | — |
| 2804:3124:800c::/48 | AS264996 | — |
| 2804:3124:800f::/48 | AS264996 | — |
| 2804:3124:8010::/48 | AS264996 | — |
| 2804:3124::/32 | AS264996 | — |
| 2804:3124::/33 | AS264996 | — |
| 2804:3124:c000::/34 | AS264996 | — |
| 2804:3124:c007::/48 | AS264996 | — |
| 2804:3124:c009::/48 | AS264996 | — |
| 2804:3124:c00a::/48 | AS264996 | — |
| 2804:3124:c00b::/48 | AS264996 | — |
| 2804:3124:c00c::/48 | AS264996 | — |
| 2804:3124:c00d::/48 | AS264996 | — |
| 2804:3124:c012::/48 | AS264996 | — |
| 2804:3124:c016::/48 | AS264996 | — |
| 2804:3124:c017::/48 | AS264996 | — |
| 45.179.128.0/22 | AS264996 | — |
| 45.179.128.0/23 | AS264996 | — |
| 45.179.130.0/23 | AS264996 | — |
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.
AS264996 is an autonomous system number used to identify an independently operated network. The current page associates it with SERVLINK TELECOM LTDA - ME 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 AS264996. 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 AS264996, 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.