ixreport

Radware

AS198949 · Radware

6Exchanges
1On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
–Type
OpenPeering policy
5Using the route servers
3To fix in PeeringDB
0Facilities in PeeringDB

Tools: Where can I peer with Radware? · Where should Radware peer next? · Compare Radware with another network

This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

3 things to fix in Radware's PeeringDB record, from what its exchanges publish: 1 to add, 2 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on Radware's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Add these exchanges (1)

On the exchange's own member list, but not in Radware's PeeringDB record. Add one entry per connection with these values.

  1. Italy Namex Rome Rome, Italy · PeeringDB 121From its IX-F export and website members list

    The exchange's IX-F export and website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

Correct these entries (2)

Addresses or port speeds in PeeringDB that differ from the exchange's IX-F export. The changes below follow the export; if the export is the one that's wrong, tell the exchange instead.

  1. South Africa NAPAfrica IX Johannesburg Johannesburg, South Africa · PeeringDB 592
    ProblemPeeringDB hasThe export has
    Port speed differs10G20G
    • In the entry with IPv4 196.60.9.83: set Speed to 20000 (20G) (now 10000).

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

  2. United Arab Emirates UAE-IX Dubai, United Arab Emirates · PeeringDB 587
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:73::bed3:0:1 2001:7f8:73:0:3:925:0:1
    • In the entry with IPv4 185.1.8.120: set IPv6 to 2001:7f8:73::bed3:0:1 (now empty).
    • In the entry with IPv4 185.1.8.121: set IPv6 to 2001:7f8:73:0:3:925:0:1 (now empty).

Exchanges over time

02468Oct 3, 2026Nov 19, 20266
Show as a table
DateExchanges
Nov 19, 20266
Nov 18, 20267
Nov 17, 20267
Nov 16, 20267
Nov 15, 20267
Nov 14, 20267
Nov 13, 20267
Nov 12, 20267
Nov 11, 20267
Nov 10, 20267
Nov 9, 20267
Nov 8, 20267
Nov 7, 20267
Nov 6, 20267
Nov 5, 20267
Nov 4, 20267
Nov 3, 20267
Nov 2, 20267
Nov 1, 20267
Oct 31, 20267
Oct 30, 20267
Oct 29, 20267
Oct 28, 20267
Oct 27, 20267
Oct 26, 20267
Oct 25, 20266
Oct 24, 20266
Oct 23, 20266
Oct 22, 20266
Oct 21, 20266
Oct 20, 20267
Oct 19, 20267
Oct 18, 20267
Oct 17, 20267
Oct 16, 20267
Oct 15, 20267
Oct 14, 20267
Oct 13, 20267
Oct 12, 20267
Oct 11, 20267
Oct 10, 20267
Oct 9, 20267
Oct 8, 20267
Oct 7, 20267
Oct 6, 20267
Oct 5, 20266
Oct 4, 20267
Oct 3, 20267

Map

Where Radware's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.

Exchanges

Total port capacity 50.3G, at the 5 of 6 exchanges with a speed in PeeringDB or the exchange's IX-F export.

Italy Namex Rome Rome, Italy Not in PeeringDB
South Africa NAPAfrica IX Johannesburg Johannesburg, South Africa 196.60.9.83 2001:43f8:6d0::9:83 10G 60 routes Both Speed differs
Colombia PIT - Colombia - Bogota Bogota, Colombia 45.68.24.193 2801:1a:5800:140::9e 10G Yes PeeringDB
Peru PIT - Peru - Lima Lima, Peru 45.183.47.219 2803:cd60:6411:5::e9 10G Yes PeeringDB
Taiwan TPIX-TW Taipei/Taiwan, Taiwan 203.163.222.147 2406:d400:1:133:203:163:222:147 300M Yes PeeringDB
United Arab Emirates UAE-IX Dubai, United Arab Emirates 185.1.8.120
185.1.8.121
2 × 10G 42 routes Both IPv6 not in PeeringDB

Radware lists no facilities in PeeringDB.