ixreport

FruburyNet

AS199109 · Guy Fenn-Newbury

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

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

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

PeeringDB fix list Printable page · CSV

3 things to fix in FruburyNet's PeeringDB record, from what its exchanges publish: 1 to add, 2 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on FruburyNet'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 FruburyNet'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:9c5:1
    SpeedNot published
    RS peerYes

Correct these entries (2)

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. Netherlands INTERIX Amsterdam, Netherlands · PeeringDB 3990
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDBnone185.1.184.236
    • In the entry with IPv6 2001:7f8:134::ec: set IPv4 to 185.1.184.236 (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.

  2. United Kingdom LONAP London, United Kingdom · PeeringDB 53
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDBnone5.57.82.232
    • In the entry with IPv6 2001:7f8:17::3:9c5:1: set IPv4 to 5.57.82.232 (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

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

Map

Where FruburyNet'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 104G, at the 5 of 6 exchanges with a speed in PeeringDB or the exchange's IX-F export.

Switzerland 4b42 Internet Exchange Point Zurich, Switzerland 2001:7f8:d0::3:9c5:1 Yes Not in PeeringDB
Switzerland FogIXP Avers, Switzerland 2001:7f8:ca:1:0:19:9109:1 1G Yes Both
Netherlands INTERIX Amsterdam, Netherlands 2001:7f8:134::ec 100G 1 routes Both IPv4 not in PeeringDB
Germany ixFabric - Frankfurt Frankfurt, Germany 2a0e:8f01:1000:24::265 1G Yes PeeringDB
United Kingdom ixFabric - London London, United Kingdom 2a0e:8f01:1000:10::169 1G Yes PeeringDB
United Kingdom LONAP London, United Kingdom 2001:7f8:17::3:9c5:1 1G Yes Both IPv4 not in PeeringDB

FruburyNet lists no facilities in PeeringDB.