ixreport

MegaIX Miami

Megaport MegaIX Miami

Miami, United States · North America

Operated by Megaport · 8 ghost exchanges

Who's on MegaIX Miami, by source

9 of 11 match: 9 in every source1 published by the exchange, not in PeeringDB1 in PeeringDB, not on the exchange's own lists

IX-F export: https://lg.megaport.com/megaport.json, read 2026-11-19 12:22 UTC.

Ports and fees

PortPriceBilled In useAs the page says it
100M –– 1
10G –– 3
100G –– 5

Every port speed MegaIX Miami lists (we haven't found its price list), plus every speed members are connected at (from PeeringDB).

We couldn't find MegaIX Miami's port fees on its website.

How members connect

In its IX-F export
0 by tunnel, 0 on a physical port, 10 not given
Facilities it lists
4 in PeeringDB
Members with a building in United States
9 of the 10 members that list any building in PeeringDB (11 members in all)
Members' countries
7 (where their organizations are, in PeeringDB)

How a Virtual IX is decided

Members over time

IX-FPeeringDB
0246810Oct 2, 2026Nov 19, 202610
Show as a table
DateIX-FPeeringDB
Nov 19, 20261010
Nov 18, 20261010
Nov 17, 20261010
Nov 16, 20261010
Nov 15, 20261010
Nov 14, 20261010
Nov 13, 20261010
Nov 12, 20261010
Nov 11, 20261010
Nov 10, 20261010
Nov 9, 20261010
Nov 8, 20261010
Nov 7, 20261010
Nov 6, 20261010
Nov 5, 20261010
Nov 4, 20261010
Nov 3, 20261010
Nov 2, 20261010
Nov 1, 20261010
Oct 31, 20261010
Oct 30, 20261010
Oct 29, 20261010
Oct 28, 20261010
Oct 27, 20261010
Oct 26, 20261010
Oct 25, 20261010
Oct 24, 20261010
Oct 23, 20261010
Oct 22, 20261010
Oct 21, 20261010
Oct 20, 20261010
Oct 19, 20261010
Oct 18, 20261010
Oct 17, 20261010
Oct 16, 20261010
Oct 15, 20261010
Oct 14, 20261010
Oct 13, 20261010
Oct 12, 20261010
Oct 11, 20261010
Oct 10, 20261010
Oct 9, 20261010
Oct 8, 20261010
Oct 7, 20261010
Oct 6, 20261010
Oct 5, 20261010
Oct 4, 20261010
Oct 3, 20261010
Oct 2, 2026–10

Exchange details

Media
Ethernet
Protocols
Unicast IPv4, IPv6
MTU
1500
Traffic stats
www.megaport.com/services/ix-statistics/
Technical
support@megaport.com
Policy
ix@megaport.com
Sales
ix@megaport.com
PeeringDB record
Updated 2024-01-18

Peering LAN prefixes

  • 206.53.168.0/26IPv4
  • 2606:a980:0:b::/64IPv6

Facilities (4)

Data status

What the last update (every 6 hours) found for MegaIX Miami, step by step.

  1. IX-F export in PeeringDB The exchange hasn't published an IX-F export URL in PeeringDB.
  2. IX-F database (IXPDB) https://lg.megaport.com/megaport.json
  3. Website search No member list found on the website (checked 2026-11-16).
  4. Member list Read 2026-11-19 12:22 UTC from the IX-F export.
  5. Port fees No fees page found on the exchange's website yet (searched weekly).
  6. Route server looking glass No public route server looking glass found: the exchange's IX-F export names none, and it isn't on one of the shared looking glasses this site reads (DE-CIX, LINX, AMS-IX, IX.br, Netnod, BCIX).

Embed this badge

MegaIX Miami on IX Report

For MegaIX Miami's website, a wiki or a README: it links back to this page and updates with the site, every 6 hours. The share is of the networks on MegaIX Miami's own member lists that PeeringDB lists here; it's left off when there's no list to compare. This page's data is also available as JSON: /api/ix/4362.json (about the API).

HTML
<a href="https://ixreport.com/ix/4362/"><img src="https://ixreport.com/ix/4362/badge.svg" alt="MegaIX Miami on IX Report" height="20"></a>
Markdown
[![MegaIX Miami on IX Report](https://ixreport.com/ix/4362/badge.svg)](https://ixreport.com/ix/4362/)

Fix list

Networks where PeeringDB and what MegaIX Miami publishes (its IX-F export and its website's members list) disagree. Download CSV Operator report with contacts

Published by the exchange, missing from PeeringDB (1)

These networks could add MegaIX Miami to their PeeringDB record.

Only in PeeringDB (1)

Either the exchange's lists are missing them, or their PeeringDB record is out of date.

Addresses and port speeds

Each network's IP addresses and port speed in PeeringDB, against MegaIX Miami's IX-F export, for the 9 networks in both. They all match.

The export doesn't list port speeds, so it isn't compared.

11 networks

AS42 PCH AS42 206.53.168.10 2606:a980:0:b::a PeeringDB IX-F
AS4826 Vocus CommunicationsExchange lists it as “Vocus” 206.53.168.12 2606:a980:0:b::c 10G Yes PeeringDB IX-F
AS6939 Hurricane Electric 206.53.168.6 2606:a980:0:b::6 100G Yes PeeringDB IX-F
AS11767 QTS MiamiExchange lists it as “QTS” 206.53.168.16 2606:a980:0:b::10 Yes PeeringDB IX-FNot in PeeringDB
AS16276 OVHcloudExchange lists it as “OVH SAS” 206.53.168.14 2606:a980:0:b::e 100G Yes PeeringDB IX-F
AS37468 Angola Cables 206.53.168.11 2606:a980:0:b::b Yes PeeringDB IX-F
AS49915 Megaport Global AccessExchange lists it as “Networks” 206.53.168.7
206.53.168.8
2606:a980:0:b::7
2606:a980:0:b::8
2 × 100G Yes PeeringDB IX-F
AS64220 MegaIX North America Route ServersExchange lists it as “MEGAPORT” 206.53.168.1
206.53.168.2
2606:a980:0:b::1
2606:a980:0:b::2
2 × 10G PeeringDB IX-F
AS139341 ACE CDNExchange lists it as “Kite Bird Germany GmbH” 206.53.168.15 2606:a980:0:b::f Yes PeeringDB IX-F
AS212232 BGP.Tools Route CollectorExchange lists it as “bgp.tools / Port 179 Ltd” 206.53.168.9 2606:a980:0:b::9 100M Yes PeeringDB IX-F
AS262287 Latitude.sh AS262287Exchange lists it as “Latitude.sh” 206.53.168.13 2606:a980:0:b::d 100G Yes PeeringDB IX-F