F.H.U. RACZEK-NET Bozena Rak
AS197849 · Raczek.Net Sp. z o.o.
Tools: Where can I peer with F.H.U. RACZEK-NET Bozena Rak? · Where should F.H.U. RACZEK-NET Bozena Rak peer next? · Compare F.H.U. RACZEK-NET Bozena Rak 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 F.H.U. RACZEK-NET Bozena Rak's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-11-19 12:40 UTC.
Make the changes on F.H.U. RACZEK-NET Bozena Rak'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 (2)
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 178.216.40.63 178.216.40.63 178.216.41.133 IPv6 address missing from PeeringDB none 2001:7f8:5b::63 2001:7f8:5b::389 Port speed differs 10G 2 × 10G - In the entry with IPv4 178.216.40.63: set IPv6 to 2001:7f8:5b::63 (now empty).
- Add an entry: IPv4 178.216.41.133, IPv6 2001:7f8:5b::389, speed 10000 (10G), 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.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:678:3ac::338 - In the entry with IPv4 89.46.145.86: set IPv6 to 2001:678:3ac::338 (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
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 F.H.U. RACZEK-NET Bozena Rak'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.
| EPIX.Katowice Katowice/Silesia, Poland | 10G | Both IPv4 not in PeeringDBIPv6 not in PeeringDBSpeed differs | |
| EPIX.Warszawa Warsaw, Poland | 10G | Both IPv6 not in PeeringDB |
F.H.U. RACZEK-NET Bozena Rak lists no facilities in PeeringDB.