CIRA-CLOUD1: PeeringDB fix list

AS55195 · peeringdb.com/net/6591

PeeringDB

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

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

  1. Japan BBIX Tokyo Tokyo, Japan · PeeringDB 126From 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.

  2. 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 (4)

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 LON1 London, United Kingdom · PeeringDB 18
    ProblemPeeringDB hasThe export has
    Port speed differs1G10G
    • In the entry with IPv4 195.66.226.79: set Speed to 10000 (10G) (now 1000).
  2. United Kingdom LONAP London, United Kingdom · PeeringDB 53
    ProblemPeeringDB hasThe export has
    Port speed differs1G5G
    • In the entry with IPv4 5.57.81.125: set Speed to 5000 (5G) (now 1000).

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

  3. Canada MBIX Winnipeg, Manitoba, Canada · PeeringDB 703
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB206.72.208.6206.72.208.6 206.72.208.9
    IPv6 address missing from PeeringDB2001:504:26::5:5195:12001:504:26::5:5195:1 2001:504:26::5:5195:2
    • In the entry with IPv4 206.72.208.6: set IPv6 to (empty) (now 2001:504:26::5:5195:1).
    • Add an entry: IPv4 –, IPv6 2001:504:26::5:5195:1, RS peer yes.
    • Add an entry: IPv4 206.72.208.9, IPv6 –, RS peer yes.
    • Add an entry: IPv4 –, IPv6 2001:504:26::5:5195:2, RS peer yes.

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

  4. Czechia Peering.cz Prague, Bratislava, Vienna, Frankfurt, Czechia · PeeringDB 713
    ProblemPeeringDB hasThe export has
    Port speed differs10G1.25G
    • In the entry with IPv4 185.0.20.135: set Speed to 1250 (1.25G) (now 10000).

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