UNILAB Network
AS218134 · 유니랩
Junseong Lee trading as UniLAB
Tools: Where can I peer with UNILAB Network? · Where should UNILAB Network peer next? · Compare UNILAB Network 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 UNILAB Network's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-11-19 12:40 UTC.
Make the changes on UNILAB Network'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 missing from PeeringDB none 163.61.162.17 - In the entry with IPv6 2a0b:4e07:fb::17: set IPv4 to 163.61.162.17 (now empty).
PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.
Exchanges over time
Collecting since Nov 18, 2026: one point a day, so this fills in as the days go by.
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 1 |
| Nov 18, 2026 | 1 |
In the last 30 days UNILAB Network joined 1 exchange and left 0. Growing networks
Joined
- KCIXP Seoul Nov 18, 2026
Map
Where UNILAB Network'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.
| KCIXP Seoul, South Korea | 1G | Both IPv4 not in PeeringDB |
UNILAB Network lists no facilities in PeeringDB.
Recent changes Search them
- Nov 19, 2026 [PDB] AS218134 UNILAB Network now in PeeringDB at KCIXP
- Nov 18, 2026 [IXF] AS218134 UNILAB Network added to KCIXP