Skip to content

Autonomous System

AS54253 · Oracle Corporation

Overview

AS54253 is announced on the Internet: RIPE RIS route collectors currently see 369 IPv4 prefixes and 467 IPv6 prefixes originated by this network. Together, its IPv4 prefixes cover 305,408 addresses, with overlapping prefixes counted once. In the paths the collectors record, it has 33 upstream neighbours (transit providers or peers) and no downstream neighbour (customers or networks it carries). Its most visible upstreams are Oracle Corporation (AS31898), Kuwait Telecommunications Company K.S.C.C. (AS47589), and Zain Omantel International FZ-LLC (AS8529). AS54253 was assigned by ARIN, and its registration country is United States.

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 151.104.80.1

The trace goes to 151.104.80.1, the first address of 151.104.80.0/20. 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 (369 prefixes)

PrefixAddresses
40.233.32.0/221,024
40.233.32.0/23512
40.233.34.0/23512
40.233.36.0/23512
40.233.40.0/212,048
40.233.48.0/212,048
51.170.4.0/221,024
64.181.130.0/23512
79.72.22.0/23512
79.72.36.0/23512
79.72.39.0/24256
79.72.96.0/221,024
79.72.96.0/23512
79.72.98.0/23512
79.72.100.0/23512
79.72.104.0/212,048
79.72.112.0/212,048
79.72.128.0/221,024
79.72.128.0/23512
79.72.130.0/23512
79.72.132.0/23512
79.72.136.0/212,048
79.72.144.0/212,048
79.76.21.0/24256
79.76.22.0/23512
79.76.64.0/221,024
79.76.64.0/23512
79.76.66.0/23512
79.76.68.0/23512
79.76.72.0/212,048
79.76.80.0/212,048
80.225.0.0/221,024
80.225.0.0/23512
80.225.2.0/23512
80.225.4.0/23512
80.225.8.0/212,048
80.225.16.0/212,048
80.225.32.0/221,024
80.225.32.0/23512
80.225.34.0/23512
80.225.36.0/23512
80.225.40.0/212,048
80.225.48.0/212,048
80.225.96.0/221,024
80.225.96.0/23512
80.225.98.0/23512
80.225.100.0/23512
80.225.104.0/212,048
80.225.112.0/212,048
81.126.145.0/24256
84.8.0.0/221,024
84.8.0.0/23512
84.8.2.0/23512
84.8.4.0/23512
84.8.8.0/212,048
84.8.16.0/212,048
84.8.32.0/221,024
84.8.32.0/23512
84.8.34.0/23512
84.8.36.0/23512
84.8.40.0/212,048
84.8.48.0/212,048
84.8.160.0/221,024
84.8.160.0/23512
84.8.162.0/23512
84.8.164.0/23512
84.8.168.0/212,048
84.8.176.0/212,048
84.235.128.0/221,024
84.235.128.0/23512
84.235.130.0/23512
84.235.132.0/23512
84.235.136.0/212,048
84.235.144.0/212,048
84.235.194.0/23512
92.4.0.0/221,024
92.4.0.0/23512
92.4.2.0/23512
92.4.4.0/23512
92.4.8.0/212,048
92.4.16.0/212,048
92.4.32.0/221,024
92.4.32.0/23512
92.4.34.0/23512
92.4.36.0/23512
92.4.38.0/24256
92.4.40.0/212,048
92.4.48.0/212,048
92.4.96.0/221,024
92.4.96.0/23512
92.4.98.0/23512
92.4.100.0/23512
92.4.104.0/212,048
92.4.112.0/212,048
130.162.200.0/212,048
131.186.48.0/221,024
131.186.48.0/23512
131.186.50.0/23512
131.186.52.0/23512
131.186.96.0/221,024

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

IPv6 prefixes (467 prefixes)

