ixreport

Mevspace

AS201814 · skynode, mevspace

Mevspace sp. z o.o.

8Exchanges
2On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
ContentType
OpenPeering policy
7Using the route servers
3To fix in PeeringDB
3Facilities in PeeringDB

Tools: Where can I peer with Mevspace? · Where should Mevspace peer next? · Compare Mevspace with another network

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

PeeringDB fix list Printable page · CSV

3 things to fix in Mevspace's PeeringDB record, from what its exchanges publish: 2 to add, 1 to correct. As of 2026-11-19 18:41 UTC.

Make the changes on Mevspace'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 (2)

On the exchange's own member list, but not in Mevspace's PeeringDB record. Add one entry per connection with these values.

  1. Ukraine 1-IX UA Kyiv, Ukraine · PeeringDB 3562From its website members list

    The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

  2. Switzerland 4b42 Internet Exchange Point Zurich, Switzerland · PeeringDB 2447From its IX-F export
    IPv4–
    IPv62001:7f8:d0::3:1456:1
    SpeedNot published
    RS peerYes

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.

  1. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 200G100G
    • In the entry with IPv4 178.18.236.240: set Speed to 100000 (100G) (now 200000).
    • In the entry with IPv4 178.18.236.250: set Speed to 100000 (100G) (now 200000).

    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

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

Map

Where Mevspace'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 1.2T, at the 6 of 8 exchanges with a speed in PeeringDB or the exchange's IX-F export.

Poland 1-IX EU New-York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Hong Kong, Poland 185.0.42.228
185.0.42.229
2001:7f8:115:1::228
2001:7f8:115:1::229
2 × 100G Yes Both
Ukraine 1-IX UA Kyiv, Ukraine Not in PeeringDB
Poland 1-PL FREE Warsaw, Wroclaw, Katowice, Poland 194.246.39.20 2001:7f8:16e::20 100G Yes PeeringDB
Switzerland 4b42 Internet Exchange Point Zurich, Switzerland 2001:7f8:d0::3:1456:1 Yes Not in PeeringDB
Ukraine Giganet IXN Amsterdam, Frankfurt am Main, Kharkiv, Kyiv, Lviv, Odesa, Warsaw, Zaporizhzhia, Zhytomyr, Ukraine 185.1.62.35
185.1.63.193
2001:7f8:6c::35
2001:7f8:6c::448
2 × 100G Yes PeeringDB
Netherlands GNM-IX Amsterdam, Netherlands 178.18.236.240
178.18.236.250
2a03:5f80:4:2::236:240
2a03:5f80:4:2::236:250
2 × 200G Yes Both Speed differs
United States GNM-IX US New York, United States 95.161.244.7 2a03:5f80:244::244:7 100G Yes PeeringDB
Poland TPIX PL Warsaw, Poland 195.149.232.16
195.149.234.76
2001:7f8:27::20:1814:1
2001:7f8:27::20:1814:2
2 × 100G Yes Both

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

These exchanges have a switch in a facility where Mevspace lists itself in PeeringDB, but don't have Mevspace 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 (3)

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

Poland Equinix WA1 - Warsaw, Centrum LIMWarsaw 5 of 13
Poland LIM WarsawWarsaw 5 of 11
Poland MEVSPACE DC-1Wyszków No exchange