MegaIX New York: operator report

New York, United States · PeeringDB 4318 · ixreport.com/ix/4318/report/

Download CSV

Members of MegaIX New York that PeeringDB has wrong, from its IX-F export (22 networks, read 2026-10-08 20:54 UTC), against PeeringDB as of 2026-10-08 20:58 UTC. 5 networks to follow up.

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 New York to their PeeringDB record. Networks with no PeeringDB record would need to create one first.

NetworkOn yourAddressesContact
AS4136 QTS New Jersey PeeringDBIX-F 206.53.173.21
2606:a980:0:2::15
No public contact
AS11403 NYI PeeringDBIX-F 206.53.173.16
2606:a980:0:2::10
No public contact

Addresses or port speeds that differ (1)

PeeringDB against your IX-F export, for the 20 networks in both. Either the network's PeeringDB record or the export is out of date.

NetworkProblemPeeringDB hasYour export hasContact
AS43009 INFOBIP PeeringDB IPv6 address missing from PeeringDBnone2606:a980:0:2::14 No public contact

In PeeringDB, not on your lists (2)

Either your lists are missing these networks, or they've left and their PeeringDB record is out of date.

NetworkIn PeeringDBContact
AS42 PCH AS42 PeeringDB 206.53.173.17
2606:a980:0:2::11
No public contact
AS30081 CacheFly PeeringDB 206.53.173.6
2606:a980:0:2::6
No public contact