Qwilt: PeeringDB fix list
AS20253 · peeringdb.com/net/27326
6 things to fix in Qwilt's PeeringDB record, from what its exchanges publish: 6 to add. As of 2026-10-08 21:56 UTC.
Make the changes on Qwilt'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 (6)
On the exchange's own member list, but not in Qwilt's PeeringDB record. Add one entry per connection with these values.
-
The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
-
IX.br (PTT.br) Rio de Janeiro Rio de Janeiro/RJ, Brazil · PeeringDB 177From its website members listThe exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
-
The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
-
IPv4 206.53.143.54 IPv6 2001:504:47::4f1d:0:1 Speed 100000 Mbps (100G) RS peer Yes -
IPv4 206.81.81.195 IPv6 2001:504:16::4f1d Speed Not published RS peer Not published PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
SLIX - Salt Lake City Internet Exchange Salt Lake City, United States · PeeringDB 829From its IX-F export and website members listIPv4 149.112.13.52 IPv6 2001:504:105::52 Speed 100000 Mbps (100G) 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/20253/: 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.