ixreport

Brisbane City Council

AS18255 · BCC

3Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
–Type
RestrictivePeering policy
2Using the route servers
3To fix in PeeringDB
0Facilities in PeeringDB

Tools: Where can I peer with Brisbane City Council? · Where should Brisbane City Council peer next? · Compare Brisbane City Council with another network

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

3 things to fix in Brisbane City Council's PeeringDB record, from what its exchanges publish: 3 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on Brisbane City Council's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

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. Australia MegaIX Brisbane Brisbane, Australia · PeeringDB 781
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:dea:0:20::48
    • In the entry with IPv4 103.26.70.72: set IPv6 to 2001:dea:0:20::48 (now empty).

    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 Melbourne Melbourne, Australia · PeeringDB 779
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:dea:0:30::6e
    • In the entry with IPv4 103.26.71.110: set IPv6 to 2001:dea:0:30::6e (now empty).

    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 780
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:dea:0:10::14 2001:dea:0:10::12f
    • In the entry with IPv4 103.26.68.20: set IPv6 to 2001:dea:0:10::14 (now empty).
    • In the entry with IPv4 103.26.69.47: set IPv6 to 2001:dea:0:10::12f (now empty).

    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 Brisbane City Council'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

Total port capacity 40G across 3 exchanges.

Australia MegaIX Brisbane Brisbane, Australia 103.26.70.72 10G Yes Both IPv6 not in PeeringDB
Australia MegaIX Melbourne Melbourne, Australia 103.26.71.110 10G Yes Both IPv6 not in PeeringDB
Australia MegaIX Sydney Sydney, Australia 103.26.68.20
103.26.69.47
2 × 10G Both IPv6 not in PeeringDB

Brisbane City Council lists no facilities in PeeringDB.