ixreport

24htv: PeeringDB fix list

AS50775

2 things to fix in 24htv's PeeringDB record, from what its exchanges publish: 2 to add. As of 2026-10-08 22:13 UTC.

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

  1. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358From its IX-F export
    IPv4178.18.225.66
    IPv62a03:5f80:4::225:66
    Speed100000 Mbps (100G)
    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. Russia MSK-IX Moscow Moscow, Russia · PeeringDB 100From its IX-F export

    2 connections, so 2 entries:

    IPv4195.208.210.111
    IPv62001:7f8:20:101::210:111
    SpeedNot published
    RS peerYes
    IPv4195.208.210.113
    IPv62001:7f8:20:101::210:113
    SpeedNot published
    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/50775/: 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.