ixreport

measurement.network

AS211286

Tobias Fiebig

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

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

Make the changes on measurement.network'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 measurement.network's PeeringDB record. Add one entry per connection with these values.

  1. Germany Community-IX Berlin, Frankfurt, Germany · PeeringDB 1329From its website members list

    The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

Exchanges over time

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

Map

Where measurement.network'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 2G, at the 2 of 3 exchanges with a speed in PeeringDB or the exchange's IX-F export.

Germany BCIX Berlin, Germany 193.178.185.176 2001:7f8:19:1:0:3:3956:1 1G 16 routes Both
Germany Community-IX Berlin, Frankfurt, Germany Not in PeeringDB
Netherlands NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands 193.239.119.46 2001:7f8:13::a521:1286:1 1G Yes Both

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

These exchanges have a switch in a facility where measurement.network lists itself in PeeringDB, but don't have measurement.network 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 measurement.network lists in PeeringDB, and how many of the exchanges in each it's on.

Germany Speedbone BerlinBerlin 3 of 6
Germany WIIT Datacenter DUS1, DUS2, DUS3, DUS4, DUS6, DUS7Düsseldorf 0 of 6