7sat: PeeringDB fix list
AS203530
One thing to fix in 7sat's PeeringDB record, from what its exchanges publish: 1 to add. As of 2026-10-08 22:13 UTC.
AS203530 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 7sat's PeeringDB record. Add one entry per connection with these values.
-
2 connections, so 2 entries:
IPv4 185.79.213.17 IPv6 2a01:7640:9400::17 Speed 10000 Mbps (10G) RS peer Yes IPv4 185.79.213.117 IPv6 2a01:7640:9400::117 Speed 10000 Mbps (10G) RS peer Yes 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/203530/: 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.