ixreport

InfoWest

AS11071

5Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
NSPType
OpenPeering policy
5Using the route servers
1To fix in PeeringDB
6Facilities in PeeringDB

Tools: Where can I peer with InfoWest? · Where should InfoWest peer next? · Compare InfoWest with another network

This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

One thing to fix in InfoWest's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on InfoWest's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

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.

  1. United States SUPRnet Saint George, United States · PeeringDB 363
    ProblemPeeringDB hasThe export has
    Port speed differs20G10G
    • In the entry with IPv4 206.53.201.10: set Speed to 10000 (10G) (now 20000).

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

Exchanges over time

0246Oct 3, 2026Nov 19, 20265
Show as a table
DateExchanges
Nov 19, 20265
Nov 18, 20265
Nov 17, 20265
Nov 16, 20265
Nov 15, 20265
Nov 14, 20265
Nov 13, 20265
Nov 12, 20265
Nov 11, 20265
Nov 10, 20265
Nov 9, 20265
Nov 8, 20265
Nov 7, 20265
Nov 6, 20265
Nov 5, 20265
Nov 4, 20265
Nov 3, 20265
Nov 2, 20265
Nov 1, 20265
Oct 31, 20265
Oct 30, 20265
Oct 29, 20265
Oct 28, 20265
Oct 27, 20265
Oct 26, 20265
Oct 25, 20265
Oct 24, 20265
Oct 23, 20265
Oct 22, 20265
Oct 21, 20265
Oct 20, 20265
Oct 19, 20265
Oct 18, 20265
Oct 17, 20265
Oct 16, 20265
Oct 15, 20265
Oct 14, 20265
Oct 13, 20265
Oct 12, 20265
Oct 11, 20265
Oct 10, 20265
Oct 9, 20265
Oct 8, 20265
Oct 7, 20265
Oct 6, 20265
Oct 5, 20265
Oct 4, 20265
Oct 3, 20265

Map

Where InfoWest's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.

Exchanges

Total port capacity 240G across 5 exchanges.

United States Any2Denver Denver, United States 206.51.46.42 2605:6c00:303:303::42 10G Yes PeeringDB
United States Any2West Los Angeles and Silicon Valley, United States 206.72.210.233 2001:504:13::233 100G Yes PeeringDB
United States Equinix San Jose San Jose, United States 206.223.117.10 2001:504:0:1:0:1:1071:1 100G Yes PeeringDB
United States SLIX - Salt Lake City Internet Exchange Salt Lake City, United States 149.112.13.13 2001:504:105::13 10G 84 routes Both
United States SUPRnet Saint George, United States 206.53.201.10 2001:504:60::2b3f 20G Yes Both Speed differs

Exchanges in its buildings that it isn't on (15)

These exchanges have a switch in a facility where InfoWest lists itself in PeeringDB, but don't have InfoWest as a member in PeeringDB, their IX-F export or their website. Joining one is usually just a cross-connect away. The biggest exchanges come first; ghost exchanges are left out.

Facilities (6)

The buildings InfoWest lists in PeeringDB, and how many of the exchanges in each it's on.