ixreport

FurITSystems

AS215168 · FurIT Systems

Akos Miklos

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

Tools: Where can I peer with FurITSystems? · Where should FurITSystems peer next? · Compare FurITSystems with another network

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

PeeringDB fix list Printable page · CSV

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

Make the changes on FurITSystems'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 FurITSystems'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:4880:1
    SpeedNot published
    RS peerYes

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. United States EVIX Fremont, United States · PeeringDB 2274
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDBnone206.81.104.12
    • In the entry with IPv6 2602:fed2:fff:ffff::12: set IPv4 to 206.81.104.12 (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

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 FurITSystems'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 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:4880:1 Yes Not in PeeringDB
Switzerland CHIX-CH Frauenfeld, Switzerland 185.1.59.179 2001:7f8:cc:333:0:21:5168:1 Yes PeeringDB
United States EVIXVIX Fremont, United States 2602:fed2:fff:ffff::12 1G Down Both IPv4 not in PeeringDB
Switzerland FogIXP Avers, Switzerland 2001:7f8:ca:1:0:21:5168:1 1G Yes Both

FurITSystems lists no facilities in PeeringDB.