ixreport

Blue Stream

AS30404

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

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

Make the changes on Blue Stream'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 FL-IX Miami, United States · PeeringDB 954
    ProblemPeeringDB hasThe export has
    Port speed differs300G + 200G2 × 300G
    • In the entry with IPv4 206.41.108.176: set Speed to 300000 (300G) (now 200000).

Exchanges over time

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

Map

Where Blue Stream'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 500G across 1 exchange.

United States FL-IX Miami, United States 206.41.108.176
206.41.108.197
2001:504:40:108::1:176
2001:504:40:108::1:197
300G + 200G 28 routes Both Speed differs

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

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

Puerto Rico PR-IXSan Juan, Puerto Rico 33 Cologix JAX1
United States DE-CIX HoustonHouston, United States 12 Databank Houston West (HOU1) (HOU2)
United States MiamiIXMiami, Florida, United States 4 ColoHouse Miami
United States Chameleon-NAPMiami, United States 3 ColoHouse Miami
Facilities (3)

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

United States ColoHouse MiamiMiami 1 of 3
United States Cologix JAX1Jacksonville 0 of 1
United States Databank Houston West (HOU1) (HOU2)Houston 0 of 1