ixreport

BAM Broadband

AS20303 · Desert iNET, DirectLink

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
1To fix in PeeringDB
5Facilities in PeeringDB

Tools: Where can I peer with BAM Broadband? · Where should BAM Broadband peer next? · Compare BAM Broadband 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 BAM Broadband's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on BAM Broadband'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 Ninja-IX Phoenix Phoenix, United States · PeeringDB 662
    ProblemPeeringDB hasThe export has
    Port speed differs100G25G
    • In the entry with IPv4 206.41.105.75: set Speed to 25000 (25G) (now 100000).

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 BAM Broadband'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 300G across 3 exchanges.

United States Any2Denver Denver, United States 206.51.46.54 2605:6c00:303:303::54 100G Yes PeeringDB
United States IX-Denver Denver, United States 206.53.175.78 2001:504:58::78 100G Yes Both
United States Ninja-IX Phoenix Phoenix, United States 206.41.105.75 2001:504:3b::75 100G 15 routes Both Speed differs

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

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

United States DE-CIX PhoenixPhoenix, United States 41 EdgeConneX Phoenix (EDCPHX01)
United States MegaIX DenverDenver, United States 7 CoreSite - Denver (DE1); Centersquare Denver (DEN1); DataBank Denver (DEN2)
United States 48 IXPhoenix, United States 5 EdgeConneX Phoenix (EDCPHX01)
Facilities (5)

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

United States CoreSite - Denver (DE1)Denver 2 of 3
United States EdgeConneX Phoenix (EDCPHX01)Tempe 1 of 3
United States Centersquare Denver (DEN1)Highlands Ranch 0 of 1
United States DataBank Denver (DEN2)Centennial 0 of 1
United States Iron Mountain Data Center - Scottsdale (AZS-1)Scottsdale 1 of 1