ixreport

Verus Corporation, Inc.

AS26156 · Verus, LLC

6Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
EnterpriseType
OpenPeering policy
6Using the route servers
1To fix in PeeringDB
1Facility in PeeringDB

Tools: Where can I peer with Verus Corporation, Inc.? · Where should Verus Corporation, Inc. peer next? · Compare Verus Corporation, Inc. with another network

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

One thing to fix in Verus Corporation, Inc.'s PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-11-19 18:41 UTC.

Make the changes on Verus Corporation, Inc.'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 differs10G1G
    • In the entry with IPv4 206.51.7.66: set Speed to 1000 (1G) (now 10000).

Exchanges over time

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

Map

Where Verus Corporation, Inc.'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 60G across 6 exchanges.

United States FCIX Fremont, United States 206.80.238.55 2001:504:91::55 10G Yes Both
United States IX-Denver Denver, United States 206.53.175.212 2001:504:58::212 10G Yes Both
United States KCIX Kansas City, United States 206.51.7.66 2001:504:1b:1::66 10G Yes Both Speed differs
United States MICE Minneapolis, MN, United States 206.108.255.33 2001:504:27::662c:0:1 10G 2 routes Both
United States QCIX Davenport, United States 206.83.43.15 2001:504:9b::15 10G Yes Both
United States SIX Seattle Seattle, United States 206.81.81.162 2001:504:16::662c 10G Yes Both

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

These exchanges have a switch in a facility where Verus Corporation, Inc. lists itself in PeeringDB, but don't have Verus Corporation, Inc. 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.

United States SIX Seattle (Jumbo)Seattle, United States 69 Cologix MIN1
Facilities (1)

The buildings Verus Corporation, Inc. lists in PeeringDB, and how many of the exchanges in each it's on.

United States Cologix MIN1Minneapolis 5 of 6