Skip to content

Autonomous System

AS3209 · Vodafone GmbH

Overview

AS3209 is announced on the Internet: RIPE RIS route collectors currently see 300 IPv4 prefixes and 19 IPv6 prefixes originated by this network. Together, its IPv4 prefixes cover 12,755,456 addresses, with overlapping prefixes counted once. In the paths the collectors record, it has 15 upstream neighbours (transit providers or peers) and 97 downstream neighbours (customers or networks it carries). Its most visible upstreams are IDDQD-AS (AS1273), Level 3 Parent, LLC (AS3356), and Deutsche Telekom AG (AS3320). AS3209 was assigned by RIPE NCC, and its registration country is Germany.

Source: RIPEstat (RIPE NCC), RIS route collectors. Read on October 16, 2026 at 8:51 PM UTC. This page is refreshed at most every 12 hours.

Go further

The trace goes to 88.64.0.1, the first address of 88.64.0.0/12. An address picked inside a prefix may not answer (nothing listens there, or the network filters probes): the trace then shows the path up to the last network that replies.

Announced prefixes

IPv4 prefixes (300 prefixes)

PrefixAddresses
2.200.0.0/13524,288
5.10.48.0/204,096
5.10.48.0/212,048
5.10.56.0/212,048
5.10.160.0/198,192
5.10.160.0/204,096
5.10.176.0/204,096
5.45.148.0/221,024
5.56.176.0/204,096
5.56.176.0/212,048
5.56.184.0/212,048
5.56.192.0/1816,384
5.56.192.0/198,192
5.56.224.0/198,192
5.146.0.0/15131,072
5.146.0.0/1665,536
5.147.0.0/1665,536
5.158.128.0/1816,384
5.158.128.0/198,192
5.158.160.0/198,192
24.134.0.0/1665,536
31.16.0.0/14262,144
37.4.0.0/15131,072
37.24.0.0/1665,536
37.24.0.0/1732,768
37.24.128.0/1732,768
37.49.0.0/1732,768
37.49.0.0/1816,384
37.49.64.0/1816,384
37.201.0.0/1665,536
37.201.0.0/1732,768
37.201.128.0/1732,768
37.209.0.0/1732,768
37.209.0.0/1816,384
37.209.64.0/1816,384
45.134.40.0/221,024
46.5.0.0/1665,536
46.5.0.0/1732,768
46.5.128.0/1732,768
46.223.0.0/1665,536
46.223.0.0/1732,768
46.223.128.0/1732,768
46.237.192.0/1816,384
46.237.192.0/198,192
46.237.224.0/198,192
46.252.128.0/204,096
46.252.128.0/212,048
46.252.136.0/212,048
47.64.0.0/13524,288
62.95.128.0/1732,768
62.143.0.0/1665,536
62.143.0.0/1732,768
62.143.128.0/1732,768
77.20.0.0/14262,144
77.24.0.0/1665,536
77.25.0.0/1732,768
78.42.0.0/15131,072
78.42.0.0/1665,536
78.43.0.0/1665,536
78.94.0.0/1665,536
78.94.0.0/1732,768
78.94.128.0/1732,768
80.69.96.0/204,096
80.69.96.0/212,048
80.69.104.0/212,048
80.226.0.0/1665,536
81.11.0.0/1732,768
81.11.0.0/1816,384
81.11.0.0/204,096
81.11.16.0/204,096
81.11.32.0/204,096
81.11.48.0/204,096
81.11.64.0/1816,384
81.11.64.0/204,096
81.11.80.0/204,096
81.11.96.0/204,096
81.11.112.0/204,096
81.16.20.0/24256
81.210.128.0/1732,768
81.210.128.0/1816,384
81.210.192.0/1816,384
82.82.0.0/15131,072
82.82.0.0/204,096
82.212.0.0/1816,384
82.212.0.0/198,192
82.212.32.0/198,192
83.169.128.0/1816,384
84.56.0.0/13524,288
84.118.0.0/15131,072
84.118.0.0/1665,536
84.119.0.0/1665,536
85.118.248.0/212,048
85.216.0.0/1732,768
85.216.0.0/1816,384
85.216.64.0/1816,384
85.238.224.0/198,192
88.64.0.0/121,048,576
88.79.0.0/1816,384
88.134.0.0/1665,536
88.152.0.0/15131,072

Showing the first 100 of 300, in address order. Complete list on RIPEstat

IPv6 prefixes (19 prefixes)

