Skip to content

Autonomous System

AS49544 · i3Dnet i3D.net B.V

Overview

AS49544 is announced on the Internet: RIPE RIS route collectors currently see 138 IPv4 prefixes and 52 IPv6 prefixes originated by this network. Together, its IPv4 prefixes cover 116,992 addresses, with overlapping prefixes counted once. In the paths the collectors record, it has 130 upstream neighbours (transit providers or peers) and 34 downstream neighbours (customers or networks it carries). Its most visible upstreams are Level 3 Parent, LLC (AS3356), NTT America, Inc. (AS2914), and Hurricane Electric LLC (AS6939). AS49544 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

Trace a route to this networkOpen in the BGP viewerWHOIS of 5.200.0.1

The trace goes to 5.200.0.1, the first address of 5.200.0.0/19. 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 (138 prefixes)

PrefixAddresses
5.180.216.0/23512
5.180.218.0/23512
5.200.0.0/198,192
5.200.5.0/24256
5.200.31.0/24256
31.204.128.0/198,192
31.204.132.0/221,024
31.204.136.0/23512
31.204.140.0/221,024
31.204.144.0/24256
31.204.145.0/24256
31.204.156.0/23512
43.239.136.0/221,024
45.147.87.0/24256
45.149.251.0/24256
45.153.18.0/23512
66.22.196.0/221,024
66.22.200.0/221,024
66.22.204.0/221,024
66.22.208.0/221,024
66.22.212.0/221,024
66.22.218.0/23512
66.22.220.0/23512
66.22.222.0/23512
66.22.224.0/23512
66.22.226.0/23512
66.22.230.0/24256
66.22.231.0/24256
66.22.232.0/24256
66.22.233.0/24256
66.22.234.0/24256
66.22.235.0/24256
66.22.236.0/24256
66.22.237.0/24256
66.22.238.0/24256
66.22.240.0/24256
66.22.241.0/24256
66.22.242.0/24256
66.22.243.0/24256
66.22.244.0/24256
66.22.245.0/24256
66.22.246.0/24256
66.22.248.0/24256
89.104.160.0/212,048
89.104.168.0/23512
89.104.170.0/23512
89.104.172.0/221,024
89.104.176.0/23512
89.104.178.0/23512
89.104.180.0/24256
89.104.181.0/24256
91.195.234.0/23512
91.216.207.0/24256
91.221.208.0/24256
91.233.67.0/24256
103.159.122.0/23512
103.194.164.0/221,024
104.153.84.0/221,024
109.200.192.0/198,192
109.200.194.0/23512
109.200.198.0/23512
109.200.208.0/221,024
109.200.212.0/221,024
109.200.220.0/221,024
130.254.64.0/198,192
130.254.80.0/23512
130.254.84.0/23512
130.254.88.0/23512
130.254.90.0/23512
138.128.136.0/221,024
138.128.140.0/221,024
146.247.72.0/221,024
162.244.52.0/23512
162.244.54.0/23512
162.245.204.0/221,024
185.38.20.0/221,024
185.41.140.0/221,024
185.50.104.0/221,024
185.52.12.0/221,024
185.77.208.0/221,024
185.162.56.0/221,024
185.171.240.0/221,024
185.172.132.0/221,024
185.179.200.0/24256
185.179.201.0/24256
185.179.202.0/23512
185.185.212.0/221,024
185.191.240.0/221,024
185.197.24.0/23512
185.197.26.0/23512
185.218.164.0/24256
185.218.165.0/24256
185.218.166.0/24256
188.122.64.0/198,192
188.122.68.0/23512
188.122.78.0/23512
188.122.80.0/23512
193.43.218.0/24256
194.2.155.0/24256
194.61.59.0/24256

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

IPv6 prefixes (52 prefixes)

