Sho Me Technologies
AS55140
Sho Me Technologies, LLC
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.
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB 206.51.7.78 206.51.7.78 206.51.7.245 IPv6 address missing from PeeringDB 2001:504:1b:1::78 2001:504:1b:1::78 2001:504:1b:1::245 Port speed differs 100G 100G + 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).
-
Problem PeeringDB has The export has Port speed differs 100G 10G - In the entry with IPv4 206.83.12.22: set Speed to 10000 (10G) (now 100000).
Exchanges over time
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 2 |
| Nov 18, 2026 | 2 |
| Nov 17, 2026 | 2 |
| Nov 16, 2026 | 2 |
| Nov 15, 2026 | 2 |
| Nov 14, 2026 | 2 |
| Nov 13, 2026 | 2 |
| Nov 12, 2026 | 2 |
| Nov 11, 2026 | 2 |
| Nov 10, 2026 | 2 |
| Nov 9, 2026 | 2 |
| Nov 8, 2026 | 2 |
| Nov 7, 2026 | 2 |
| Nov 6, 2026 | 2 |
| Nov 5, 2026 | 2 |
| Nov 4, 2026 | 2 |
| Nov 3, 2026 | 2 |
| Nov 2, 2026 | 2 |
| Nov 1, 2026 | 2 |
| Oct 31, 2026 | 2 |
| Oct 30, 2026 | 2 |
| Oct 29, 2026 | 2 |
| Oct 28, 2026 | 2 |
| Oct 27, 2026 | 2 |
| Oct 26, 2026 | 2 |
| Oct 25, 2026 | 2 |
| Oct 24, 2026 | 2 |
| Oct 23, 2026 | 2 |
| Oct 22, 2026 | 2 |
| Oct 21, 2026 | 2 |
| Oct 20, 2026 | 2 |
| Oct 19, 2026 | 2 |
| Oct 18, 2026 | 2 |
| Oct 17, 2026 | 2 |
| Oct 16, 2026 | 2 |
| Oct 15, 2026 | 2 |
| Oct 14, 2026 | 2 |
| Oct 13, 2026 | 2 |
| Oct 12, 2026 | 2 |
| Oct 11, 2026 | 2 |
| Oct 10, 2026 | 2 |
| Oct 9, 2026 | 2 |
| Oct 8, 2026 | 2 |
| Oct 7, 2026 | 2 |
| Oct 6, 2026 | 2 |
| Oct 5, 2026 | 2 |
| Oct 4, 2026 | 2 |
| Oct 3, 2026 | 2 |
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.
| KCIX Kansas City, United States | 100G | Both IPv4 not in PeeringDBIPv6 not in PeeringDBSpeed differs | |
| STLIX Saint Louis, MO, United States | 100G | Both Speed differs |
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.
| NetIXSofia, Bulgaria | 204 | |
| FD-IX - St. LouisSt. Louis, MO, United States | 18 |
Facilities (2)
The buildings Sho Me Technologies lists in PeeringDB, and how many of the exchanges in each it's on.
| Netrality St. Louis - 900 WalnutSt. Louis | 2 of 4 | |
| Netrality Kansas City - 1102 GrandKansas City | 1 of 2 |