Cato Networks: PeeringDB fix list

AS13150 · peeringdb.com/net/11851

PeeringDB

39 things to fix in Cato Networks's PeeringDB record, from what its exchanges publish: 5 to add, 33 to correct, 1 at exchanges that look shut down. As of 2026-10-08 20:58 UTC.

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

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

  1. Indonesia IIX-Jakarta Jakarta, Indonesia · PeeringDB 210From its IX-F export
    IPv4123.108.9.184
    IPv62001:7fa:2:5::1b8
    Speed1000 Mbps (1G)
    RS peerYes

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

  2. United Kingdom LONAP London, United Kingdom · PeeringDB 53From its IX-F export
    IPv45.57.82.74
    IPv6–
    Speed5000 Mbps (5G)
    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. Australia MegaIX Brisbane Brisbane, Australia · PeeringDB 781From its IX-F export
    IPv4103.26.70.64
    IPv62001:dea:0:20::40
    SpeedNot published
    RS peerYes

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

  4. Sweden Netnod Stockholm BLUE -- MTU4470 Stockholm, Sweden · PeeringDB 2847From its IX-F export
    IPv4195.69.119.113
    IPv62001:7f8:d:fb::113
    SpeedNot published
    RS peerYes
  5. Sweden Netnod Stockholm GREEN -- MTU4470 Stockholm, Sweden · PeeringDB 2845From its IX-F export
    IPv4195.245.240.113
    IPv62001:7f8:d:fc::113
    SpeedNot published
    RS peerYes

