CacheFly: PeeringDB fix list

AS30081 · peeringdb.com/net/906

PeeringDB

12 things to fix in CacheFly's PeeringDB record, from what its exchanges publish: 7 to add, 3 to correct, 2 to check. As of 2026-10-08 20:58 UTC.

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

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

  1. India DE-CIX Mumbai Mumbai, India · PeeringDB 832From 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. Sweden Netnod Stockholm BLUE -- MTU4470 Stockholm, Sweden · PeeringDB 2847From its IX-F export
    IPv4195.69.119.185
    IPv62001:7f8:d:fb::185
    Speed50000000 Mbps (50T)
    RS peerYes
  3. Sweden Netnod Stockholm GREEN -- MTU4470 Stockholm, Sweden · PeeringDB 2845From its IX-F export
    IPv4195.245.240.185
    IPv62001:7f8:d:fc::185
    Speed50000000 Mbps (50T)
    RS peerYes
  4. United States Ohio IX Columbus, United States · PeeringDB 869From 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.

  5. United States OmahaIX Omaha, United States · PeeringDB 809From its website members list
    IPv4206.126.235.58
    IPv62001:504:33::58
    SpeedNot published
    RS peerNot published
  6. Puerto Rico PR-IX San Juan, Puerto Rico · PeeringDB 2353From 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.

  7. United States SFMIX San Francisco, United States · PeeringDB 155From its IX-F export and website members list
    IPv4206.197.187.83
    IPv62001:504:30::ba03:81:1
    Speed100000 Mbps (100G)
    RS peerNot published

Correct these entries (3)

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. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 100G100G

    PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.

  2. Sweden Netnod Stockholm BLUE -- MTU1500 Stockholm, Sweden · PeeringDB 2846
    ProblemPeeringDB hasThe export has
    Port speed differs50G50T
    • In the entry with IPv4 194.68.128.185: set Speed to 50000000 (50T) (now 50000).
  3. Sweden Netnod Stockholm GREEN -- MTU1500 Stockholm, Sweden · PeeringDB 70
    ProblemPeeringDB hasThe export has
    Port speed differs50G50T
    • In the entry with IPv4 194.68.123.185: set Speed to 50000000 (50T) (now 50000).

Check these entries (2)

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

  1. United States MegaIX New York New York, United States · PeeringDB 4318Not on its IX-F export
    IPv4206.53.173.6
    IPv62606:a980:0:2::6
    SpeedNot published
  2. Singapore MegaIX Singapore Singapore, Singapore · PeeringDB 965Not on its IX-F export
    IPv4103.41.12.57
    IPv62001:ded::39
    SpeedNot published

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