ixreport

MedsiGroup: PeeringDB fix list

AS206295 · peeringdb.com/net/20262

PeeringDB

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

Make the changes on MedsiGroup's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Add these exchanges (2)

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

  1. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31From its IX-F export and website members list

    2 connections, so 2 entries:

    IPv480.81.196.37
    IPv62001:7f8::3:25d7:0:1
    Speed200000 Mbps (200G)
    RS peerYes
    IPv480.81.196.39
    IPv62001:7f8::3:25d7:0:2
    Speed200000 Mbps (200G)
    RS peerYes
  2. Russia MSK-IX Moscow Moscow, Russia · PeeringDB 100From its IX-F export

    2 connections, so 2 entries:

    IPv4195.208.208.52
    IPv6–
    SpeedNot published
    RS peerYes
    IPv4195.208.208.139
    IPv6–
    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/206295/: 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.