ixreport

7Hoop Network Telecom, LLC

AS63066 · 7Hoop Network

7HOOP NETWORK TELECOM

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

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

This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

4 things to fix in 7Hoop Network Telecom, LLC's PeeringDB record, from what its exchanges publish: 4 to correct. As of 2026-11-19 18:41 UTC.

Make the changes on 7Hoop Network 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 (4)

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 HOUIX Houston, United States · PeeringDB 2835
    ProblemPeeringDB hasThe export has
    Port speed differs200G80G
    • In the entry with IPv4 206.83.136.60: set Speed to 80000 (80G) (now 200000).
  2. United States KCIX Kansas City, United States · PeeringDB 249
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 200G2 × 100G
    • In the entry with IPv4 206.51.7.204: set Speed to 100000 (100G) (now 200000).
    • In the entry with IPv4 206.51.7.225: set Speed to 100000 (100G) (now 200000).
  3. United States SpringIX Springfield, MO, United States · PeeringDB 3195
    ProblemPeeringDB hasThe export has
    Port speed differs200G80G
    • In the entry with IPv4 149.112.4.15: set Speed to 80000 (80G) (now 200000).

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

  4. United States STLIX Saint Louis, MO, United States · PeeringDB 2585
    ProblemPeeringDB hasThe export has
    Port speed differs200G80G
    • In the entry with IPv4 206.83.12.90: set Speed to 80000 (80G) (now 200000).

Exchanges over time

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

Map

Where 7Hoop Network 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 1T across 8 exchanges.

United States HOUIX Houston, United States 206.83.136.60 2001:504:9e::60 200G Both Speed differs
Brazil IX.br (PTT.br) São Paulo São Paulo/SP, Brazil 187.16.209.198
187.16.221.15
2001:12f8::209:198
2001:12f8::221:15
2 × 10G 13 routes PeeringDB only
United States KCIX Kansas City, United States 206.51.7.204
206.51.7.225
2001:504:1b:1::204
2001:504:1b:1::225
2 × 200G Both Speed differs
United States MICE Minneapolis, MN, United States 206.108.255.223 2001:504:27:0:3:4d78:0:1 10G 69 routes Both
United States SIX Seattle Seattle, United States 206.81.82.22 2001:504:16::f65a 10G Both
United States SIX Seattle (Jumbo) Seattle, United States 149.112.98.22 2001:504:16:1::f65a 10G Both
United States SpringIX Springfield, MO, United States 149.112.4.15 2001:504:100::15 200G Both Speed differs
United States STLIX Saint Louis, MO, United States 206.83.12.90 2001:504:98::90 200G Both Speed differs

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

These exchanges have a switch in a facility where 7Hoop Network Telecom, LLC lists itself in PeeringDB, but don't have 7Hoop Network 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 Ascenty SPO01 - São Paulo; Ascenty SPO02 - São Paulo; Ascenty SPO03 - São Paulo and 1 more
Australia MegaIX MelbourneMelbourne, Australia 152 Ascenty SPO02 - São Paulo
United States IX-DenverDenver, United States 96 1530 SWIFT - NOCIX
United States F4IX MCIKansas City, United States 67 1530 SWIFT - NOCIX
Brazil DE-CIX Sao PauloSao Paulo, Brazil 58 Ascenty SPO04 - São Paulo
United States HN Internet Exchange (Main)North Kansas City, United States 27 1530 SWIFT - NOCIX
United States DesMoinesIXDes Moines, United States 11 1530 SWIFT - NOCIX
United States Global Peer ExchangeWashington, United States 6 Ascenty SPO02 - São Paulo
United States SIOUIXSioux City, United States 4 1530 SWIFT - NOCIX
United States MOCIXKansas City, United States 3 1530 SWIFT - NOCIX
Facilities (5)

The buildings 7Hoop Network Telecom, LLC lists in PeeringDB, and how many of the exchanges in each it's on.

United States 1530 SWIFT - NOCIXNorth Kansas City 7 of 13
Brazil Ascenty SPO02 - São PauloOsasco 1 of 4
Brazil Ascenty SPO04 - São PauloOsasco 0 of 2
Brazil Ascenty SPO01 - São PauloOsasco 0 of 1
Brazil Ascenty SPO03 - São PauloOsasco 0 of 1