ixreport

The Cloud Provider

AS209369 · TCPro

2Exchanges
0On an exchange's list, not in PeeringDB
1In PeeringDB, not on the exchange's list
–Type
OpenPeering policy
2Using the route servers
1To fix in PeeringDB
2Facilities in PeeringDB

Tools: Where can I peer with The Cloud Provider? · Where should The Cloud Provider peer next? · Compare The Cloud Provider with another network

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

PeeringDB fix list Printable page · CSV

One thing to fix in The Cloud Provider's PeeringDB record, from what its exchanges publish: 1 to check. As of 2026-11-19 12:40 UTC.

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

Check these entries (1)

In PeeringDB, but on none of the exchange's own lists. If The Cloud Provider has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. Czechia Peering.cz Prague, Bratislava, Vienna, Frankfurt, Czechia · PeeringDB 713Not on its IX-F export or website members list
    IPv4185.0.20.79
    IPv62001:7f8:7f::79
    Speed10000 Mbps (10G)

Exchanges over time

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

Map

Where The Cloud Provider'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 11G across 2 exchanges.

Czechia NIX.CZ Prague, Czechia 91.210.16.217 2001:7f8:14::27:1 1G Yes Both
Czechia Peering.cz Prague, Bratislava, Vienna, Frankfurt, Czechia 185.0.20.79 2001:7f8:7f::79 10G Yes PeeringDB only

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

These exchanges have a switch in a facility where The Cloud Provider lists itself in PeeringDB, but don't have The Cloud Provider 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.

Czechia NIX.CZ FENIXPrague, Czechia 8 TTC TELEPORT DC1; TTC TELEPORT DC2
Facilities (2)

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

Czechia TTC TELEPORT DC1Prague 2 of 3
Czechia TTC TELEPORT DC2Prague 2 of 3