ixreport

Socket Telecom, LLC

AS4581 · Socket Internet Services

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

Tools: Where can I peer with Socket Telecom, LLC? · Where should Socket Telecom, LLC peer next? · Compare Socket Telecom, LLC with another network

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

One thing to fix in Socket Telecom, LLC's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on Socket Telecom, LLC'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 KCIX Kansas City, United States · PeeringDB 249
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:504:1b:1::88
    • In the entry with IPv4 206.51.7.88: set IPv6 to 2001:504:1b:1::88 (now empty).

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 Socket Telecom, LLC'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.88 100G Both IPv6 not in PeeringDB
United States STLIX Saint Louis, MO, United States 206.83.12.27 2001:504:98::27 100G Both

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

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