Correct these entries (33)

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. New Zealand AKL-IX (Auckland NZ) Auckland, New Zealand · PeeringDB 977
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7fa:11:6:0:335e:0:1
    • In the entry with IPv4 43.243.21.117: set IPv6 to 2001:7fa:11:6:0:335e:0:1 (now empty).

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

  2. Netherlands AMS-IX Amsterdam, Netherlands · PeeringDB 26
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:1::a501:3150:1
    • In the entry with IPv4 80.249.210.159: set IPv6 to 2001:7f8:1::a501:3150:1 (now empty).

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

  3. Thailand BKNIX (Thailand) Bangkok, Thailand · PeeringDB 1025
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:df5:b881::157
    • In the entry with IPv4 203.159.68.157: set IPv6 to 2001:df5:b881::157 (now empty).

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

  4. Belgium BNIX Brussels, Belgium · PeeringDB 59
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:26::a501:3150:1
    • In the entry with IPv4 194.53.172.85: set IPv6 to 2001:7f8:26::a501:3150:1 (now empty).

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

  5. Canada CANIX Montreal Montreal, Canada · PeeringDB 355
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:504:2d::18:10
    • In the entry with IPv4 198.179.18.10: set IPv6 to 2001:504:2d::18:10 (now empty).

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

  6. India DE-CIX Chennai Chennai, India · PeeringDB 2588
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2400:d180:68::60
    • In the entry with IPv4 103.228.174.60: set IPv6 to 2400:d180:68::60 (now empty).
  7. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8::335e:0:1 2001:7f8::335e:0:2
    • In the entry with IPv4 80.81.197.55: set IPv6 to 2001:7f8::335e:0:1 (now empty).
    • In the entry with IPv4 80.81.197.82: set IPv6 to 2001:7f8::335e:0:2 (now empty).
  8. Portugal DE-CIX Lisbon Lisbon, Portugal · PeeringDB 2531
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:d5::335e:0:1
    • In the entry with IPv4 185.1.131.67: set IPv6 to 2001:7f8:d5::335e:0:1 (now empty).
  9. India DE-CIX Mumbai Mumbai, India · PeeringDB 832
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2401:7500:fff6::5f
    Port speed differs5G10G
    • In the entry with IPv4 103.27.170.248: set IPv6 to 2401:7500:fff6::5f (now empty); set Speed to 10000 (10G) (now 5000).
  10. Germany DE-CIX Munich Munich, Germany · PeeringDB 248
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:44::335e:0:1
    • In the entry with IPv4 185.1.208.14: set IPv6 to 2001:7f8:44::335e:0:1 (now empty).
  11. United States DE-CIX Phoenix Phoenix, United States · PeeringDB 3775
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:504:116::335e:0:1
    • In the entry with IPv4 149.112.27.42: set IPv6 to 2001:504:116::335e:0:1 (now empty).
  12. India Extreme IX Delhi Delhi, India · PeeringDB 1323
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:df2:1900:1::142
    • In the entry with IPv4 45.120.248.142: set IPv6 to 2001:df2:1900:1::142 (now empty).

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

  13. Philippines GetaFIX Manila Manila, Philippines · PeeringDB 2345
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2401:fdc0::1:3150:1
    • In the entry with IPv4 103.104.19.37: set IPv6 to 2401:fdc0::1:3150:1 (now empty).

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

  14. Romania InterLAN-IX Bucharest, Romania · PeeringDB 270
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:64:225:0:1:3150:1
    • In the entry with IPv4 86.104.125.167: set IPv6 to 2001:7f8:64:225:0:1:3150:1 (now empty).

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

  15. Australia IX Australia Melbourne (VIC-IX) Melbourne, Australia · PeeringDB 513
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7fa:11:1:0:335e:0:1
    • In the entry with IPv4 218.100.78.29: set IPv6 to 2001:7fa:11:1:0:335e:0:1 (now empty).

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

  16. Australia IX Australia Perth (WA-IX) Perth, Australia · PeeringDB 21
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7fa:11::335e:0:1
    • In the entry with IPv4 27.106.192.4: set IPv6 to 2001:7fa:11::335e:0:1 (now empty).

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

  17. Australia IX Australia Sydney (NSW-IX) Sydney, Australia · PeeringDB 716
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7fa:11:4:0:335e:0:1
    • In the entry with IPv4 218.100.52.63: set IPv6 to 2001:7fa:11:4:0:335e:0:1 (now empty).

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

  18. Nigeria IXPN Lagos Lagos, Nigeria · PeeringDB 488
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:43f8:bb1::177
    • In the entry with IPv4 196.216.148.177: set IPv6 to 2001:43f8:bb1::177 (now empty).
  19. Kenya KIXP - Nairobi Nairobi, Kenya · PeeringDB 236
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:43f8:60:1::174
    • In the entry with IPv4 196.223.21.174: set IPv6 to 2001:43f8:60:1::174 (now empty).
  20. United Kingdom LINX LON1 London, United Kingdom · PeeringDB 18
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB195.66.227.252195.66.227.252 195.66.228.135
    IPv6 address missing from PeeringDBnone2001:7f8:4::335e:1 2001:7f8:4::335e:2
    Port speed differs100G2 × 100G
    • In the entry with IPv4 195.66.227.252: set IPv6 to 2001:7f8:4::335e:1 (now empty).
    • Add an entry: IPv4 195.66.228.135, IPv6 2001:7f8:4::335e:2, speed 100000 (100G), RS peer yes.
  21. United Kingdom LINX Manchester Manchester, United Kingdom · PeeringDB 583
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:4:2::335e:1
    • In the entry with IPv4 195.66.244.84: set IPv6 to 2001:7f8:4:2::335e:1 (now empty).
  22. United States MICE Minneapolis, MN, United States · PeeringDB 446
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:504:27::335e:0:1
    • In the entry with IPv4 206.108.255.9: set IPv6 to 2001:504:27::335e:0:1 (now empty).

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

  23. Italy Namex Rome Rome, Italy · PeeringDB 121
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:10::1:3150
    • In the entry with IPv4 193.201.29.31: set IPv6 to 2001:7f8:10::1:3150 (now empty).

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

  24. South Africa NAPAfrica IX Cape Town Cape Town, South Africa · PeeringDB 597
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:43f8:6d1::71:161
    • In the entry with IPv4 196.60.71.161: set IPv6 to 2001:43f8:6d1::71:161 (now empty).

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

  25. South Africa NAPAfrica IX Johannesburg Johannesburg, South Africa · PeeringDB 592
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:43f8:6d0::11:8
    • In the entry with IPv4 196.60.11.8: set IPv6 to 2001:43f8:6d0::11:8 (now empty).

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

  26. Denmark Netnod Copenhagen BLUE -- MTU9K Malmo / Copenhagen, Denmark · PeeringDB 2868
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:d:202::113
    • In the entry with IPv4 212.237.192.113: set IPv6 to 2001:7f8:d:202::113 (now empty).
  27. Denmark Netnod Copenhagen GREEN -- MTU9K Malmo / Copenhagen, Denmark · PeeringDB 193
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:d:203::113
    • In the entry with IPv4 212.237.193.113: set IPv6 to 2001:7f8:d:203::113 (now empty).
  28. Sweden Netnod Stockholm BLUE -- MTU1500 Stockholm, Sweden · PeeringDB 2846
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:d:fe::113
    • In the entry with IPv4 194.68.128.113: set IPv6 to 2001:7f8:d:fe::113 (now empty).
  29. Sweden Netnod Stockholm GREEN -- MTU1500 Stockholm, Sweden · PeeringDB 70
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:d:ff::113
    • In the entry with IPv4 194.68.123.113: set IPv6 to 2001:7f8:d:ff::113 (now empty).
  30. Czechia NIX.CZ Prague, Czechia · PeeringDB 71
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:14::1b:1 2001:7f8:14::1b:2
    • In the entry with IPv4 91.210.17.32: set IPv6 to 2001:7f8:14::1b:1 (now empty).
    • In the entry with IPv4 91.210.17.41: set IPv6 to 2001:7f8:14::1b:2 (now empty).

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

  31. United States NWAX Portland, United States · PeeringDB 165
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2620:124:2000::25
    • In the entry with IPv4 198.32.195.25: set IPv6 to 2620:124:2000::25 (now empty).

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

  32. Singapore SGIX Singapore, Singapore · PeeringDB 429
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:de8:12:100::131
    • In the entry with IPv4 103.16.102.131: set IPv6 to 2001:de8:12:100::131 (now empty).
  33. Switzerland SwissIX Zurich, Switzerland · PeeringDB 60
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:24::111
    • In the entry with IPv4 91.206.53.17: set IPv6 to 2001:7f8:24::111 (now empty).

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

Exchanges that look shut down (1)

In PeeringDB, but these exchanges have fewer than two networks besides their operator: nobody to peer with, so they may have shut down. If an exchange is gone, delete its entry.

  1. Canada Equinix Montrealghost Montreal, Canada · PeeringDB 3814

    Only one outside network

    IPv4206.223.115.1
    IPv6–
    Speed10000 Mbps (10G)

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