Optua Telecommunications Limited: PeeringDB fix list

AS202076

3 things to fix in Optua Telecommunications Limited's PeeringDB record, from what its exchanges publish: 3 to add. As of 2026-10-08 20:58 UTC.

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

Add these exchanges (3)

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

  1. Switzerland FogIXP Avers, Switzerland · PeeringDB 3756From its IX-F export and website members list
    IPv4185.1.147.182
    IPv62001:7f8:ca:1:0:20:2076:1
    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. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358From its IX-F export
    IPv4178.18.236.98
    IPv62a03:5f80:4:2::236:98
    Speed10000 Mbps (10G)
    RS peerYes

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

  3. United Kingdom LONAP London, United Kingdom · PeeringDB 53From its IX-F export
    IPv45.57.82.67
    IPv62001:7f8:17::3:155c:1
    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.

From ixreport.com/net/202076/: 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.