ixreport

Fatbeam

AS55039 · Fatbeam, LLC

Fatbeam, LLC

3Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Cable/DSL/ISPType
SelectivePeering policy
3Using the route servers
11Facilities in PeeringDB

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

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

PeeringDB fix list

Nothing to fix: Fatbeam's PeeringDB record matches the member lists of the 2 exchanges we could compare (the others publish no list we could read).

Exchanges over time

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

Map

Where Fatbeam'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 120G across 3 exchanges.

United States Central Oregon Internet Exchange Bend, United States 149.112.8.9 2001:504:101::9 10G Yes Both
United States SIX Seattle Seattle, United States 206.81.81.39 2001:504:16::d6ff 100G Yes Both
United States SpokaneIX Spokane, United States 206.83.139.12 2001:504:9f::12 10G Yes PeeringDB

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

These exchanges have a switch in a facility where Fatbeam lists itself in PeeringDB, but don't have Fatbeam 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 NWAXPortland, United States 96 PTOR1
United States SIX Seattle (Jumbo)Seattle, United States 69 Digital Realty Seattle SEA10
United States Ninja-IX PhoenixPhoenix, United States 60 Iron Mountain Data Center - Phoenix (AZP-1)
United States DE-CIX PhoenixPhoenix, United States 41 Iron Mountain Data Center - Phoenix (AZP-1)
Puerto Rico PR-IXSan Juan, Puerto Rico 33 PTOR1
United States MegaIX SeattleSeattle, United States 15 Digital Realty Seattle SEA10; TierPoint Spokane
United States Pacific WaveWest Coast, United States 14 Digital Realty Seattle SEA10
United States Global Peer ExchangeWashington, United States 6 Tonaquint Data Center - Boise ID
Facilities (11)

The buildings Fatbeam 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 Iron Mountain Data Center - Phoenix (AZP-1)Phoenix 0 of 2
United States PTOR1Portland 0 of 2
United States TierPoint SpokaneLiberty Lake 1 of 2
United States Fort Rock Data CenterBend 1 of 1
United States Neutron - Coeur d'AleneCoeur d'Alene 1 of 1
United States Neutron - SpokaneSpokane 1 of 1
United States Tonaquint Data Center - Boise IDBoise 0 of 1
United States US Bank BuildingSpokane 1 of 1
United States Serverfarm TiTAN Moses LakeMoses Lake No exchange
United States US Signal OR01 - BendBend No exchange