YIPTEL: PeeringDB fix list
AS33264
One thing to fix in YIPTEL's PeeringDB record, from what its exchanges publish: 1 to add. As of 2026-10-08 20:58 UTC.
AS33264 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 YIPTEL's PeeringDB record. Add one entry per connection with these values.
-
SLIX - Salt Lake City Internet Exchange Salt Lake City, United States · PeeringDB 829From its IX-F export and website members list
IPv4 149.112.13.20 IPv6 2001:504:105::20 Speed 10000 Mbps (10G) RS peer No 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/33264/: 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.