Any2Florida: operator report

Miami/Orlando, United States · PeeringDB 205 · ixreport.com/ix/205/report/

Download CSV

Members of Any2Florida that PeeringDB has wrong, from its website members list (2 networks, read 2026-10-08 20:54 UTC), against PeeringDB as of 2026-10-08 20:58 UTC. 2 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 Any2Florida to their PeeringDB record. Networks with no PeeringDB record would need to create one first.

NetworkOn yourAddressesContact
AS21777 Massive Networks PeeringDBwebsite 206.51.40.117
2001:504:13:1::117		 No public contact
AS55016 Imperium PeeringDBwebsite 206.51.44.3
2001:504:13:5::3		 No public contact

Addresses or port speeds that differ (0)

Any2Florida publishes no IX-F export we could read, so addresses and port speeds can't be compared.

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.