ixreport

GlobalEdge

AS136181

3Exchanges
3On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
2Using the route servers
4To fix in PeeringDB

This network has no PeeringDB record; it was found on exchanges' own member lists.

Tools: Where can I peer with GlobalEdge? · Where should GlobalEdge peer next? · Compare GlobalEdge with another network

This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

4 things to fix in GlobalEdge's PeeringDB record, from what its exchanges publish: 3 to add, 1 to correct. As of 2026-11-19 12:40 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 (1)

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.

Exchanges over time

0123Oct 3, 2026Nov 19, 20263
Show as a table
DateExchanges
Nov 19, 20263
Nov 18, 20263
Nov 17, 20263
Nov 16, 20263
Nov 15, 20263
Nov 14, 20263
Nov 13, 20263
Nov 12, 20263
Nov 11, 20263
Nov 10, 20263
Nov 9, 20263
Nov 8, 20263
Nov 7, 20263
Nov 6, 20263
Nov 5, 20263
Nov 4, 20263
Nov 3, 20263
Nov 2, 20263
Nov 1, 20263
Oct 31, 20263
Oct 30, 20263
Oct 29, 20263
Oct 28, 20263
Oct 27, 20263
Oct 26, 20263
Oct 25, 20263
Oct 24, 20263
Oct 23, 20263
Oct 22, 20263
Oct 21, 20263
Oct 20, 20263
Oct 19, 20263
Oct 18, 20263
Oct 17, 20263
Oct 16, 20263
Oct 15, 20263
Oct 14, 20263
Oct 13, 20263
Oct 12, 20263
Oct 11, 20263
Oct 10, 20263
Oct 9, 20263
Oct 8, 20263
Oct 7, 20263
Oct 6, 20263
Oct 5, 20263
Oct 4, 20263
Oct 3, 20263

Map

Where GlobalEdge's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.

Exchanges

Australia MegaIX Melbourne Melbourne, Australia 103.26.71.27 2001:dea:0:30::1b Yes Not in PeeringDB
Australia MegaIX Perth Perth, Australia 202.12.243.59 2001:dea:0:50::3b Not in PeeringDB Address taken
Australia MegaIX Sydney Sydney, Australia 103.26.68.146 2001:dea:0:10::92 Yes Not in PeeringDB