Skip to content

Autonomous System

AS215628 · Xenox IT & Kommunikations GmbH

Overview

AS215628 is announced on the Internet: RIPE RIS route collectors currently see 9 IPv4 prefixes and 4 IPv6 prefixes originated by this network. Together, its IPv4 prefixes cover 2,304 addresses, with overlapping prefixes counted once. In the paths the collectors record, it has 14 upstream neighbours (transit providers or peers) and 3 downstream neighbours (customers or networks it carries). Its most visible upstreams are MMC GmbH (AS12577), Hurricane Electric LLC (AS6939), and RETN Limited (AS9002). AS215628 was assigned by RIPE NCC, and its registration country is Austria.

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

Go further

The trace goes to 66.203.252.1, the first address of 66.203.252.0/24. 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 (9 prefixes)

PrefixAddresses
66.203.252.0/24256
66.228.90.0/24256
66.228.91.0/24256
94.156.245.0/24256
109.175.234.0/24256
194.62.113.0/24256
203.32.197.0/24256
203.56.45.0/24256
217.13.99.0/24256

IPv6 prefixes (4 prefixes)

Prefix
2a0d:6c00::/31
2a0d:6c02::/31
2a0d:6c04::/31
2a0d:6c06::/31

Neighbours

Upstreams (transit or peers) (14)

ASNetworkVisibility
AS12577MMC GmbH114,503
AS6939Hurricane Electric LLC34,220
AS9002RETN Limited2,886
AS5405Inter.link GmbH1,673
AS6663Euroweb Romania S.R.L.593
AS8218Zayo Infrastructure France SA256
AS15576NTS workspace AG97
AS47147Anexia Cloud Solutions GmbH71
AS15958CETIN Ltd. Belgrade67
AS6204INTERKVM HOST SRL45
AS48362Stadtwerke Feldkirch20
AS14840BR.Digital Telecom8
AS41327Fiber Telecom S.p.A.8
AS263444Open X Tecnologia Ltda4

Downstreams (customers) (3)

ASNetworkVisibility
AS199156Peter Roubicek368
AS219198open mind consulting gmbh366
AS199596EL KOM - Electronic u. Kommunikationstechnik GmbH259

147 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.