YEGIX: operator report
Edmonton, Canada · PeeringDB 1169 · ixreport.com/ix/1169/report/
Members of YEGIX that PeeringDB has wrong, from its website members list (15 networks, read 2026-10-08 21:25 UTC), against PeeringDB as of 2026-10-08 21:35 UTC. 6 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 (6)
These networks could add YEGIX to their PeeringDB record. Networks with no PeeringDB record would need to create one first.
| Network | On your | Addresses | Contact |
|---|---|---|---|
| AS3359 AS3359 | website | 206.53.140.109 2001:504:46::3359:1 |
No PeeringDB record |
| AS14426 AS14426 | website | 206.53.140.112 2001:504:46::1:4426:1 |
No PeeringDB record |
| AS15296 Cybera Inc | website | 206.53.140.108 2001:504:46::1:5296:1 |
No public contact |
| AS36331 AS36331 | website | 206.53.140.118 2001:504:46::3:6331:1 |
No PeeringDB record |
| AS46184 NorQuest College | website | 206.53.140.116 2001:504:46::4:6184:1 |
No public contact |
| AS46265 Netskrt (Canada) | website | 206.53.140.119 2001:504:46::4:6265:1 |
No public contact |
Addresses or port speeds that differ (0)
YEGIX publishes no IX-F export we could read, so addresses and port speeds can't be compared.
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.