Kamel Networks: PeeringDB fix list

AS213113 · peeringdb.com/net/23520

PeeringDB

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

Make the changes on Kamel Networks'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 Kamel Networks's PeeringDB record. Add one entry per connection with these values.

  1. Sweden Netnod Stockholm BLUE -- MTU1500 Stockholm, Sweden · PeeringDB 2846From its IX-F export
    IPv4194.68.128.103
    IPv62001:7f8:d:fe::103
    Speed100000 Mbps (100G)
    RS peerYes
  2. Sweden Netnod Stockholm BLUE -- MTU4470 Stockholm, Sweden · PeeringDB 2847From its IX-F export
    IPv4195.69.119.103
    IPv62001:7f8:d:fb::103
    Speed100000 Mbps (100G)
    RS peerYes
  3. Sweden Netnod Stockholm GREEN -- MTU4470 Stockholm, Sweden · PeeringDB 2845From its IX-F export
    IPv4195.245.240.103
    IPv62001:7f8:d:fc::103
    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. Sweden Netnod Stockholm GREEN -- MTU1500 Stockholm, Sweden · PeeringDB 70
    ProblemPeeringDB hasThe export has
    Port speed differs100M100G
    • In the entry with IPv4 194.68.123.103: set Speed to 100000 (100G) (now 100).

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