FLIP: PeeringDB fix list

AS133898 · peeringdb.com/net/20649

PeeringDB

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

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

  1. Australia IX Australia Melbourne (VIC-IX) Melbourne, Australia · PeeringDB 513From its IX-F export
    IPv4218.100.78.72
    IPv62001:7fa:11:1:2:b0a:0:1
    Speed10000 Mbps (10G)
    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. Australia IX Australia Sydney (NSW-IX) Sydney, Australia · PeeringDB 716From its IX-F export and website members list
    IPv4218.100.53.72
    IPv62001:7fa:11:4:2:e37:0:1
    Speed20000 Mbps (20G)
    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 Melbourne Melbourne, Australia · PeeringDB 779From its IX-F export
    IPv4103.26.71.52
    IPv62001:dea:0:30::34
    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. Australia MegaIX Sydney Sydney, Australia · PeeringDB 780From its IX-F export
    IPv4103.26.69.119
    IPv62001:dea:0:10::177
    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/133898/: 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.