ixreport

POLOPRO

AS208824

11Exchanges, of which 1 VIX
1On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
NSPType
OpenPeering policy
11Using the route servers
2To fix in PeeringDB
3Facilities in PeeringDB

Tools: Where can I peer with POLOPRO? · Where should POLOPRO peer next? · Compare POLOPRO with another network

This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

2 things to fix in POLOPRO's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct. As of 2026-11-19 18:41 UTC.

Make the changes on POLOPRO's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Add these exchanges (1)

On the exchange's own member list, but not in POLOPRO's PeeringDB record. Add one entry per connection with these values.

  1. Switzerland FogIXP Avers, Switzerland · PeeringDB 3756From its IX-F export and website members list
    IPv4–
    IPv62001:7f8:ca:1:0:20:8824:1
    Speed1000 Mbps (1G)
    RS peerYes

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

Correct these entries (1)

Addresses or port speeds in PeeringDB that differ from the exchange's IX-F export. The changes below follow the export; if the export is the one that's wrong, tell the exchange instead.

  1. Canada ONIX Toronto, Canada · PeeringDB 4059
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDBnone149.112.50.132
    • In the entry with IPv6 2001:504:125:e1::aaec: set IPv4 to 149.112.50.132 (now empty).

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

Exchanges over time

051015Oct 3, 2026Nov 19, 202611
Show as a table
DateExchanges
Nov 19, 202611
Nov 18, 202611
Nov 17, 202611
Nov 16, 202611
Nov 15, 202611
Nov 14, 202611
Nov 13, 202611
Nov 12, 202611
Nov 11, 202611
Nov 10, 202611
Nov 9, 202611
Nov 8, 202611
Nov 7, 202611
Nov 6, 202611
Nov 5, 202611
Nov 4, 202611
Nov 3, 202611
Nov 2, 202611
Nov 1, 202611
Oct 31, 202611
Oct 30, 202611
Oct 29, 202611
Oct 28, 202611
Oct 27, 202611
Oct 26, 202611
Oct 25, 202610
Oct 24, 202610
Oct 23, 202610
Oct 22, 202610
Oct 21, 202610
Oct 20, 202611
Oct 19, 202611
Oct 18, 202611
Oct 17, 202611
Oct 16, 202611
Oct 15, 202611
Oct 14, 202611
Oct 13, 202611
Oct 12, 202611
Oct 11, 202611
Oct 10, 202611
Oct 9, 202611
Oct 8, 202611
Oct 7, 202611
Oct 6, 202611
Oct 5, 202611
Oct 4, 202611
Oct 3, 202611

Map

Where POLOPRO's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.

Exchanges

Total port capacity 9.1G, at the 10 of 11 exchanges with a speed in PeeringDB or the exchange's IX-F export.

Switzerland 4b42 Internet Exchange Point Zurich, Switzerland 2001:7f8:d0::3:2fb8:1 1G Yes Both
Spain Barcelona-IX Barcelona, Spain 2001:7f8:93:1:0:20:8824:1 1G Yes Both
Switzerland FogIXP Avers, Switzerland 2001:7f8:ca:1::20:8824:1 1G Yes Not in PeeringDB
United States HN Internet Exchange (Main)VIX North Kansas City, United States 2a0f:85c1:363:1:20:8824:0:1 100M Yes PeeringDB
Netherlands INTERIX Amsterdam, Netherlands 185.1.184.153 2001:7f8:134::8f 3 routes Both
Netherlands ixFabric - Amsterdam Amsterdam, Netherlands 2a0e:8f01:1000:11::1bf 1G Yes PeeringDB
Switzerland ixFabric - Zurich Zurich, Switzerland 2a0e:8f01:1000:25::156 1G Yes PeeringDB
Canada ONIX Toronto, Canada 2001:504:125:e1::aaec 1G Yes Both IPv4 not in PeeringDB
Netherlands PeersIX Amsterdam Amsterdam, Netherlands 2a0a:6044:a1ff::29 1G Yes PeeringDB
United States Zero Internet eXchange San Jose San Jose, United States 2a13:b487:3200::20:8824:1 1G Yes PeeringDB
Hong Kong ZXIX Hong Kong Hong Kong, Hong Kong 2406:840:1f:1000:0:20:8824:1 1G Yes PeeringDB

Exchanges in its buildings that it isn't on (19)

These exchanges have a switch in a facility where POLOPRO lists itself in PeeringDB, but don't have POLOPRO as a member in PeeringDB, their IX-F export or their website. Joining one is usually just a cross-connect away. The biggest exchanges come first; ghost exchanges are left out.

Canada TorIXToronto, Canada 251 Equinix TR2 - Toronto
United States EVIXFremont, United States 227 Hurricane Electric Fremont 2
Bulgaria NetIXSofia, Bulgaria 204 Equinix TR2 - Toronto
United States FCIXFremont, United States 187 Hurricane Electric Fremont 2
United States FREMIXFremont, United States 141 Hurricane Electric Fremont 2
United States SFMIXSan Francisco, United States 100 Hurricane Electric Fremont 2
Spain CATNIXBarcelona, Spain 55 Templus DC Barcelona BCN01
Spain ixFabric - BarcelonaBarcelona, Spain 52 Templus DC Barcelona BCN01
Spain DE-CIX BarcelonaBarcelona, Spain 47 Templus DC Barcelona BCN01
Puerto Rico PR-IXSan Juan, Puerto Rico 33 Hurricane Electric Fremont 2
United States ARIXFremont, Portland, Flagstaff, United States 22 Hurricane Electric Fremont 2
United States Lambda-IXFremont, United States 22 Hurricane Electric Fremont 2
United States MegaIX Bay AreaSan Francisco, United States 21 Hurricane Electric Fremont 2
Canada Equinix TorontoToronto, Canada 16 Equinix TR2 - Toronto
Canada MegaIX TorontoToronto, Canada 16 Equinix TR2 - Toronto
United States DACS-IX WestSilicon Valley, United States 14 Hurricane Electric Fremont 2
United States Global Peer ExchangeWashington, United States 6 Templus DC Barcelona BCN01
United States Ninja-IX Bay AreaNorthern California, United States 6 Hurricane Electric Fremont 2
Australia ixFabricGlobal, Australia 2 Hurricane Electric Fremont 2; Equinix TR2 - Toronto
Facilities (3)

The buildings POLOPRO lists in PeeringDB, and how many of the exchanges in each it's on.

United States Hurricane Electric Fremont 2Fremont 1 of 12
Canada Equinix TR2 - TorontoToronto 1 of 6
Spain Templus DC Barcelona BCN01L'Hospitalet de Llobregat 1 of 5