AAIX: operator report
Klagenfurt, Austria · PeeringDB 377 · ixreport.com/ix/377/report/
Members of AAIX that PeeringDB has wrong, from its IX-F export (22 networks, read 2026-10-08 22:05 UTC) and its website members list (23 networks, read 2026-10-08 22:05 UTC), against PeeringDB as of 2026-10-08 22:13 UTC. 8 networks to follow up; 1 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 (2)
These networks could add AAIX to their PeeringDB record. Networks with no PeeringDB record would need to create one first.
Addresses or port speeds that differ (4)
PeeringDB against your IX-F export, for the 20 networks in both. Either the network's PeeringDB record or the export is out of date.
| Network | Problem | PeeringDB has | Your export has | Contact |
|---|---|---|---|---|
| AS21013 eww ag / ITandTEL | Port speed differs | 10G | 1G | No public contact |
| AS26415 VeriSign Global Registry Services | Port speed differs | 1G | 10G | No public contact |
| AS39912 oja.at | Port speed differs | 40G | 20G | No public contact |
| AS62373 Christian Singerl | Port speed differs | 1G | 10G | NOC: email address (needs JavaScript) |
In PeeringDB, not on your lists (2)
Either your lists are missing these networks, or they've left and their PeeringDB record is out of date.