RTCLOUD, LLC: PeeringDB fix list

AS49395

One thing to fix in RTCLOUD, LLC's PeeringDB record, from what its exchanges publish: 1 to add. As of 2026-10-08 20:58 UTC.

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

Add these exchanges (1)

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

  1. Russia MSK-IX Saint-Petersburg St.Petersburg, Russia · PeeringDB 107From its IX-F export

    4 connections, so 4 entries:

    IPv4194.226.102.40
    IPv62001:7f8:20:202::102:40
    SpeedNot published
    RS peerYes
    IPv4194.226.102.39
    IPv62001:7f8:20:202::102:39
    SpeedNot published
    RS peerYes
    IPv4194.226.100.40
    IPv62001:7f8:20:201::100:40
    SpeedNot published
    RS peerYes
    IPv4194.226.100.39
    IPv62001:7f8:20:201::100:39
    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/49395/: 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.