ixreport

TCT West, Inc.

AS4474 · TCT, Tri County Telephone Association Inc

4Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Cable/DSL/ISPType
OpenPeering policy
4Using the route servers
1To fix in PeeringDB
5Facilities in PeeringDB

Tools: Where can I peer with TCT West, Inc.? · Where should TCT West, Inc. peer next? · Compare TCT West, Inc. with another network

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

One thing to fix in TCT West, Inc.'s PeeringDB record, from what its exchanges publish: 1 at exchanges that look shut down. As of 2026-11-19 12:40 UTC.

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

Exchanges that look shut down (1)

In PeeringDB, but these exchanges have fewer than two networks besides their operator: nobody to peer with, so they may have shut down. If an exchange is gone, delete its entry.

  1. United States YRIXghost Billings, MT, United States · PeeringDB 199

    Only one outside network

    IPv4206.126.116.105
    IPv6–
    Speed100 Mbps (100M)

Exchanges over time

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

Map

Where TCT West, Inc.'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 400.1G across 4 exchanges.

United States Any2Denver Denver, United States 206.51.46.45 2605:6c00:303:303::45 100G Yes PeeringDB
United States IX-Denver Denver, United States 206.53.175.38 2001:504:58::38 100G Yes Both
United States SIX Seattle Seattle, United States 206.81.80.215 2001:504:16::117a 200G Yes Both
United States YRIXghost Billings, MT, United States 206.126.116.105 100M Yes PeeringDB

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

These exchanges have a switch in a facility where TCT West, Inc. lists itself in PeeringDB, but don't have TCT West, Inc. 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.

Bulgaria NetIXSofia, Bulgaria 204 Digital Realty Seattle SEA10
United States SIX Seattle (Jumbo)Seattle, United States 69 Digital Realty Seattle SEA10
United States MegaIX SeattleSeattle, United States 15 Digital Realty Seattle SEA10
United States Pacific WaveWest Coast, United States 14 Digital Realty Seattle SEA10
United States MegaIX DenverDenver, United States 7 CoreSite - Denver (DE1)
Facilities (5)

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

United States Digital Realty Seattle SEA10Seattle 1 of 5
United States CoreSite - Denver (DE1)Denver 2 of 3
United States Cogent BillingsBillings No exchange
United States iConnect Billings Fiber HotelBillings No exchange
United States ParsecBillings No exchange