ixreport

Ops One AG

AS198249

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

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

Make the changes on Ops One AG'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. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    Port speed differs1G10G
    • In the entry with IPv4 80.81.193.224: set Speed to 10000 (10G) (now 1000).

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 Ops One AG'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 11G across 2 exchanges.

Germany DE-CIX Frankfurt Frankfurt, Germany 80.81.193.224 2001:7f8::3:669:0:1 1G 9 routes Both Speed differs
Switzerland SwissIX Zurich, Switzerland 91.206.52.199 2001:7f8:24::c7 10G 9 routes Both

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

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

Switzerland FogIXPAvers, Switzerland 532 NTT Zurich 1 Data Center (ZRH1)
Switzerland CHIX-CHFrauenfeld, Switzerland 66 NTT Zurich 1 Data Center (ZRH1)
Switzerland Free-IX SwitzerlandGeneva, Zurich, Lugano, Switzerland 21 NTT Zurich 1 Data Center (ZRH1)
Switzerland Community-IX.chZurich, Switzerland 18 NTT Zurich 1 Data Center (ZRH1)
Switzerland FogIXP ZurichZurich, Switzerland 9 NTT Zurich 1 Data Center (ZRH1)
United States Global Peer ExchangeWashington, United States 6 NTT Zurich 1 Data Center (ZRH1)
Facilities (1)

The buildings Ops One AG lists in PeeringDB, and how many of the exchanges in each it's on.

Switzerland NTT Zurich 1 Data Center (ZRH1)Rümlang 1 of 7