MegaIX Dallas: operator report
Dallas, United States · PeeringDB 1180 · ixreport.com/ix/1180/report/
Members of MegaIX Dallas that PeeringDB has wrong, from its IX-F export (30 networks, read 2026-10-08 20:54 UTC), against PeeringDB as of 2026-10-08 20:58 UTC. 3 networks to follow up; 1 with a public PeeringDB contact.
Contacts are the networks' public PeeringDB contacts: the peering (policy) contact where there is one, else technical, then NOC. Networks keep these themselves on PeeringDB.
On your lists, missing from PeeringDB (2)
These networks could add MegaIX Dallas to their PeeringDB record. Networks with no PeeringDB record would need to create one first.
| Network | On your | Addresses | Contact |
|---|---|---|---|
| AS15164 Unite | IX-F | 206.53.174.22 2606:a980:0:7::16 |
NOC: email address (needs JavaScript) +18334673472 |
| AS46746 Secure-24 | IX-F | 206.53.174.28 2606:a980:0:7::1c |
No public contact |
Addresses or port speeds that differ (1)
PeeringDB against your IX-F export, for the 28 networks in both. Either the network's PeeringDB record or the export is out of date.
| Network | Problem | PeeringDB has | Your export has | Contact |
|---|---|---|---|---|
| AS40731 Latin IP LLC | IPv6 address missing from PeeringDB | none | 2606:a980:0:7::6 | No public contact |
| IPv4 address in PeeringDB, not in the export | 206.53.174.6 206.53.174.15 | 206.53.174.6 |
In PeeringDB, not on your lists (0)
Either your lists are missing these networks, or they've left and their PeeringDB record is out of date.
None.