NVL-IX: operator report
Athens, Greece · PeeringDB 4775 · ixreport.com/ix/4775/report/
Members of NVL-IX that PeeringDB has wrong, from its IX-F export (14 networks, read 2026-10-08 20:54 UTC) and its website members list (11 networks, read 2026-10-08 20:54 UTC), against PeeringDB as of 2026-10-08 20:58 UTC. 5 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 (4)
These networks could add NVL-IX to their PeeringDB record. Networks with no PeeringDB record would need to create one first.
| Network | On your | Addresses | Contact |
|---|---|---|---|
| AS22772 Login | website | – | NOC: email address (needs JavaScript) +15206183000 |
| AS200736 MEDIANET INVEST M.I.K.E | IX-F and website | 194.93.123.121 2001:7f8:37:21:2347:20:736:1 100G |
No public contact |
| AS203635 Exandas | IX-F | 194.93.123.123 1G |
No PeeringDB record |
| AS211186 FastTelecomGR | IX-F and website | 194.93.123.111 2001:7f8:37:21:2347:21:1186:1 10G |
No public contact |
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.
| Network | Problem | PeeringDB has | Your export has | Contact |
|---|---|---|---|---|
| AS215036 COMPUGEN | IPv6 address missing from PeeringDB | none | 2001:7f8:37:21:2347:21:5036:1 | 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.