ixreport

StormWall: PeeringDB fix list

AS59796 · peeringdb.com/net/11349

PeeringDB

3 things to fix in StormWall's PeeringDB record, from what its exchanges publish: 2 to add, 1 to correct. As of 2026-10-08 22:13 UTC.

Make the changes on StormWall'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 (2)

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

  1. Switzerland 4b42 Internet Exchange Point Zurich, Switzerland · PeeringDB 2447From its IX-F export and website members list
    IPv4185.1.125.227
    IPv62001:7f8:d0::e994:1
    SpeedNot published
    RS peerYes
  2. Singapore SGIX Singapore, Singapore · PeeringDB 429From its IX-F export
    IPv4103.16.103.97
    IPv62001:de8:12:100::103:97
    Speed100000 Mbps (100G)
    RS peerYes

Correct these entries (1)

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. ProblemPeeringDB hasThe export has
    Address belongs to another network in PeeringDB185.1.125.227 is AS38846 WOLFNET185.1.125.227

    An address another network has in PeeringDB isn't suggested here: either that network's entry or the exchange's export is wrong. Ask the exchange which.

From ixreport.com/net/59796/: 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.