ixreport

Any2Chicago: operator report

Chicago, United States · PeeringDB 226 · ixreport.com/ix/226/report/

Download CSV

Members of Any2Chicago that PeeringDB has wrong, from its website members list (17 networks, read 2026-10-08 18:46 UTC), against PeeringDB as of 2026-10-08 18:53 UTC. 6 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 (3)

These networks could add Any2Chicago to their PeeringDB record. Networks with no PeeringDB record would need to create one first.

NetworkOn yourAddressesContact
AS11414 NVIDIA Corporation PeeringDBwebsite 206.51.43.30
206.51.43.31
2001:504:13:4::30
2001:504:13:4::31
No public contact
AS15169 Google LLC PeeringDBwebsite 206.51.43.14
206.51.43.21
2001:504:13:4::14
2001:504:13:4::21
No public contact
AS22697 ROBLOX PeeringDBwebsite 206.51.43.34
2001:504:13:4::34
No public contact

Addresses or port speeds that differ (0)

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

In PeeringDB, not on your lists (3)

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

NetworkIn PeeringDBContact
AS2734 CoreSite PeeringDB 206.51.43.244
206.51.43.245
2001:504:13:4::244
2001:504:13:4::245
2 × 100G
No public contact
AS32184 Any2 Route Servers PeeringDB 206.51.43.252
206.51.43.253
2001:504:13:4::252
2001:504:13:4::253
2 × 10G
No public contact
AS49915 Megaport Global Access PeeringDB 206.51.43.43
2001:504:13:4::43
100G
No public contact