Country
—
ASN LANDING PAGE
BORUSANTELEKOM-AS Vodafone Net Iletisim Hizmetler AS
Last updated · Jul 20, 2026
Country
—
Total prefixes
356
IPv4 prefixes
352
IPv6 prefixes
4
BORUSANTELEKOM-AS Vodafone Net Iletisim Hizmetler AS currently reports 356 prefixes and 53 upstream, downstream, or peer relationships. These counts describe the current dataset; they do not by themselves prove network quality, reach, or service use.
An ASN page shows the public organization label, country or region, BGP prefixes, and available peer and upstream relationships. It adds network context but cannot confirm a website host, physical facility, security status, or service quality.
BORUSANTELEKOM-AS Vodafone Net Iletisim Hizmetler AS is currently associated with an unknown region. These values come from public network sources and are useful lookup clues; an organization label, registration region, and actual service location may differ.
The page shows ASN data returned by the current upstream query; interpret it with the update time. Open representative IP pages from the same network and compare prefixes, source labels, and query times. Verify operator or service claims with the relevant registry or network operator.
Detailed data for this ASN is not available right now.
AS44327
AS44327
—
AS8386
AS8386
—
AS20940
AS20940
—
AS44217
AS44217
—
AS15897
AS15897
—
AS47952
AS47952
—
AS214588
AS214588
—
AS214095
AS214095
—
AS136907
AS136907
—
AS12861
AS12861
—
AS47524
AS47524
—
AS12840
AS12840
—
AS213145
AS213145
—
AS58203
AS58203
—
AS208553
AS208553
—
AS212249
AS212249
—
AS43417
AS43417
—
AS209263
AS209263
—
AS209275
AS209275
—
AS13335
AS13335
—
AS47123
AS47123
—
AS212538
AS212538
—
AS212805
AS212805
—
AS8685
AS8685
—
AS34684
AS34684
—
AS39298
AS39298
—
AS202557
AS202557
—
AS60607
AS60607
—
AS8947
AS8947
—
AS62077
AS62077
—
AS197720
AS197720
—
AS210178
AS210178
—
AS197654
AS197654
—
AS30734
AS30734
—
AS206163
AS206163
—
AS13138
AS13138
—
AS209380
AS209380
—
AS201996
AS201996
—
AS35080
AS35080
—
AS42584
AS42584
—
| Prefix | Name | Country |
|---|---|---|
| 149.0.76.0/24 | AS15924 | — |
| 149.18.4.0/24 | AS15924 | — |
| 159.253.85.0/24 | AS15924 | — |
| 163.5.53.0/24 | AS15924 | — |
| 164.37.72.0/21 | AS15924 | — |
| 178.18.202.0/24 | AS15924 | — |
| 185.114.216.0/23 | AS15924 | — |
| 185.157.46.0/24 | AS15924 | — |
| 185.158.151.0/24 | AS15924 | — |
| 185.180.28.0/23 | AS15924 | — |
| 185.205.17.0/24 | AS15924 | — |
| 185.22.230.0/24 | AS15924 | — |
| 185.233.164.0/24 | AS15924 | — |
| 185.246.113.0/24 | AS15924 | — |
| 188.3.24.0/24 | AS15924 | — |
| 188.3.25.0/24 | AS15924 | — |
| 193.105.243.0/24 | AS15924 | — |
| 193.243.192.0/19 | AS15924 | — |
| 193.243.194.0/24 | AS15924 | — |
| 193.243.200.0/24 | AS15924 | — |
| 193.243.203.0/24 | AS15924 | — |
| 193.243.219.0/24 | AS15924 | — |
| 193.243.223.0/24 | AS15924 | — |
| 194.125.235.0/24 | AS15924 | — |
| 194.242.32.0/24 | AS15924 | — |
| 194.247.59.0/24 | AS15924 | — |
| 195.177.230.0/24 | AS15924 | — |
| 195.177.231.0/24 | AS15924 | — |
| 195.178.105.0/24 | AS15924 | — |
| 195.234.81.0/24 | AS15924 | — |
| 195.46.128.0/19 | AS15924 | — |
| 195.46.128.0/20 | AS15924 | — |
| 195.46.131.0/24 | AS15924 | — |
| 195.46.133.0/24 | AS15924 | — |
| 195.46.136.0/24 | AS15924 | — |
| 195.46.144.0/20 | AS15924 | — |
| 195.46.146.0/24 | AS15924 | — |
| 195.46.152.0/24 | AS15924 | — |
| 195.46.158.0/24 | AS15924 | — |
| 195.87.0.0/17 | AS15924 | — |
Review Google network organization fields, prefixes, peers, upstreams, and downstreams.
Review Cloudflare network organization fields, prefixes, peers, upstreams, and downstreams.
Review Microsoft network organization fields, prefixes, peers, upstreams, and downstreams.
Review Amazon network organization fields, prefixes, peers, upstreams, and downstreams.
AS15924 is an autonomous system number. The current source associates it with BORUSANTELEKOM-AS Vodafone Net Iletisim Hizmetler AS and the region field an unknown region; those values add network context but do not prove a specific service, physical location, or quality level.
They help explain the scale, interconnection depth, and route structure of AS15924. Richer peering and upstream data often indicate broader network reach, but they should still be interpreted together with prefixes and related IP landing pages.
Open a concrete IP page to check how the address maps into AS15924, then compare the prefix, source labels, and query time. Verify operator or service claims with the relevant registry or network operator.
Use real IP and ASN pages to understand ASNs, BGP prefixes, peers, upstreams, and downstreams, including the limits of each snapshot.
Build troubleshooting context from an IP, BGP prefix, ASN, and public network relationships without treating static route data as a packet path.
Compare representative cloud and edge networks by ASN, announced prefixes, peers, upstreams, and downstreams without inferring a specific host or customer workload.