Prefix
2600:2004::/40
2600:2004:100::/40
2600:2004:1000::/39
2600:2004:1000::/44
2600:2004:1200::/39
2600:2004:1200::/44
2600:2004:2000::/40
2600:2004:2000::/44
2600:2004:2100::/40
2600:2004:2100::/44
2600:2004:2800::/40
2600:2004:2800::/44
2600:2004:2900::/40
2600:2004:2900::/44
2600:2005::/36
2600:2005:2000::/36
2600:2006::/35
2600:2006:4000::/35
2600:200c::/40
2600:200c:100::/40
2600:200c:1000::/39
2600:200c:1000::/44
2600:200c:1200::/39
2600:200c:1200::/44
2600:200c:2000::/40
2600:200c:2000::/44
2600:200c:2100::/40
2600:200c:2100::/44
2600:200c:2800::/40
2600:200c:2800::/44
2600:200c:2900::/40
2600:200c:2900::/44
2600:200d::/36
2600:200d:2000::/36
2600:200e::/35
2600:200e:4000::/35
2603:c044:100::/40
2603:c044:1200::/39
2603:c044:1200::/44
2603:c044:2100::/40
2603:c044:2100::/44
2603:c044:2900::/40
2603:c044:2900::/44
2603:c045:2000::/36
2603:c046:4000::/35
2603:c048::/40
2603:c048:100::/40
2603:c048:1000::/39
2603:c048:1000::/44
2603:c048:1200::/39
2603:c048:1200::/44
2603:c048:2000::/40
2603:c048:2000::/44
2603:c048:2100::/40
2603:c048:2100::/44
2603:c048:2800::/40
2603:c048:2800::/44
2603:c048:2900::/40
2603:c048:2900::/44
2603:c049::/36
2603:c049:2000::/36
2603:c04a::/35
2603:c04a:4000::/35
2603:c054::/40
2603:c054:100::/40
2603:c054:1000::/39
2603:c054:1000::/44
2603:c054:1200::/39
2603:c054:1200::/44
2603:c054:2000::/40
2603:c054:2000::/44
2603:c054:2100::/40
2603:c054:2100::/44
2603:c054:2800::/40
2603:c054:2800::/44
2603:c054:2900::/40
2603:c054:2900::/44
2603:c055::/36
2603:c055:2000::/36
2603:c056::/35
2603:c056:4000::/35
2603:c058::/40
2603:c058:100::/40
2603:c058:1000::/39
2603:c058:1000::/44
2603:c058:1200::/39
2603:c058:1200::/44
2603:c058:2000::/40
2603:c058:2000::/44
2603:c058:2100::/40
2603:c058:2100::/44
2603:c058:2800::/40
2603:c058:2800::/44
2603:c058:2900::/40
2603:c058:2900::/44
2603:c059::/36
2603:c059:2000::/36
2603:c05a::/35
2603:c05a:4000::/35
2603:c060::/40

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

Neighbours

Upstreams (transit or peers) (33)

ASNetworkVisibility
AS31898Oracle Corporation1,225
AS47589Kuwait Telecommunications Company K.S.C.C.685
AS8529Zain Omantel International FZ-LLC549
AS15802Emirates Integrated Telecommunications Company PJSC467
AS4826Vocus Connect International Backbone465
AS8781Ooredoo Q.S.C.451
AS8966EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSC428
AS6619SamsungSDS Inc.416
AS4637Telstra Global400
AS4230CLARO S.A.390
AS39386Saudi Telecom Company JSC389
AS3356Level 3 Parent, LLC365
AS132280Symphony Communication (Thailand) PCL.365
AS14840BR.Digital Telecom364
AS47169-363
AS1273IDDQD-AS359
AS58682Level3 Carrier Ltd.358
AS6461Zayo Bandwidth346
AS46887Crown Castle Fiber LLC341
AS8220COLT Technology Services Group Limited327
AS6453TATA COMMUNICATIONS (AMERICA) INC324
AS48728vodafoneqatar Vodafone Qatar P.Q.S.C294
AS20746Telecom Italia S.p.A.265
AS1299Arelion Sweden AB258
AS2914NTT America, Inc.227
AS45458SBN-ISP/AWN-ISP and SBN-NIX/AWN-NIX221
AS702Verizon Business98
AS24324Kordia Limited69
AS50010-50
AS5483Magyar Telekom Plc.45

The 30 most visible of 33.

Downstreams (customers) (0)

None seen.

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.