Hotwire Communications: PeeringDB fix list
AS23089 · peeringdb.com/net/4454
2 things to fix in Hotwire Communications's PeeringDB record, from what its exchanges publish: 1 to add, 1 to check. As of 2026-10-08 21:56 UTC.
Make the changes on Hotwire Communications'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 (1)
On the exchange's own member list, but not in Hotwire Communications'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.
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If Hotwire Communications has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
Any2West Los Angeles and Silicon Valley, United States · PeeringDB 142Not on its website members listIPv4 206.72.211.194 IPv6 2001:504:13::211:194 Speed 20000 Mbps (20G) This exchange only publishes a website list, and some leave out members who ask not to be listed.
From ixreport.com/net/23089/: 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.