Prefix
2001:650:cc01::/48
2001:678:458::/48
2001:67c:818::/48
2001:67c:d14::/48
2001:67c:e80::/48
2001:67c:297c::/48
2001:67c:2b74::/48
2a00::/22
2a01:860::/32
2a01:867::/32
2a02:908::/32
2a02:908::/33
2a02:908:8000::/33
2a02:8070::/31
2a02:8070::/32
2a02:8071::/32
2a02:8100::/27
2a0d:240::/29
2a10:fb40::/32

Neighbours

Upstreams (transit or peers) (15)

ASNetworkVisibility
AS1273IDDQD-AS10,917
AS3356Level 3 Parent, LLC2,253
AS3320Deutsche Telekom AG498
AS5405Inter.link GmbH369
AS33891Core-Backbone GmbH349
AS50629LWLcom GmbH278
AS60068Datacamp Limited218
AS24961WIIT AG189
AS21320GEANT Vereniging162
AS1299Arelion Sweden AB94
AS6204INTERKVM HOST SRL67
AS9009M247 Europe SRL47
AS88811&1 Versatel GmbH3
AS41095IPTP LTD2
AS8365Man-da.de GmbH1

Downstreams (customers) (97)

ASNetworkVisibility
AS204028DolphinIT Dolphin IT-Systeme e.K.2,081
AS201878Stadtwerke Muehlheim am Main GmbH778
AS21207E.ON Verwaltungs GmbH580
AS206063CompuGroup Medical Deutschland AG513
AS34156DB Systel GmbH501
AS16024GELSEN-NET Kommunikationsgesellschaft mbH409
AS36040Google LLC356
AS201299BWI GmbH354
AS12557SimpleThings SimpleThings GmbH350
AS213251Marcel Andrew Zaiser trading as Metaliance ISP Systems e.k350
AS203865overturn technologies GmbH348
AS48352-345
AS29239-330
AS199725-287
AS201530-267
AS213141-267
AS3278SEW-EURODRIVE GmbH & Co KG260
AS58265-260
AS205887-259
AS15434-258
AS58234-257
AS204445-257
AS205660-257
AS210849-257
AS9135-227
AS12693-218
AS33806-193
AS15933-188
AS201318-188
AS198311-155

The 30 most visible of 97.

6 more neighbours appear on both sides of this network depending on the path, so they are counted in neither list.

Visibility is RIPEstat's count of how often the route collectors observed the link. It compares neighbours with each other; it is not a traffic volume.

How to read this page

An Autonomous System (AS) is a network run under one routing policy: an internet provider, a cloud, a content network, a university. Each one has a number, its ASN, assigned by a regional registry (ARIN, RIPE NCC, APNIC, LACNIC, AFRINIC), and uses BGP, the protocol networks use to tell each other where addresses are, to announce the blocks of addresses it delivers to.

A prefix such as 203.0.113.0/24 is a block of addresses: the number after the slash says how many bits are fixed, so a /24 holds 256 IPv4 addresses and a /16 holds 65,536. Networks often announce a large block and smaller pieces of it at the same time, which is why the address total counts each address once.

Neighbours come from the paths themselves. A network that appears just before this one in a path, on the collector's side, is an upstream: a transit provider or a peer. One that appears just after it is a downstream, usually a customer. Peering at an internet exchange also shows up as an upstream, so the upstream list is not a list of paid transit.

The data comes from RIPEstat, run by the RIPE NCC, which gathers the routing tables of hundreds of networks through its RIS route collectors. This page reads it when it is visited and keeps it for 12 hours at most; the BGP viewer reads it live.

Frequently asked questions

How do I find the ASN of an IP address?
Type the address in the BGP viewer: it shows the prefix that covers it, the AS that originates that prefix and the paths seen towards it. A traceroute also names the network of each hop, so you can see every AS a connection crosses.
Why does one company have several ASNs?
Large operators split their network by region, by activity or by history: a cloud may use one number for its backbone and another for a region, and every acquisition brings its own numbers. Each number has its own page, with its own prefixes and neighbours.
Why do prefix counts differ from one site to another?
Each source sees the routing table from different collectors, at a different time, and counts differently: some include prefixes withdrawn in recent weeks, some merge a block and its pieces. This page counts the prefixes RIPE RIS collectors see originated by the network at the end of the latest two-week window, and counts each IPv4 address once.
Is this the list of IP ranges of a cloud provider?
It is what its networks announce, which is what the Internet routes to them. Many providers also publish an official list of ranges per service and region; that list is the reference for firewall rules, because a range can be announced before it is used, or announced by another of their AS numbers.