STIX: operator report
Bozen/Bolzano, Italy · PeeringDB 2537 · ixreport.com/ix/2537/report/
Members of STIX 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. 3 networks to follow up.
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 (3)
These networks could add STIX to their PeeringDB record. Networks with no PeeringDB record would need to create one first.
| Network | On your | Addresses | Contact |
|---|---|---|---|
| AS22359 NETSKRTSYSTEMS-UK | IX-F and website | 185.1.124.11 2001:7f8:cf::11 30G |
No public contact |
| AS28716 Retelit Spa | IX-F and website | 185.1.124.10 2001:7f8:cf::10 10G |
No public contact |
| AS34694 Stadtwerke Woergl GmbH | IX-F and website | 185.1.124.5 2001:7f8:cf::5 1G |
No public contact |
Addresses or port speeds that differ (0)
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.
None: every network's addresses and port speed match.
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.