ixreport

Any2Denver: operator report

Denver, United States · PeeringDB 254 · ixreport.com/ix/254/report/

Download CSV

Members of Any2Denver that PeeringDB has wrong, from its website members list (72 networks, read 2026-10-08 22:05 UTC), against PeeringDB as of 2026-10-08 22:13 UTC. 8 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 (3)

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

NetworkOn yourAddressesContact
AS4436 GTT Communications (AS4436) PeeringDBwebsite 206.51.46.150
2605:6c00:303:303::150
No public contact
AS62887 Whitesky Communications AS62887 PeeringDBwebsite 206.51.46.126
2605:6c00:303:303::126
NOC: email address (needs JavaScript) +18667558593
AS397301 THRIVE BROADBAND PeeringDBwebsite 206.51.46.96
2605:6c00:303:303::96
No public contact

Addresses or port speeds that differ (0)

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

In PeeringDB, not on your lists (5)

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.46.244
206.51.46.245
2605:6c00:303:303::244
2605:6c00:303:303::245
2 × 100G
No public contact
AS14701 Faction Inc. PeeringDB 206.51.46.16
2605:6c00:303:303::16
10G
No public contact
AS30688 FastTrack Communications PeeringDB 206.51.46.129
2605:6c00:303:303::129
100G
No public contact
AS32184 Any2 Route Servers PeeringDB 206.51.46.64
206.51.46.65
2605:6c00:303:303::64
2605:6c00:303:303::65
2 × 10G
No public contact
AS32261 Subspace PeeringDB 206.51.46.123
2605:6c00:303:303::123
10G
No public contact