ixreport

FLIP

AS133898 · Flip

FLIP TV PTY LIMITED

4Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Cable/DSL/ISPType
OpenPeering policy
4Using the route servers
1To fix in PeeringDB
2Facilities in PeeringDB

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

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

PeeringDB fix list Printable page · CSV

One thing to fix in FLIP's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-11-19 12:40 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.

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. ProblemPeeringDB hasThe export has
    Port speed differs20G10G
    • In the entry with IPv4 218.100.78.72: set Speed to 10000 (10G) (now 20000).

    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

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

Map

Where FLIP'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 70G across 4 exchanges.

Australia IX Australia Melbourne (VIC-IX) Melbourne, Australia 218.100.78.72 2001:7fa:11:1:2:b0a:0:1 20G Yes Both Speed differs
Australia IX Australia Sydney (NSW-IX) Sydney, Australia 218.100.53.72 2001:7fa:11:4:2:e37:0:1 20G Yes Both
Australia MegaIX Melbourne Melbourne, Australia 103.26.71.52 2001:dea:0:30::34 10G Yes Both
Australia MegaIX Sydney Sydney, Australia 103.26.69.119 2001:dea:0:10::177 20G Yes Both

Exchanges in its buildings that it isn't on (5)

These exchanges have a switch in a facility where FLIP lists itself in PeeringDB, but don't have FLIP as a member in PeeringDB, their IX-F export or their website. Joining one is usually just a cross-connect away. The biggest exchanges come first; ghost exchanges are left out.

Australia EdgeIX - SydneySydney, Australia 230 Equinix SY3 - Sydney
Australia Equinix SydneySydney, Australia 219 Equinix SY3 - Sydney
Bulgaria NetIXSofia, Bulgaria 204 Equinix SY3 - Sydney
Australia EdgeIX - MelbourneMelbourne, Australia 73 NEXTDC M1
Australia ixFabricGlobal, Australia 2 Equinix SY3 - Sydney
Facilities (2)

The buildings FLIP lists in PeeringDB, and how many of the exchanges in each it's on.

Australia Equinix SY3 - SydneySydney 2 of 6
Australia NEXTDC M1Melbourne 2 of 3

Recent changes Search them

  • Nov 18, 2026 [PDB] AS133898 FLIP now in PeeringDB at MegaIX Melbourne
  • Nov 18, 2026 [PDB] AS133898 FLIP now in PeeringDB at MegaIX Sydney
  • Oct 14, 2026 [PDB] AS133898 FLIP now in PeeringDB at IX Australia Melbourne (VIC-IX)
  • Oct 14, 2026 [PDB] AS133898 FLIP now in PeeringDB at IX Australia Sydney (NSW-IX)