ixreport

Your.Org

AS19255

Your.Org, Inc.

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

Tools: Where can I peer with Your.Org? · Where should Your.Org peer next? · Compare Your.Org with another network

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

One thing to fix in Your.Org's PeeringDB record, from what its exchanges publish: 1 to add. As of 2026-11-19 12:40 UTC.

Make the changes on Your.Org's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Add these exchanges (1)

On the exchange's own member list, but not in Your.Org's PeeringDB record. Add one entry per connection with these values.

  1. Netherlands AMS-IX Amsterdam, Netherlands · PeeringDB 26From its IX-F export and website members list
    IPv480.249.215.76
    IPv62001:7f8:1::a501:9255:1
    Speed10000 Mbps (10G)
    RS peerNo

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

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 Your.Org'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 650G across 6 exchanges.

Netherlands AMS-IX Amsterdam, Netherlands 80.249.215.76 2001:7F8:1::A501:9255:1 10G Not in PeeringDB
United States ChIX Chicago, United States 206.41.110.60
206.41.110.61
206.41.110.103
206.41.110.104
2001:504:41:110::60
2001:504:41:110::61
2001:504:41:110::103
2001:504:41:110::104
4 × 100G Yes Both
Ukraine DTEL-IX Kiev, Ukraine 193.25.180.228 2001:7f8:63::e4 10G Yes PeeringDB
United States Equinix Chicago Chicago, United States 208.115.136.107
208.115.137.181
2001:504:0:4:0:1:9255:2
2001:504:0:4:0:1:9255:3
2 × 100G Yes PeeringDB
Netherlands GNM-IX Amsterdam, Netherlands 178.18.236.211
178.18.236.238
2a03:5f80:4:2::236:211
2a03:5f80:4:2::236:238
2 × 10G Yes Both
Romania InterLAN-IX Bucharest, Romania 86.104.125.188 2001:7f8:64:225:0:1:9255:1 10G Yes Both

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

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

Facilities (2)

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

United States Equinix CH1/CH2/CH4 - ChicagoChicago 2 of 9
United States Digital Realty CH1 - ChicagoElk Grove Village 0 of 2