Connect plus
AS48602 · Connect plus s.r.o.
Connect plus s.r.o.
Tools: Where can I peer with Connect plus? · Where should Connect plus peer next? · Compare Connect plus 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 Connect plus's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-11-19 18:41 UTC.
Make the changes on Connect plus's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.
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 differs 91.213.211.240 91.213.211.241 185.0.20.240 185.0.20.241 IPv6 address missing from PeeringDB none 2001:7f8:7f::240 2001:7f8:7f::241 Port speed differs 2 × 10G 2.5G - The entry with IPv4 91.213.211.240, IPv6 – isn't in the export: delete it if that connection is gone.
- The entry with IPv4 91.213.211.241, IPv6 – isn't in the export: delete it if that connection is gone.
- Add an entry: IPv4 185.0.20.240, IPv6 2001:7f8:7f::240, speed 2500 (2.5G), RS peer yes.
- Add an entry: IPv4 185.0.20.241, IPv6 2001:7f8:7f::241, speed 2500 (2.5G), 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 Connect plus'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 | 10G | Both | |
| Peering.cz Prague, Bratislava, Vienna, Frankfurt, Czechia | 2 × 10G | Both IPv4 differsIPv6 not in PeeringDBSpeed differs |
These exchanges have a switch in a facility where Connect plus lists itself in PeeringDB, but don't have Connect plus 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 (1)
The buildings Connect plus lists in PeeringDB, and how many of the exchanges in each it's on.
| CE Colo PraguePrague | 2 of 8 |