SpriteLink International Carrier: PeeringDB fix list
AS2863 · peeringdb.com/net/1219
4 things to fix in SpriteLink International Carrier's PeeringDB record, from what its exchanges publish: 2 to add, 2 to correct. As of 2026-10-08 20:58 UTC.
Make the changes on SpriteLink International Carrier'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 SpriteLink International Carrier's PeeringDB record. Add one entry per connection with these values.
-
IPv4 195.69.119.220 IPv6 2001:7f8:d:fb::220 Speed 200000 Mbps (200G) RS peer No -
IPv4 195.245.240.220 IPv6 2001:7f8:d:fc::220 Speed 200000 Mbps (200G) RS peer No
Correct these entries (2)
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 IPv6 address missing from PeeringDB none 2001:7f8:d:fe::220 Port speed differs 1G 200G - In the entry with IPv4 194.68.128.220: set IPv6 to 2001:7f8:d:fe::220 (now empty); set Speed to 200000 (200G) (now 1000).
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:7f8:d:ff::220 Port speed differs 1G 200G - In the entry with IPv4 194.68.123.220: set IPv6 to 2001:7f8:d:ff::220 (now empty); set Speed to 200000 (200G) (now 1000).
From ixreport.com/net/2863/: 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.