ixreport

GlobalEdge: PeeringDB fix list

AS136181

5 things to fix in GlobalEdge's PeeringDB record, from what its exchanges publish: 3 to add, 2 to correct. As of 2026-10-08 21:56 UTC.

AS136181 has no PeeringDB record. Create one (register, then request the network for your organisation) before adding these exchanges.

Add these exchanges (3)

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

  1. Australia MegaIX Melbourne Melbourne, Australia · PeeringDB 779From its IX-F export
    IPv4103.26.71.27
    IPv62001:dea:0:30::1b
    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.

  2. Australia MegaIX Perth Perth, Australia · PeeringDB 1235From its IX-F export
    IPv4202.12.243.59
    IPv62001:dea:0:50::3b
    SpeedNot published
    RS peerNo

    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.146
    IPv62001:dea:0:10::92
    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.

Correct these entries (2)

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. Australia MegaIX Perth Perth, Australia · PeeringDB 1235
    ProblemPeeringDB hasThe export has
    Address belongs to another network in PeeringDB202.12.243.59 is AS139084 FUTURE BROADBAND (AS139084)202.12.243.59
    Address belongs to another network in PeeringDB2001:dea:0:50::3b is AS139084 FUTURE BROADBAND (AS139084)2001:dea:0:50::3b

    An address another network has in PeeringDB isn't suggested here: either that network's entry or the exchange's export is wrong. Ask the exchange which.

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

  2. Australia MegaIX Sydney Sydney, Australia · PeeringDB 780
    ProblemPeeringDB hasThe export has
    Address belongs to another network in PeeringDB103.26.68.146 is AS139084 FUTURE BROADBAND (AS139084)103.26.68.146
    Address belongs to another network in PeeringDB2001:dea:0:10::92 is AS139084 FUTURE BROADBAND (AS139084)2001:dea:0:10::92

    An address another network has in PeeringDB isn't suggested here: either that network's entry or the exchange's export is wrong. Ask the exchange which.

    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/136181/: 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.