Radware
AS198949 · Radware
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.
-
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.
-
Problem PeeringDB has The export has Port speed differs 10G 20G - 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.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001: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
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 6 |
| Nov 18, 2026 | 7 |
| Nov 17, 2026 | 7 |
| Nov 16, 2026 | 7 |
| Nov 15, 2026 | 7 |
| Nov 14, 2026 | 7 |
| Nov 13, 2026 | 7 |
| Nov 12, 2026 | 7 |
| Nov 11, 2026 | 7 |
| Nov 10, 2026 | 7 |
| Nov 9, 2026 | 7 |
| Nov 8, 2026 | 7 |
| Nov 7, 2026 | 7 |
| Nov 6, 2026 | 7 |
| Nov 5, 2026 | 7 |
| Nov 4, 2026 | 7 |
| Nov 3, 2026 | 7 |
| Nov 2, 2026 | 7 |
| Nov 1, 2026 | 7 |
| Oct 31, 2026 | 7 |
| Oct 30, 2026 | 7 |
| Oct 29, 2026 | 7 |
| Oct 28, 2026 | 7 |
| Oct 27, 2026 | 7 |
| Oct 26, 2026 | 7 |
| Oct 25, 2026 | 6 |
| Oct 24, 2026 | 6 |
| Oct 23, 2026 | 6 |
| Oct 22, 2026 | 6 |
| Oct 21, 2026 | 6 |
| Oct 20, 2026 | 7 |
| Oct 19, 2026 | 7 |
| Oct 18, 2026 | 7 |
| Oct 17, 2026 | 7 |
| Oct 16, 2026 | 7 |
| Oct 15, 2026 | 7 |
| Oct 14, 2026 | 7 |
| Oct 13, 2026 | 7 |
| Oct 12, 2026 | 7 |
| Oct 11, 2026 | 7 |
| Oct 10, 2026 | 7 |
| Oct 9, 2026 | 7 |
| Oct 8, 2026 | 7 |
| Oct 7, 2026 | 7 |
| Oct 6, 2026 | 7 |
| Oct 5, 2026 | 6 |
| Oct 4, 2026 | 7 |
| Oct 3, 2026 | 7 |
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.
| Namex Rome Rome, Italy | Not in PeeringDB | ||
| NAPAfrica IX Johannesburg Johannesburg, South Africa | 10G | Both Speed differs | |
| PIT - Colombia - Bogota Bogota, Colombia | 10G | PeeringDB | |
| PIT - Peru - Lima Lima, Peru | 10G | PeeringDB | |
| TPIX-TW Taipei/Taiwan, Taiwan | 300M | PeeringDB | |
| UAE-IX Dubai, United Arab Emirates | 2 × 10G | Both IPv6 not in PeeringDB |
Radware lists no facilities in PeeringDB.