ixreport

TIMOSCHAFFERT

AS207530 · TSCHAFFERT

Timo Schaffert

9Exchanges, of which 1 VIX
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
NSPType
OpenPeering policy
9Using the route servers
1To fix in PeeringDB
0Facilities in PeeringDB

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

Make the changes on TIMOSCHAFFERT'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. France nine Amsterdam, Bordeaux, Frankfurt, Genève, Lille, London, Lyon, Marseille, Milano, Montpellier, Paris, Zurich, France · PeeringDB 4705
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDBnone185.1.14.152
    • In the entry with IPv6 2001:7f8:12e::20:7530:1: set IPv4 to 185.1.14.152 (now empty).

    PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.

Exchanges over time

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

In the last 30 days TIMOSCHAFFERT joined 0 exchanges and left 1. Growing networks

Left

Map

Where TIMOSCHAFFERT'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 18G across 9 exchanges.

United States EVIXVIX Fremont, United States 2602:fed2:fff:ffff:6::10e 1G 3 routes Both
Netherlands ixFabric - Amsterdam Amsterdam, Netherlands 2a0e:8f01:1000:11::205 1G Yes PeeringDB
Germany ixFabric - Frankfurt Frankfurt, Germany 2a0e:8f01:1000:24::253 1G Yes PeeringDB
United States ixFabric - Fremont Fremont, United States 2a0e:8f01:1000:22::13f 1G Yes PeeringDB
United States ixFabric - Kansas Kansas, United States 2a0e:8f01:1000:32::11f 1G Yes PeeringDB
United Kingdom ixFabric - London London, United Kingdom 2a0e:8f01:1000:10::1bb 1G Yes PeeringDB
United States ixFabric - New York New York, United States 2401:2060:b109:156::12d 1G Yes PeeringDB
Switzerland ixFabric - Zurich Zurich, Switzerland 2a0e:8f01:1000:25::172 1G Yes PeeringDB
France nine Amsterdam, Bordeaux, Frankfurt, Genève, Lille, London, Lyon, Marseille, Milano, Montpellier, Paris, Zurich, France 2001:7f8:12e::20:7530:1 10G Yes Both IPv4 not in PeeringDB

TIMOSCHAFFERT lists no facilities in PeeringDB.

Recent changes Search them

  • Oct 20, 2026 [PDB] AS207530 TIMOSCHAFFERT left ixFabric - Dusseldorf
  • Oct 14, 2026 [PDB] AS207530 TIMOSCHAFFERT left LOCIX DUSSELDORF