ixreport

Servperso Systems Transit 2

AS208210

Servperso Systems

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

Tools: Where can I peer with Servperso Systems Transit 2? · Where should Servperso Systems Transit 2 peer next? · Compare Servperso Systems Transit 2 with another network

This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

4 things to fix in Servperso Systems Transit 2's PeeringDB record, from what its exchanges publish: 1 to add, 3 to correct. As of 2026-11-19 18:41 UTC.

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

  1. Switzerland 4b42 Internet Exchange Point Zurich, Switzerland · PeeringDB 2447From its IX-F export and website members list
    IPv4–
    IPv62001:7f8:d0::3:2d52:1
    SpeedNot published
    RS peerYes

Correct these entries (3)

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 Dusseldorf Düsseldorf, Germany · PeeringDB 1214
    ProblemPeeringDB hasThe export has
    Port speed differs1G200G
    • In the entry with IPv4 185.1.170.200: set Speed to 200000 (200G) (now 1000).
  2. Germany DE-CIX Hamburg Hamburg, Germany · PeeringDB 74
    ProblemPeeringDB hasThe export has
    Port speed differs1G200G
    • In the entry with IPv4 185.1.210.178: set Speed to 200000 (200G) (now 1000).
  3. Germany DE-CIX Munich Munich, Germany · PeeringDB 248
    ProblemPeeringDB hasThe export has
    Port speed differs1G200G
    • In the entry with IPv4 185.1.208.186: set Speed to 200000 (200G) (now 1000).

Exchanges over time

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

Map

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

Switzerland 4b42 Internet Exchange Point Zurich, Switzerland 2001:7f8:d0::3:2d52:1 Yes Not in PeeringDB
Germany DE-CIX Dusseldorf Düsseldorf, Germany 185.1.170.200 2001:7f8:9e:0:3:2d52:0:1 1G 134 routes Both Speed differs
Germany DE-CIX Hamburg Hamburg, Germany 185.1.210.178 2001:7f8:3d:0:3:2d52:0:1 1G 134 routes Both Speed differs
Germany DE-CIX Munich Munich, Germany 185.1.208.186 2001:7f8:44:0:3:2d52:0:1 1G 134 routes Both Speed differs

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

These exchanges have a switch in a facility where Servperso Systems Transit 2 lists itself in PeeringDB, but don't have Servperso Systems Transit 2 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 (1)

The buildings Servperso Systems Transit 2 lists in PeeringDB, and how many of the exchanges in each it's on.

Germany WIIT Datacenter DUS1, DUS2, DUS3, DUS4, DUS6, DUS7Düsseldorf 1 of 6