ixreport

OzarksGo, LLC

AS395662 · OzarksGo

2Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
NSPType
OpenPeering policy
2Using the route servers
1To fix in PeeringDB
3Facilities in PeeringDB

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

Make the changes on OzarksGo, 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
    Port speed differs100G200G
    • In the entry with IPv4 206.51.7.46: set Speed to 200000 (200G) (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 OzarksGo, 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 300G across 2 exchanges.

United States Equinix Dallas Dallas, United States 206.223.118.188 2001:504:0:5:0:39:5662:1 200G Yes PeeringDB
United States KCIX Kansas City, United States 206.51.7.46 2001:504:1b:1::46 100G Yes Both Speed differs

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

These exchanges have a switch in a facility where OzarksGo, LLC lists itself in PeeringDB, but don't have OzarksGo, 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 Equinix DA3 - Dallas; Netrality Kansas City - 1102 Grand
United States DE-CIX DallasDallas, United States 177 Equinix DA3 - Dallas
United States MegaIX DallasDallas, United States 30 Equinix DA3 - Dallas
United States DFW-IXDallas, United States 11 Equinix DA3 - Dallas
United States MUS-IXDallas, TX, United States 11 Equinix DA3 - Dallas
Facilities (3)

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

United States Equinix DA3 - DallasDallas 1 of 6
United States Netrality Kansas City - 1102 GrandKansas City 1 of 2
United States OzarksGo FayettevilleFayetteville No exchange