ixreport

Telegram_HEL: PeeringDB fix list

AS211157

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

AS211157 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 Telegram_HEL'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.5
    IPv62a03:5f80:4::225:5
    Speed400000 Mbps (400G)
    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
    IPv4195.208.210.131
    IPv62001:7f8:20:101::210:131
    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/211157/: 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.