Skip to content

Autonomous System

AS6777 · Amsterdam Internet Exchange B.V.

Overview

RIPE RIS route collectors currently see no prefix originated by AS6777: as far as they can tell, the number is not announced on the Internet right now. In the paths the collectors record, it has 5 upstream neighbours (transit providers or peers) and 500 downstream neighbours (customers or networks it carries). Its most visible upstreams are LWLcom GmbH (AS50629), FBW NETWORKS SAS (AS49434), and TBISS Ltd (AS42295). AS6777 was assigned by RIPE NCC, and its registration country is Netherlands.

Source: RIPEstat (RIPE NCC), RIS route collectors. Read on October 16, 2026 at 8:58 PM 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) (5)

ASNetworkVisibility
AS50629LWLcom GmbH4,305
AS49434FBW NETWORKS SAS3,697
AS42295TBISS Ltd536
AS30886PP KOM i TEX524
AS62000SERVERD SAS66

Downstreams (customers) (500)

ASNetworkVisibility
AS7195EDGEUNO S.A.S2,582
AS2603NORDUnet828
AS137409GSL Networks Pty LTD797
AS41095IPTP LTD456
AS12552GlobalConnect AB443
AS8966EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSC437
AS18678INTERNEXA S.A. E.S.P419
AS9050Orange Romania S.A.400
AS35598INETCOM CARRIER LLC325
AS39386Saudi Telecom Company JSC299
AS31027-279
AS12400Partner Communications Ltd.255
AS2119-247
AS5606-235
AS8732JSC Comcor202
AS1267WIND TRE S.P.A.191
AS6461Zayo Bandwidth174
AS47147Anexia Cloud Solutions GmbH155
AS28725-136
AS31133PJSC MegaFon134
AS12713-133
AS12578-125
AS50263A-Systems Sp. z o.o.120
AS8400TELEKOM SRBIJA a.d.103
AS2686AT&T Enterprises, LLC100
AS57463NetIX NetIX Communications JSC99
AS50673Serverius Holding B.V.98
AS196844Institute of Bioorganic Chemistry Polish Academy of Science, Poznan Supercomputing and Networking Center98
AS59692IQWeb FZ-LLC97
AS9038Al Bahrainia al Urdunia Liltaknia Wa Alitisalat Plc. Co96

The 30 most visible of 500.

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.