ixreport

MoeDove Global: PeeringDB fix list

AS44324 · peeringdb.com/net/34997

PeeringDB

6 things to fix in MoeDove Global's PeeringDB record, from what its exchanges publish: 2 to add, 3 to correct, 1 to check. As of 2026-10-08 18:53 UTC.

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

  1. United States FREMIX Fremont, United States · PeeringDB 3685From its website members list
    IPv4149.112.29.116
    IPv62001:504:125:e0::116
    SpeedNot published
    RS peerNot published
  2. Japan MSR IX shibuya, Japan · PeeringDB 4499From its website members list
    IPv4–
    IPv62602:f919:90f:fffa::4432:4
    SpeedNot published
    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. ProblemPeeringDB hasThe export has
    IPv4 address in PeeringDB, not in the export185.1.125.244none
    • In the entry with IPv4 185.1.125.244: set IPv4 to (empty) (now 185.1.125.244).
  2. ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB185.0.24.195185.0.24.195 185.0.24.249
    IPv6 address missing from PeeringDB2001:7f8:aa::1952001:7f8:aa::195 2001:7f8:aa::249
    Port speed differs10G2 × 10G
    • Add an entry: IPv4 185.0.24.249, IPv6 2001:7f8:aa::249, speed 10000 (10G), 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.

  3. Canada ONIX Toronto, Canada · PeeringDB 4059
    ProblemPeeringDB hasThe export has
    Port speed differs1G100M
    • In the entry with IPv4 149.112.50.101: set Speed to 100 (100M) (now 1000).

    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 (1)

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

  1. Ukraine BEE-IX Lviv, Ukraine · PeeringDB 4105Not on its website members list
    IPv4–
    IPv62001:7f8:11f:be00:44:324:0:1
    Speed10000 Mbps (10G)

    This exchange only publishes a website list, and some leave out members who ask not to be listed.

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