Ssmidge Technologies: PeeringDB fix list

AS60900 · peeringdb.com/net/32862

PeeringDB

3 things to fix in Ssmidge Technologies's PeeringDB record, from what its exchanges publish: 2 to add, 1 to check. As of 2026-10-08 20:58 UTC.

Make the changes on Ssmidge Technologies'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 Ssmidge Technologies's PeeringDB record. Add one entry per connection with these values.

  1. Poland 1-IX EU New-York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Hong Kong, Poland · PeeringDB 3958From its website members list

    The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

  2. Egypt PyramIX Cairo, Egypt · PeeringDB 3302From its IX-F export
    IPv4–
    IPv62a0e:46c4:102::609:0:1
    Speed100 Mbps (100M)
    RS peerYes

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

Check these entries (1)

In PeeringDB, but on none of the exchange's own lists. If Ssmidge Technologies has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. Netherlands NSIX Amsterdam Amsterdam, Netherlands · PeeringDB 4589Not on its website members list
    IPv4193.192.12.25
    IPv62001:7f8:130::ede4:1
    Speed10000 Mbps (10G)

    This exchange only publishes a website list, and some leave out members who ask not to be listed.

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