POM-IX: operator report

Gdańsk, Poland · PeeringDB 4480 · ixreport.com/ix/4480/report/

Download CSV

Members of POM-IX that PeeringDB has wrong, from its IX-F export (14 networks, read 2026-10-08 20:54 UTC) and its website members list (13 networks, read 2026-10-08 20:54 UTC), against PeeringDB as of 2026-10-08 20:58 UTC. 6 networks to follow up; 2 with a public PeeringDB contact.

Contacts are the networks' public PeeringDB contacts: the peering (policy) contact where there is one, else technical, then NOC. Networks keep these themselves on PeeringDB.

On your lists, missing from PeeringDB (5)

These networks could add POM-IX to their PeeringDB record. Networks with no PeeringDB record would need to create one first.

NetworkOn yourAddressesContact
AS29649 Limes sp. z o.o. PeeringDBIX-F and website 185.0.16.69
10G
No public contact
AS51976 AS51976website – No PeeringDB record
AS60191 Nowatel PeeringDBIX-F and website 185.0.16.75
10G
NOC: email address (needs JavaScript) +48587272020
AS198881 GetResponseIX-F and website 185.0.16.77
10G
No PeeringDB record
AS207217 HAWE CDN PeeringDBwebsite – Policy: email address (needs JavaScript) +48618614935

Addresses or port speeds that differ (1)

PeeringDB against your IX-F export, for the 11 networks in both. Either the network's PeeringDB record or the export is out of date.

NetworkProblemPeeringDB hasYour export hasContact
AS41297 ABAKS PeeringDB Port speed differs2 × 10G10G No public contact

In PeeringDB, not on your lists (0)

Either your lists are missing these networks, or they've left and their PeeringDB record is out of date.

None.