Prefix
2406:d140:8000::/34
2a00:1630::/29
2a00:1630::/32
2a00:1630:5200::/48
2a00:1631::/32
2a00:1632::/32
2a00:1633::/32
2a00:1634::/32
2a00:1635::/32
2a00:1636::/32
2a00:1637::/32
2a00:1708::/32
2a00:1d20::/34
2a00:1d20:4000::/34
2a00:1d20:8000::/34
2a00:1d21::/32
2a00:1d22::/32
2a00:1d24::/32
2a00:1d25::/32
2a00:1d26::/34
2a00:1d26:4000::/34
2a00:1d26:8000::/34
2a00:1d26:c000::/34
2a00:1d27::/32
2a00:1e29::/32
2a01:9580::/34
2a01:9580:4000::/34
2a01:9580:8000::/34
2a01:9580:c000::/34
2a04:7141::/36
2a04:c600::/29
2a04:c600::/32
2a04:c602::/32
2a04:c603::/32
2a04:c604::/32
2a04:c605::/32
2a04:c606::/32
2a04:c607::/32
2a05:6440::/29
2a0a:2140::/29
2a0a:5980::/29
2a0a:8000::/29
2a0b:1b00::/29
2a0b:d9c0:164::/48
2a0b:d9c0:165::/48
2a0b:d9c0:166::/48
2a0e:5940:20::/44
2a0e:5940:90::/44
2a0e:6b00::/48
2a0f:8200::/32
2a13:3ec0::/29
2a13:d780::/29

Neighbours

Upstreams (transit or peers) (130)

ASNetworkVisibility
AS3356Level 3 Parent, LLC142,163
AS2914NTT America, Inc.115,797
AS6939Hurricane Electric LLC37,444
AS1299Arelion Sweden AB29,950
AS12956TELEFONICA GLOBAL SOLUTIONS SL23,550
AS3491PCCW Global (HK) Ltd.14,153
AS9002RETN Limited10,375
AS9498BHARTI Airtel Ltd.3,840
AS7195EDGEUNO S.A.S3,313
AS3216PJSC "Vimpelcom"2,927
AS4637Telstra Global2,536
AS12389PJSC Rostelecom2,377
AS137409GSL Networks Pty LTD2,144
AS8220COLT Technology Services Group Limited1,854
AS14840BR.Digital Telecom1,734
AS37468Angola Cables1,710
AS1273IDDQD-AS1,686
AS52320GlobeNet Cabos Submarinos Colombia, S.A.S.1,676
AS6830LibertyGlobal Liberty Global Europe Holding B.V.1,493
AS33891Core-Backbone GmbH1,426
AS13786Seabras 1 USA, LLC1,182
AS22356Durand do Brasil Ltda1,180
AS20485Joint Stock Company TransTeleCom1,155
AS6461Zayo Bandwidth1,093
AS4230CLARO S.A.1,078
AS20473The Constant Company, LLC1,013
AS64049Reliance Jio Infocomm Pte Ltd Singapore995
AS31133PJSC MegaFon844
AS8359MTS PJSC811
AS20764CJSC RASCOM737

The 30 most visible of 130.

Downstreams (customers) (34)

ASNetworkVisibility
AS64404Stichting EventInfra735
AS141383VERGE CLOUD PRIVATE LIMITED635
AS58272LeaderTelecom B.V.565
AS53991Acronis539
AS5419Cubic Circle B.V.518
AS200851Bamboozle Web Services MEA FZ-LLC473
AS48283Stichting Internet Domeinregistratie Nederland349
AS49078SC UBISOFT SRL321
AS215747NubaCloud NubaCloud B.V.321
AS214783Danny Nieuwenhuis trading as DedicatedNodes320
AS205316-319
AS200342-318
AS211769-318
AS62370-314
AS202625-314
AS199332-293
AS56851-273
AS202918-270
AS13720Daybreak Game Company LLC269
AS400944-269
AS201510-268
AS203656-268
AS208917-268
AS42473Anexia Cloud Solutions GmbH265
AS62731247RACK.com205
AS50889-200
AS20756-173
AS197156-154
AS209453GANDI SAS138
AS209510-104

The 30 most visible of 34.

6,378 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.