Forcepoint Cloud: PeeringDB fix list

AS44444 · peeringdb.com/net/1764

PeeringDB

6 things to fix in Forcepoint Cloud's PeeringDB record, from what its exchanges publish: 3 to add, 3 to correct. As of 2026-10-08 20:58 UTC.

Make the changes on Forcepoint Cloud'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 (3)

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

  1. Switzerland CIXP Geneva, Switzerland · PeeringDB 33From its IX-F export
    IPv4192.65.185.241
    IPv62001:7f8:1c:24a:ad9c::1
    SpeedNot published
    RS peerNo
  2. Australia IX Australia Sydney (NSW-IX) Sydney, Australia · PeeringDB 716From its IX-F export and website members list
    IPv4218.100.52.30
    IPv6–
    Speed10000 Mbps (10G)
    RS peerYes

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

  3. Switzerland SwissIX Zurich, Switzerland · PeeringDB 60From its IX-F export
    IPv491.206.52.215
    IPv62001:7f8:24::d7
    Speed20000 Mbps (20G)
    RS peerYes

    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 (3)

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. United Kingdom LINX LON2 London, United Kingdom · PeeringDB 321
    ProblemPeeringDB hasThe export has
    Port speed differs20G100G
    • In the entry with IPv4 195.66.236.170: set Speed to 100000 (100G) (now 20000).
  2. United States LINX NoVA Ashburn, Reston, Manassas, United States · PeeringDB 777
    ProblemPeeringDB hasThe export has
    Port speed differs10G100G
    • In the entry with IPv4 206.55.196.25: set Speed to 100000 (100G) (now 10000).
  3. United Kingdom LONAP London, United Kingdom · PeeringDB 53
    ProblemPeeringDB hasThe export has
    Port speed differs100G + 20G100G + 40G
    • In the entry with IPv4 5.57.80.34: set Speed to 40000 (40G) (now 20000).

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

From ixreport.com/net/44444/: PeeringDB against each exchange's IX-F export and website members list. Exchanges whose lists couldn't be read on this update aren't included.