ixreport

MegaIX Chicago

Chicago, United States · North America

Operated by Megaport · 8 ghost exchanges

Who's on MegaIX Chicago, by source

12 of 13 match: 12 in every source1 published by the exchange, not in PeeringDB

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 –– 5
100G –– 7

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

We couldn't find MegaIX Chicago'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
17 in PeeringDB
Members with a building in United States
10 of the 11 members that list any building in PeeringDB (13 members in all)
Members' countries
5 (where their organizations are, in PeeringDB)

How a Virtual IX is decided

Members over time

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

Exchange details

Media
Ethernet
Protocols
Unicast IPv4, IPv6
MTU
1500
Service level
24/7 Support
Traffic stats
megaport.com
Technical
support@megaport.com
Policy
ix@megaport.com
Sales
ix@megaport.com
PeeringDB record
Updated 2025-05-22

Peering LAN prefixes

  • 206.53.206.0/25IPv4
  • 2606:a980:0:d::/64IPv6

Facilities (17)

Scroll for all 17 facilities

Data status

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

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

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

Fix list

Networks where PeeringDB and what MegaIX Chicago 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 Chicago to their PeeringDB record.

Only in PeeringDB (0)

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

  • None

Addresses and port speeds

Each network's IP addresses and port speed in PeeringDB, against MegaIX Chicago's IX-F export, for the 12 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 Chicago. PeeringDB suggests these corrections to the networks (and makes them for networks that allow it).

IPv6 address missing from PeeringDB (1)
AS395505 iManage none 2606:a980:0:d::d

13 networks

AS4826 Vocus CommunicationsExchange lists it as “Vocus” 206.53.206.11 2606:a980:0:d::b 10G Yes PeeringDB IX-F
AS6939 Hurricane Electric 206.53.206.9 2606:a980:0:d::9 100G Yes PeeringDB IX-F
AS16276 OVHcloudExchange lists it as “OVH SAS” 206.53.206.20 2606:a980:0:d::14 100G Yes PeeringDB IX-F
AS16524 MetTel 206.53.206.17 2606:a980:0:d::11 2G Yes PeeringDB IX-F
AS17378 TierPoint LLC 206.53.206.12 2606:a980:0:d::c 10G Yes PeeringDB IX-F
AS32899 Bresco Broadband 206.53.206.16 2606:a980:0:d::10 Yes PeeringDB IX-F
AS32934 MetaExchange lists it as “Edge Network Services Limited” 206.53.206.18
206.53.206.19
2606:a980:0:d::12
2606:a980:0:d::13
2 × 100G PeeringDB IX-F
AS49915 Megaport Global AccessExchange lists it as “Networks” 206.53.206.6
206.53.206.7
2606:a980:0:d::6
2606:a980:0:d::7
2 × 100G Yes PeeringDB IX-F
AS64214 MegaIX Chicago Route ServersExchange lists it as “MEGAPORT” 206.53.206.1
206.53.206.2
2606:a980:0:d::1
2606:a980:0:d::2
2 × 10G PeeringDB IX-F
AS212232 BGP.Tools Route CollectorExchange lists it as “bgp.tools / Port 179 Ltd” 206.53.206.8 2606:a980:0:d::8 100M Yes PeeringDB IX-F
AS262287 Latitude.sh AS262287Exchange lists it as “Latitude.sh” 206.53.206.10
206.53.206.15
206.53.206.21
206.53.206.22
2606:a980:0:d::a
2606:a980:0:d::f
2606:a980:0:d::15
2606:a980:0:d::16
100G Yes PeeringDB IX-F
AS394968 QTS ChicagoExchange lists it as “QTS” 206.53.206.14 2606:a980:0:d::e Yes PeeringDB IX-FNot in PeeringDB
AS395505 iManageExchange lists it as “iManage Cloud” 206.53.206.13 10G Yes PeeringDB IX-F