ITCare Pawel Staszewski
AS198560 · ITCare
Tools: Where can I peer with ITCare Pawel Staszewski? · Where should ITCare Pawel Staszewski peer next? · Compare ITCare Pawel Staszewski 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 ITCare Pawel Staszewski'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 ITCare Pawel Staszewski'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 ITCare Pawel Staszewski's PeeringDB record. Add one entry per connection with these values.
-
IPv4 89.46.145.137 IPv6 2001:678:3ac::a137 Speed 100000 Mbps (100G) 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 178.216.40.112 178.216.40.112 178.216.40.138 IPv6 address missing from PeeringDB 2001:7f8:5b::112 2001:7f8:5b::112 2001:7f8:5b::169 Port speed differs 1G 100G + 1G - Add an entry: IPv4 178.216.40.138, IPv6 2001:7f8:5b::169, speed 100000 (100G), 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.
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 | 1 |
| Oct 21, 2026 | 1 |
| Oct 20, 2026 | 1 |
| Oct 19, 2026 | 1 |
| Oct 18, 2026 | 1 |
| Oct 17, 2026 | 1 |
| Oct 16, 2026 | 1 |
| Oct 15, 2026 | 1 |
| Oct 14, 2026 | 1 |
| Oct 13, 2026 | 1 |
| Oct 12, 2026 | 1 |
| Oct 11, 2026 | 1 |
| Oct 10, 2026 | 1 |
| Oct 9, 2026 | 1 |
| Oct 8, 2026 | 1 |
| Oct 7, 2026 | 1 |
| Oct 6, 2026 | 1 |
| Oct 5, 2026 | 1 |
| Oct 4, 2026 | 1 |
| Oct 3, 2026 | 1 |
Map
Where ITCare Pawel Staszewski'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 | 1G | Both IPv4 not in PeeringDBIPv6 not in PeeringDBSpeed differs | |
| EPIX.Warszawa Warsaw, Poland | 100G | Not in PeeringDB |
These exchanges have a switch in a facility where ITCare Pawel Staszewski lists itself in PeeringDB, but don't have ITCare Pawel Staszewski 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 ITCare Pawel Staszewski lists in PeeringDB, and how many of the exchanges in each it's on.
| 4 Data CenterKatowice | 1 of 7 |
Recent changes Search them
- Oct 23, 2026 [IXF] AS198560 ITCare Pawel Staszewski added to EPIX.Warszawa