Skip to content

Autonomous System

AS6695 · DE-CIX Management GmbH

Overview

RIPE RIS route collectors currently see no prefix originated by AS6695: as far as they can tell, the number is not announced on the Internet right now. In the paths the collectors record, it has 2 upstream neighbours (transit providers or peers) and 456 downstream neighbours (customers or networks it carries). Its most visible upstreams are NETHINKS GmbH (AS8319) and BSE Software GmbH (AS9044). AS6695 was assigned by RIPE NCC, and its registration country is Germany.

Source: RIPEstat (RIPE NCC), RIS route collectors. Read on October 17, 2026 at 4:53 AM UTC. This page is refreshed at most every 12 hours.

Go further

No IPv4 address of this network is known right now, so there is nothing to trace to.

Announced prefixes

IPv4 prefixes (none)

None currently seen.

IPv6 prefixes (none)

None currently seen.

Neighbours

Upstreams (transit or peers) (2)

ASNetworkVisibility
AS8319NETHINKS GmbH47
AS9044BSE Software GmbH38

Downstreams (customers) (456)

ASNetworkVisibility
AS7195EDGEUNO S.A.S2,305
AS14840BR.Digital Telecom1,536
AS4230CLARO S.A.965
AS57463NetIX NetIX Communications JSC440
AS7049Silica Networks Argentina S.A.401
AS137409GSL Networks Pty LTD294
AS28283Adylnet Telecom246
AS38193Transworld Associates (Pvt.) Ltd.221
AS18403FPT Telecom Company173
AS23764CTGNet154
AS1680-140
AS20473The Constant Company, LLC131
AS88811&1 Versatel GmbH118
AS1764Next Layer Telekommunikationsdienstleistungs- und Beratungs GmbH114
AS21574Century Telecom Ltda113
AS9318SK Broadband Co Ltd107
AS29208Quantcom, a.s.106
AS61599-96
AS9269-90
AS17557Pakistan Telecommunication Company Limited84
AS4229Zenlayer Inc81
AS5578SWAN, a.s.78
AS62255BiMajLink d.o.o.72
AS49666Telecommunication Infrastructure Company71
AS201053-70
AS31133PJSC MegaFon69
AS5713Telkom SA Ltd.66
AS22356Durand do Brasil Ltda64
AS58511-64
AS6204INTERKVM HOST SRL63

The 30 most visible of 456.

1 more neighbour appears 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.