ixreport

Swisscom: PeeringDB fix list

AS3303 · peeringdb.com/net/5

PeeringDB

18 things to fix in Swisscom's PeeringDB record, from what its exchanges publish: 5 to add, 11 to correct, 2 to check. As of 2026-10-08 18:53 UTC.

Make the changes on Swisscom'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 (5)

On the exchange's own member list, but not in Swisscom'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.22
    IPv62001:7f8:d0::ce7:1
    SpeedNot published
    RS peerYes
  2. Netherlands Asteroid Amsterdam Amsterdam, Netherlands · PeeringDB 1812From its IX-F export
    IPv4185.1.94.19
    IPv62001:7f8:b6::ce7:1
    Speed10000 Mbps (10G)
    RS peerYes
  3. France Hopus Paris, Lyon, Marseille, Geneva, Zurich, Amsterdam, Frankfurt, France · PeeringDB 1320From its website members list

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

  4. Indonesia IIX-Jakarta Jakarta, Indonesia · PeeringDB 210From its IX-F export
    IPv4123.108.12.117
    IPv62001:7fa:2:5::483
    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.

  5. Australia IX Australia Sydney (NSW-IX) Sydney, Australia · PeeringDB 716From its website members list

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

Correct these entries (11)

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. Switzerland CIXP Geneva, Switzerland · PeeringDB 33
    ProblemPeeringDB hasThe export has
    Port speed differs100G10G
    • In the entry with IPv4 192.65.185.137: set Speed to 10000 (10G) (now 100000).
  2. Singapore DE-CIX ASEAN Singapore, Singapore · PeeringDB 3472
    ProblemPeeringDB hasThe export has
    Port speed differs100M10G
    • In the entry with IPv4 103.162.254.62: set Speed to 10000 (10G) (now 100).
  3. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    Port speed differs50G100G
    • In the entry with IPv4 80.81.193.183: set Speed to 100000 (100G) (now 50000).
  4. Türkiye DE-CIX Istanbul Istanbul, Türkiye · PeeringDB 1150
    ProblemPeeringDB hasThe export has
    Port speed differs1G20G
    • In the entry with IPv4 185.1.48.38: set Speed to 20000 (20G) (now 1000).
  5. India DE-CIX Mumbai Mumbai, India · PeeringDB 832
    ProblemPeeringDB hasThe export has
    Port speed differs300M1G
    • In the entry with IPv4 103.27.170.87: set Speed to 1000 (1G) (now 300).
  6. Australia IX Australia Perth (WA-IX) Perth, Australia · PeeringDB 21
    ProblemPeeringDB hasThe export has
    Port speed differs200M10G
    • In the entry with IPv4 27.106.192.129: set Speed to 10000 (10G) (now 200).

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

  7. Nigeria IXPN Lagos Lagos, Nigeria · PeeringDB 488
    ProblemPeeringDB hasThe export has
    Port speed differs300M1G
    • In the entry with IPv4 196.216.148.41: set Speed to 1000 (1G) (now 300).
  8. Kenya KIXP - Nairobi Nairobi, Kenya · PeeringDB 236
    ProblemPeeringDB hasThe export has
    Port speed differs300M1G
    • In the entry with IPv4 196.223.21.82: set Speed to 1000 (1G) (now 300).
  9. Italy MIX-IT Milan, Italy · PeeringDB 35
    ProblemPeeringDB hasThe export has
    Port speed differs20G100G
    • In the entry with IPv4 217.29.66.17: set Speed to 100000 (100G) (now 20000).
  10. South Africa NAPAfrica IX Cape Town Cape Town, South Africa · PeeringDB 597
    ProblemPeeringDB hasThe export has
    Port speed differs200M10G
    • In the entry with IPv4 196.60.70.151: set Speed to 10000 (10G) (now 200).

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

  11. South Africa NAPAfrica IX Johannesburg Johannesburg, South Africa · PeeringDB 592
    ProblemPeeringDB hasThe export has
    Port speed differs200M1G
    • In the entry with IPv4 196.60.9.18: set Speed to 1000 (1G) (now 200).

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

Check these entries (2)

In PeeringDB, but on none of the exchange's own lists. If Swisscom has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. Sweden Netnod Stockholm BLUE -- MTU1500 Stockholm, Sweden · PeeringDB 2846Not on its IX-F export
    IPv4194.68.128.116
    IPv62001:7f8:d:fe::116
    Speed10000 Mbps (10G)
  2. Sweden Netnod Stockholm GREEN -- MTU1500 Stockholm, Sweden · PeeringDB 70Not on its IX-F export
    IPv4194.68.123.116
    IPv62001:7f8:d:ff::116
    Speed10000 Mbps (10G)

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