Wasabi Technologies: PeeringDB fix list

AS395717 · peeringdb.com/net/17597

PeeringDB

4 things to fix in Wasabi Technologies's PeeringDB record, from what its exchanges publish: 4 to add. As of 2026-10-08 21:35 UTC.

Make the changes on Wasabi Technologies'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 (4)

On the exchange's own member list, but not in Wasabi Technologies'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. Singapore MegaIX Singapore Singapore, Singapore · PeeringDB 965From its IX-F export
    IPv4103.41.12.38
    IPv62001:ded::26
    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.

  3. Australia MegaIX Sydney Sydney, Australia · PeeringDB 780From its IX-F export
    IPv4103.26.68.250
    IPv62001:dea:0:10::fa
    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. Canada MegaIX Toronto Toronto, Canada · PeeringDB 1307From its IX-F export
    IPv4206.53.203.23
    IPv62606:a980:0:8::17
    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.

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