CC INTERNET
AS202921 · CC INTERNET
CC INTERNET s.r.o.
Tools: Where can I peer with CC INTERNET? · Where should CC INTERNET peer next? · Compare CC INTERNET 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 CC INTERNET's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct. As of 2026-11-19 12:40 UTC.
Make the changes on CC INTERNET'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 CC INTERNET's PeeringDB record. Add one entry per connection with these values.
-
IPv4 91.210.16.237 IPv6 2001:7f8:14::72:1 Speed 25000 Mbps (25G) RS peer Yes 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.
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB 185.0.20.60 185.0.20.60 185.0.21.60 IPv6 address missing from PeeringDB none 2001:7f8:7f::60 2001:7f8:7f::c:60 Port speed differs 160G 20G - In the entry with IPv4 185.0.20.60: set IPv6 to 2001:7f8:7f::60 (now empty); set Speed to 20000 (20G) (now 160000).
- Add an entry: IPv4 185.0.21.60, IPv6 2001:7f8:7f::c:60, speed 20000 (20G), RS peer yes.
Exchanges over time
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 2 |
| Nov 18, 2026 | 2 |
| Nov 17, 2026 | 2 |
| Nov 16, 2026 | 2 |
| Nov 15, 2026 | 2 |
| Nov 14, 2026 | 2 |
| Nov 13, 2026 | 2 |
| Nov 12, 2026 | 2 |
| Nov 11, 2026 | 2 |
| Nov 10, 2026 | 2 |
| Nov 9, 2026 | 2 |
| Nov 8, 2026 | 2 |
| Nov 7, 2026 | 2 |
| Nov 6, 2026 | 2 |
| Nov 5, 2026 | 2 |
| Nov 4, 2026 | 2 |
| Nov 3, 2026 | 2 |
| Nov 2, 2026 | 2 |
| Nov 1, 2026 | 2 |
| Oct 31, 2026 | 2 |
| Oct 30, 2026 | 2 |
| Oct 29, 2026 | 2 |
| Oct 28, 2026 | 2 |
| Oct 27, 2026 | 2 |
| Oct 26, 2026 | 2 |
| Oct 25, 2026 | 2 |
| Oct 24, 2026 | 2 |
| Oct 23, 2026 | 2 |
| Oct 22, 2026 | 2 |
| Oct 21, 2026 | 2 |
| Oct 20, 2026 | 2 |
| Oct 19, 2026 | 2 |
| Oct 18, 2026 | 2 |
| Oct 17, 2026 | 2 |
| Oct 16, 2026 | 2 |
| Oct 15, 2026 | 2 |
| Oct 14, 2026 | 2 |
| Oct 13, 2026 | 2 |
| Oct 12, 2026 | 2 |
| Oct 11, 2026 | 2 |
| Oct 10, 2026 | 2 |
| Oct 9, 2026 | 2 |
| Oct 8, 2026 | 2 |
| Oct 7, 2026 | 2 |
| Oct 6, 2026 | 2 |
| Oct 5, 2026 | 2 |
| Oct 4, 2026 | 2 |
| Oct 3, 2026 | 2 |
Map
Where CC INTERNET'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.
| NIX.CZ Prague, Czechia | 25G | Not in PeeringDB | |
| Peering.cz Prague, Bratislava, Vienna, Frankfurt, Czechia | 160G | Both IPv4 not in PeeringDBIPv6 not in PeeringDBSpeed differs |
These exchanges have a switch in a facility where CC INTERNET lists itself in PeeringDB, but don't have CC INTERNET 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.
Facilities (2)
The buildings CC INTERNET lists in PeeringDB, and how many of the exchanges in each it's on.
| CE Colo PraguePrague | 2 of 8 | |
| TTC TELEPORT DC1Prague | 2 of 3 |