OPTIXCOM: PeeringDB fix list

AS205923

2 things to fix in OPTIXCOM's PeeringDB record, from what its exchanges publish: 2 to add. As of 2026-10-08 18:53 UTC.

AS205923 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 OPTIXCOM's PeeringDB record. Add one entry per connection with these values.

ANIX Tirana, Albania · PeeringDB 2004From its IX-F export and website members list

IPv4 185.1.100.40

IPv6 2001:7f8:bb::40

Speed 10000 Mbps (10G)

RS peer Yes
KleyReX Frankfurt, Germany · PeeringDB 123From its IX-F export and website members list

IPv4 –

IPv6 2001:7f8:33::a120:5923:1

Speed 100 Mbps (100M)

RS peer Yes

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

IPv4	185.1.100.40
IPv6	2001:7f8:bb::40
Speed	10000 Mbps (10G)
RS peer	Yes

IPv4	–
IPv6	2001:7f8:33::a120:5923:1
Speed	100 Mbps (100M)
RS peer	Yes

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