Sloth Networks: PeeringDB fix list
AS212276
4 things to fix in Sloth Networks's PeeringDB record, from what its exchanges publish: 3 to add, 1 to correct. As of 2026-10-08 20:58 UTC.
AS212276 has no PeeringDB record. Create one (register, then request the network for your organisation) before adding these exchanges.
Add these exchanges (3)
On the exchange's own member list, but not in Sloth Networks's PeeringDB record. Add one entry per connection with these values.
-
4b42 Internet Exchange Point Zurich, Switzerland · PeeringDB 2447From its IX-F export and website members listIPv4 185.1.125.212 IPv6 2001:7f8:d0::3:3d34:1 Speed Not published RS peer Yes -
IPv4 206.83.136.32 IPv6 2001:504:9e::32 Speed 10000 Mbps (10G) RS peer Not published -
IPv4 206.83.12.59 IPv6 2001:504:98::59 Speed 10000 Mbps (10G) RS peer Not published
Correct these entries (1)
Addresses or port speeds in PeeringDB that differ from the exchange's IX-F export. The changes below follow the export; if the export is the one that's wrong, tell the exchange instead.
-
Problem PeeringDB has The export has Address belongs to another network in PeeringDB 206.83.12.59 is AS25735 Sloth Networks 206.83.12.59 Address belongs to another network in PeeringDB 2001:504:98::59 is AS25735 Sloth Networks 2001:504:98::59 An address another network has in PeeringDB isn't suggested here: either that network's entry or the exchange's export is wrong. Ask the exchange which.
From ixreport.com/net/212276/: 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.