LZ NETWORKS: PeeringDB fix list

AS44509

2 things to fix in LZ NETWORKS's PeeringDB record, from what its exchanges publish: 2 to add. As of 2026-10-08 20:58 UTC.

AS44509 has no PeeringDB record. Create one (register, then request the network for your organisation) before adding these exchanges.

Add these exchanges (2)

On the exchange's own member list, but not in LZ NETWORKS's PeeringDB record. Add one entry per connection with these values.

  1. Canada ONIX Toronto, Canada · PeeringDB 4059From its IX-F export and website members list
    IPv4149.112.50.134
    IPv62001:504:125:e1::134
    Speed1000 Mbps (1G)
    RS peerYes

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

  2. Canada UNM-Exch Canada-West Vancouver, Canada · PeeringDB 2452From its IX-F export and website members list

    2 connections, so 2 entries:

    IPv4192.34.27.51
    IPv6–
    SpeedNot published
    RS peerNot published
    IPv4–
    IPv62602:ffb1:200:0:192:34:27:51
    SpeedNot published
    RS peerNot published

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

From ixreport.com/net/44509/: PeeringDB against each exchange's IX-F export and website members list. Exchanges whose lists couldn't be read on this update aren't included.