Country
—
ASN LANDING PAGE
radware Radware Ltd
Last updated · Jul 20, 2026
Country
—
Total prefixes
146
IPv4 prefixes
117
IPv6 prefixes
29
radware Radware Ltd currently reports 146 prefixes and 40 upstream, downstream, or peer relationships. These counts describe the current dataset; they do not by themselves prove network quality, reach, or service use.
An ASN page shows the public organization label, country or region, BGP prefixes, and available peer and upstream relationships. It adds network context but cannot confirm a website host, physical facility, security status, or service quality.
radware Radware Ltd is currently associated with an unknown region. These values come from public network sources and are useful lookup clues; an organization label, registration region, and actual service location may differ.
The page shows ASN data returned by the current upstream query; interpret it with the update time. Open representative IP pages from the same network and compare prefixes, source labels, and query times. Verify operator or service claims with the relevant registry or network operator.
Detailed data for this ASN is not available right now.
Detailed data for this ASN is not available right now.
AS198949
AS198949
—
AS36351
AS36351
—
AS25773
AS25773
—
AS23352
AS23352
—
AS1680
AS1680
—
AS3491
AS3491
—
AS1299
AS1299
—
AS36866
AS36866
—
AS2914
AS2914
—
AS21859
AS21859
—
AS12400
AS12400
—
AS6939
AS6939
—
AS31713
AS31713
—
AS8218
AS8218
—
AS5405
AS5405
—
AS4455
AS4455
—
AS14840
AS14840
—
AS24961
AS24961
—
AS29632
AS29632
—
AS137409
AS137409
—
AS5392
AS5392
—
AS5394
AS5394
—
AS6204
AS6204
—
AS8660
AS8660
—
AS9009
AS9009
—
AS9498
AS9498
—
AS12637
AS12637
—
AS12779
AS12779
—
AS13237
AS13237
—
AS15605
AS15605
—
AS24482
AS24482
—
AS28716
AS28716
—
AS49544
AS49544
—
AS49605
AS49605
—
AS49709
AS49709
—
AS50877
AS50877
—
AS51185
AS51185
—
AS57111
AS57111
—
AS59919
AS59919
—
AS60171
AS60171
—
| Prefix | Name | Country |
|---|---|---|
| 141.226.100.0/24 | AS48851 | — |
| 141.226.101.0/24 | AS48851 | — |
| 141.226.102.0/24 | AS48851 | — |
| 141.226.103.0/24 | AS48851 | — |
| 141.226.252.0/24 | AS48851 | — |
| 141.226.253.0/24 | AS48851 | — |
| 141.226.254.0/24 | AS48851 | — |
| 141.226.255.0/24 | AS48851 | — |
| 141.226.97.0/24 | AS48851 | — |
| 141.226.98.0/24 | AS48851 | — |
| 144.249.131.0/24 | AS48851 | — |
| 144.249.133.0/24 | AS48851 | — |
| 144.249.134.0/24 | AS48851 | — |
| 144.249.136.0/24 | AS48851 | — |
| 144.249.139.0/24 | AS48851 | — |
| 144.249.140.0/24 | AS48851 | — |
| 144.249.142.0/24 | AS48851 | — |
| 144.249.157.0/24 | AS48851 | — |
| 144.249.170.0/24 | AS48851 | — |
| 167.17.129.0/24 | AS48851 | — |
| 167.17.133.0/24 | AS48851 | — |
| 167.17.134.0/24 | AS48851 | — |
| 167.17.135.0/24 | AS48851 | — |
| 167.17.137.0/24 | AS48851 | — |
| 167.17.138.0/24 | AS48851 | — |
| 167.17.139.0/24 | AS48851 | — |
| 167.17.141.0/24 | AS48851 | — |
| 167.17.145.0/24 | AS48851 | — |
| 167.86.36.0/24 | AS48851 | — |
| 167.86.39.0/24 | AS48851 | — |
| 167.86.40.0/24 | AS48851 | — |
| 167.86.42.0/24 | AS48851 | — |
| 167.86.44.0/24 | AS48851 | — |
| 167.86.45.0/24 | AS48851 | — |
| 167.86.47.0/24 | AS48851 | — |
| 167.86.48.0/24 | AS48851 | — |
| 167.86.50.0/24 | AS48851 | — |
| 167.86.53.0/24 | AS48851 | — |
| 176.100.160.0/24 | AS48851 | — |
| 176.100.162.0/24 | AS48851 | — |
Review Google network organization fields, prefixes, peers, upstreams, and downstreams.
Review Cloudflare network organization fields, prefixes, peers, upstreams, and downstreams.
Review Microsoft network organization fields, prefixes, peers, upstreams, and downstreams.
Review Amazon network organization fields, prefixes, peers, upstreams, and downstreams.
AS48851 is an autonomous system number. The current source associates it with radware Radware Ltd and the region field an unknown region; those values add network context but do not prove a specific service, physical location, or quality level.
They help explain the scale, interconnection depth, and route structure of AS48851. Richer peering and upstream data often indicate broader network reach, but they should still be interpreted together with prefixes and related IP landing pages.
Open a concrete IP page to check how the address maps into AS48851, then compare the prefix, source labels, and query time. Verify operator or service claims with the relevant registry or network operator.
Use real IP and ASN pages to understand ASNs, BGP prefixes, peers, upstreams, and downstreams, including the limits of each snapshot.
Build troubleshooting context from an IP, BGP prefix, ASN, and public network relationships without treating static route data as a packet path.
Compare representative cloud and edge networks by ASN, announced prefixes, peers, upstreams, and downstreams without inferring a specific host or customer workload.