ixreport

Laguna sp. z o.o.

AS60534 · lagunaNET

2Exchanges
1On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Cable/DSL/ISPType
OpenPeering policy
1Using the route servers
2To fix in PeeringDB
0Facilities in PeeringDB

Tools: Where can I peer with Laguna sp. z o.o.? · Where should Laguna sp. z o.o. peer next? · Compare Laguna sp. z o.o. 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 Laguna sp. z o.o.'s PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct. As of 2026-11-19 18:41 UTC.

Make the changes on Laguna sp. z o.o.'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 Laguna sp. z o.o.'s PeeringDB record. Add one entry per connection with these values.

  1. Poland TPIX PL Warsaw, Poland · PeeringDB 482From its IX-F export and website members list
    IPv4195.149.234.61
    IPv6–
    SpeedNot published
    RS peerNot published

    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.

  1. Poland EPIX.Katowice Katowice/Silesia, Poland · PeeringDB 491
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB178.216.40.3178.216.40.3 178.216.40.48
    IPv6 address missing from PeeringDBnone2001:7f8:5b::3 2001:7f8:5b::48
    Port speed differs10G2 × 10G
    • In the entry with IPv4 178.216.40.3: set IPv6 to 2001:7f8:5b::3 (now empty).
    • Add an entry: IPv4 178.216.40.48, IPv6 2001:7f8:5b::48, 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.

Exchanges over time

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

Map

Where Laguna sp. z o.o.'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 10G, at the 1 of 2 exchanges with a speed in PeeringDB or the exchange's IX-F export.

Poland EPIX.Katowice Katowice/Silesia, Poland 178.216.40.3 10G Yes Both IPv4 not in PeeringDBIPv6 not in PeeringDBSpeed differs
Poland TPIX PL Warsaw, Poland 195.149.234.61 Not in PeeringDB

Laguna sp. z o.o. lists no facilities in PeeringDB.