ixreport

MegaIX Seattle

Megaport MegaIX Seattle

Seattle, United States · North America

Operated by Megaport · 8 ghost exchanges

Who's on MegaIX Seattle, by source

13 of 15 match: 13 in every source2 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
1G –– 1
10G –– 11
100G –– 3

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

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

How members connect

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

How a Virtual IX is decided

Members over time

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

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
PeeringDB record
Updated 2023-07-09

Peering LAN prefixes

  • 206.53.171.0/24IPv4
  • 2606:a980:0:4::/64IPv6

Facilities (8)

Data status

What the last update (every 6 hours) found for MegaIX Seattle, 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 Seattle on IX Report

For MegaIX Seattle'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 Seattle'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/1174.json (about the API).

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

Fix list

Networks where PeeringDB and what MegaIX Seattle 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 (0)

These networks could add MegaIX Seattle to their PeeringDB record.

  • None

Only in PeeringDB (2)

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 Seattle's IX-F export, for the 13 networks in both. 1 has differences. Download CSV Operator report with contacts

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

PeeringDB's IX-F import is on for MegaIX Seattle. PeeringDB suggests these corrections to the networks (and makes them for networks that allow it).

IPv6 address missing from PeeringDB (1)
AS58580 Fastrack Technology none 2606:a980:0:4::12

Recent changes Search them

15 networks

AS42 PCH AS42 206.53.171.14 2606:a980:0:4::e 10G PeeringDB IX-F
AS3856 PCH AS3856 206.53.171.15 2606:a980:0:4::f 1G PeeringDB IX-F
AS4213 Evocative GlobalExchange lists it as “Evocative_Internal” 206.53.171.9 2606:a980:0:4::9 10G Yes PeeringDB IX-F
AS4826 Vocus CommunicationsExchange lists it as “Vocus” 206.53.171.21 2606:a980:0:4::15 20G Yes PeeringDB IX-F
AS6939 Hurricane Electric 206.53.171.11 2606:a980:0:4::b 10G PeeringDB IX-F
AS7575 AARNet 206.53.171.12 2606:a980:0:4::c 10G Yes PeeringDB IX-F
AS13335 CloudflareExchange lists it as “Cloudflare Inc.” 206.53.171.7 2606:a980:0:4::7 10G Yes PeeringDB IX-F
AS16276 OVHcloudExchange lists it as “OVH SAS” 206.53.171.17 2606:a980:0:4::11 100G Yes PeeringDB IX-F
AS17378 TierPoint LLC 206.53.171.20 2606:a980:0:4::14 10G Yes PeeringDB IX-F
AS49544 i3D.net 206.53.171.6 2606:a980:0:4::6 10G Yes PeeringDB IX-F
AS49915 Megaport Global AccessExchange lists it as “Networks” 206.53.171.22
206.53.171.23
2606:a980:0:4::16
2606:a980:0:4::17
2 × 100G Yes PeeringDB IX-F
AS58580 Fastrack Technology 206.53.171.18 10G Yes PeeringDB IX-F
AS64219 MegaIX Seattle Route ServersExchange lists it as “MEGAPORT” 206.53.171.1
206.53.171.2
2606:a980:0:4::1
2606:a980:0:4::2
2 × 10G PeeringDB IX-F
AS151332 CoinJar 206.53.171.10 2606:a980:0:4::a 10G Yes PeeringDB IX-F
AS212232 BGP.Tools Route CollectorExchange lists it as “bgp.tools / Port 179 Ltd” 206.53.171.24 2606:a980:0:4::18 100M Yes PeeringDB IX-F