ixreport

PACKET LOSS LTD

AS202831 · Packet Loss LTD

5Exchanges
1On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
NSPType
OpenPeering policy
5Using the route servers
1To fix in PeeringDB
3Facilities in PeeringDB

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

Make the changes on PACKET LOSS LTD'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 PACKET LOSS LTD's PeeringDB record. Add one entry per connection with these values.

  1. Spain DE-CIX Madrid Madrid, Spain · PeeringDB 1277From its IX-F export and website members list
    IPv4185.1.192.18
    IPv62001:7f8:a0:0:3:184f:0:1
    Speed10000 Mbps (10G)
    RS peerYes

Exchanges over time

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

Map

Where PACKET LOSS LTD'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 41G across 5 exchanges.

Spain DE-CIX Madrid Madrid, Spain 185.1.192.18 2001:7f8:a0:0:3:184f:0:1 10G Down Not in PeeringDB
Netherlands GNM-IX Amsterdam, Netherlands 178.18.225.72 2a03:5f80:4::225:72 10G Yes Both
Russia ixFabric - Moscow Moscow, Russia 2a0e:8f01:1000:18::104 1G Yes PeeringDB
Russia PITER-IX Moscow Moscow, Russia 185.0.15.27 2001:7f8:eb::3:184f:1 10G Yes PeeringDB
Russia PITER-IX Saint-Petersburg Saint-Petersburg, Russia 185.0.45.179 2001:7f8:e6::3:184f:1 10G Yes PeeringDB

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

These exchanges have a switch in a facility where PACKET LOSS LTD lists itself in PeeringDB, but don't have PACKET LOSS LTD 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.

Russia MSK-IX MoscowMoscow, Russia 638 Moscow M9
Netherlands Global-IXAmsterdam, Netherlands 138 Moscow M9
Russia Eurasia Peering IXMoscow, Russia 136 Moscow M9
Germany ERA-IX FrankfurtFrankfurt, Germany 85 TornadoDC - FRA1
Russia W-IXMoscow, Russia 66 Moscow M9
Russia CLOUD-IX MSKMoscow, Russia 52 Moscow M9
Russia SFO-IXBarnaul, Novosibirsk, Russia 30 Moscow M9
Facilities (3)

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

Russia Moscow M9Moscow 3 of 9
Germany TornadoDC - FRA1Langen 0 of 1
Netherlands SkyLink Data Center BVEygelshoven No exchange