ixreport

Sho Me Technologies

AS55140

Sho Me Technologies, LLC

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

Tools: Where can I peer with Sho Me Technologies? · Where should Sho Me Technologies peer next? · Compare Sho Me Technologies with another network

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

2 things to fix in Sho Me Technologies's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on Sho Me Technologies'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 (2)

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 KCIX Kansas City, United States · PeeringDB 249
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB206.51.7.78206.51.7.78 206.51.7.245
    IPv6 address missing from PeeringDB2001:504:1b:1::782001:504:1b:1::78 2001:504:1b:1::245
    Port speed differs100G100G + 10G
    • In the entry with IPv4 206.51.7.78: set Speed to 10000 (10G) (now 100000).
    • Add an entry: IPv4 206.51.7.245, IPv6 2001:504:1b:1::245, speed 100000 (100G).
  2. United States STLIX Saint Louis, MO, United States · PeeringDB 2585
    ProblemPeeringDB hasThe export has
    Port speed differs100G10G
    • In the entry with IPv4 206.83.12.22: set Speed to 10000 (10G) (now 100000).

Exchanges over time

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

Map

Where Sho Me Technologies'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 200G across 2 exchanges.

United States KCIX Kansas City, United States 206.51.7.78 2001:504:1b:1::78 100G Both IPv4 not in PeeringDBIPv6 not in PeeringDBSpeed differs
United States STLIX Saint Louis, MO, United States 206.83.12.22 2001:504:98::22 100G Both Speed differs

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

These exchanges have a switch in a facility where Sho Me Technologies lists itself in PeeringDB, but don't have Sho Me Technologies 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 Netrality Kansas City - 1102 Grand; Netrality St. Louis - 900 Walnut
United States FD-IX - St. LouisSt. Louis, MO, United States 18 Netrality St. Louis - 900 Walnut
Facilities (2)

The buildings Sho Me Technologies lists in PeeringDB, and how many of the exchanges in each it's on.

United States Netrality St. Louis - 900 WalnutSt. Louis 2 of 4
United States Netrality Kansas City - 1102 GrandKansas City 1 of 2