ixreport

ALLO Communications

AS15108 · Allo Fiber

ALLO Communications 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
1To fix in PeeringDB
11Facilities in PeeringDB

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

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

One thing to fix in ALLO Communications's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-11-19 18:41 UTC.

Make the changes on ALLO Communications'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 differs100G40G
    • In the entry with IPv4 206.41.105.71: set Speed to 40000 (40G) (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 ALLO Communications'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 400G across 3 exchanges.

United States IX-Denver Denver, United States 206.53.175.86 2001:504:58::86 100G Yes Both
United States Ninja-IX Phoenix Phoenix, United States 206.41.105.71 2001:504:3b::71 100G 20 routes Both Speed differs
United States OmahaIX Omaha, United States 206.126.235.12 2001:504:33::c 200G Yes Both

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

These exchanges have a switch in a facility where ALLO Communications lists itself in PeeringDB, but don't have ALLO Communications 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 (11)

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

United States Equinix CH1/CH2/CH4 - ChicagoChicago 0 of 9
United States CoreSite - Denver (DE1)Denver 1 of 3
United States EdgeConneX Phoenix (EDCPHX01)Tempe 1 of 3
United States Netrality Kansas City - 1102 GrandKansas City 0 of 2
United States 1623 Farnam - OmahaOmaha 1 of 1
United States EdgeConneX Las Vegas (EDCLAS01)Las Vegas 0 of 1
United States ACT CheyenneCheyenne No exchange
United States Lincoln Data CentersLincoln No exchange
United States Lunavi - CheyenneCheyenne No exchange
United States TierPoint Omaha - BellevueBellevue No exchange
United States TierPoint Omaha - MidlandsPapillion No exchange