Country
—
ASN LANDING PAGE
AVSISP ANDREW KRISTULI
Last updated · Apr 10, 2026
Country
—
Total prefixes
32
IPv4 prefixes
4
IPv6 prefixes
28
AVSISP ANDREW KRISTULI currently shows 32 prefixes and 39 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.
AVSISP ANDREW KRISTULI 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.
AS204044
AS204044
—
AS6939
AS6939
—
AS64289
AS64289
—
AS6204
AS6204
—
AS213900
AS213900
—
AS205941
AS205941
—
AS34019
AS34019
—
AS5405
AS5405
—
AS25091
AS25091
—
AS1103
AS1103
—
AS20764
AS20764
—
AS8298
AS8298
—
AS39351
AS39351
—
AS3214
AS3214
—
AS50629
AS50629
—
AS24482
AS24482
—
AS212635
AS212635
—
AS6424
AS6424
—
AS12859
AS12859
—
AS39122
AS39122
—
AS49544
AS49544
—
AS60326
AS60326
—
AS50869
AS50869
—
AS209823
AS209823
—
AS3399
AS3399
—
AS137409
AS137409
—
AS34927
AS34927
—
AS35360
AS35360
—
AS37721
AS37721
—
AS56584
AS56584
—
| Prefix | Name | Country |
|---|---|---|
| 195.144.24.0/24 | AS210464 | — |
| 208.70.218.0/24 | AS210464 | — |
| 2602:f704:c00::/38 | AS210464 | — |
| 2a0a:79c7:f200::/40 | AS210464 | — |
| 2a0a:79c7:f300::/40 | AS210464 | — |
| 2a0a:79c7:f400::/40 | AS210464 | — |
| 2a0a:79c7:f500::/40 | AS210464 | — |
| 2a0a:79c7:f600::/40 | AS210464 | — |
| 2a0a:79c7:f700::/40 | AS210464 | — |
| 2a0a:79c7:f800::/40 | AS210464 | — |
| 2a0a:79c7:fa00::/40 | AS210464 | — |
| 2a0a:79c7:fb00::/40 | AS210464 | — |
| 2a0a:79c7:fc00::/40 | AS210464 | — |
| 2a0a:79c7:ff00::/40 | AS210464 | — |
| 2a0f:6284:f::/48 | AS210464 | — |
| 2a14:7580:c000::/40 | AS210464 | — |
| 2a14:7580:c300::/40 | AS210464 | — |
| 2a14:7580:ff99::/48 | AS210464 | — |
| 2a14:7583:200::/39 | AS210464 | — |
| 2a14:7583:5b00::/40 | AS210464 | — |
| 2a14:7583:700::/40 | AS210464 | — |
| 2a14:7583:800::/40 | AS210464 | — |
| 2a14:7583:900::/40 | AS210464 | — |
| 2a14:7583::/39 | AS210464 | — |
| 2a14:7583:a00::/40 | AS210464 | — |
| 2a14:7583:b00::/40 | AS210464 | — |
| 2a14:7583:c00::/40 | AS210464 | — |
| 2a14:7583:d00::/40 | AS210464 | — |
| 2a14:7583:e00::/40 | AS210464 | — |
| 2a14:7583:f00::/40 | AS210464 | — |
| 31.57.56.0/24 | AS210464 | — |
| 85.155.228.0/24 | AS210464 | — |
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.
AS210464 is an autonomous system number used to identify an independently operated network. The current page associates it with AVSISP ANDREW KRISTULI 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 AS210464. 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 AS210464, 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.