ixreport

MegaIX Atlanta

Megaport MegaIX Atlanta

Atlanta, United States · North America

Operated by Megaport · 8 ghost exchanges

Who's on MegaIX Atlanta, by source

10 of 12 match: 10 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 –– 6
100G –– 4

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

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

How members connect

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

How a Virtual IX is decided

Members over time

IX-FPeeringDB
051015Oct 2, 2026Nov 19, 202611
Show as a table
DateIX-FPeeringDB
Nov 19, 20261111
Nov 18, 20261111
Nov 17, 20261111
Nov 16, 20261111
Nov 15, 20261111
Nov 14, 20261111
Nov 13, 20261111
Nov 12, 20261111
Nov 11, 20261111
Nov 10, 20261111
Nov 9, 20261111
Nov 8, 20261111
Nov 7, 20261111
Nov 6, 20261111
Nov 5, 20261111
Nov 4, 20261111
Nov 3, 20261111
Nov 2, 20261111
Nov 1, 20261111
Oct 31, 20261111
Oct 30, 20261111
Oct 29, 20261111
Oct 28, 20261111
Oct 27, 20261111
Oct 26, 20261111
Oct 25, 20261111
Oct 24, 20261111
Oct 23, 20261111
Oct 22, 20261111
Oct 21, 20261111
Oct 20, 20261111
Oct 19, 20261111
Oct 18, 20261111
Oct 17, 20261111
Oct 16, 20261111
Oct 15, 20261111
Oct 14, 20261111
Oct 13, 20261111
Oct 12, 20261111
Oct 11, 20261111
Oct 10, 20261111
Oct 9, 20261111
Oct 8, 20261111
Oct 7, 20261111
Oct 6, 20261111
Oct 5, 20261111
Oct 4, 20261110
Oct 3, 20261110
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.169.128/26IPv4
  • 2606:a980:0:a::/64IPv6

Facilities (13)

Scroll for all 13 facilities

Data status

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

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

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

Fix list

Networks where PeeringDB and what MegaIX Atlanta 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 Atlanta 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 Atlanta's IX-F export, for the 10 networks in both. They all match.

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

Recent changes Search them

12 networks

AS42 PCH AS42 206.53.169.139 2606:a980:0:a::b PeeringDB IX-F
AS4213 Evocative GlobalExchange lists it as “Evocative_Internal” 206.53.169.143 2606:a980:0:a::f 30G Yes PeeringDB IX-F
AS4826 Vocus CommunicationsExchange lists it as “Vocus” 206.53.169.144 2606:a980:0:a::10 10G Yes PeeringDB IX-F
AS6939 Hurricane Electric 206.53.169.135 2606:a980:0:a::7 100G Yes PeeringDB IX-F
AS14127 11:11 Systems 206.53.169.134 2606:a980:0:a::6 10G Yes PeeringDB IX-F
AS16276 OVHcloudExchange lists it as “OVH SAS” 206.53.169.145 2606:a980:0:a::11 100G Yes PeeringDB IX-F
AS20141 QTS Atlanta-SuwaneeExchange lists it as “QTS” 206.53.169.142 2606:a980:0:a::e Yes PeeringDB IX-FNot in PeeringDB
AS40805 JMF Networks 206.53.169.140 2606:a980:0:a::c 10G Yes PeeringDB IX-F
AS49544 i3D.net 206.53.169.141 2606:a980:0:a::d 10G Yes PeeringDB IX-F
AS49915 Megaport Global AccessExchange lists it as “Networks” 206.53.169.136
206.53.169.137
2606:a980:0:a::8
2606:a980:0:a::9
2 × 100G Yes PeeringDB IX-F
AS64220 MegaIX North America Route ServersExchange lists it as “MEGAPORT” 206.53.169.129
206.53.169.130
2606:a980:0:a::1
2606:a980:0:a::2
2 × 10G PeeringDB IX-F
AS212232 BGP.Tools Route CollectorExchange lists it as “bgp.tools / Port 179 Ltd” 206.53.169.138 2606:a980:0:a::a 100M Yes PeeringDB IX-F