ixreport

Fibrus

AS202282 · Fibrus

FIBRUS NETWORKS LTD

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

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

Make the changes on Fibrus'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 (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. United Kingdom LINX LON1 London, United Kingdom · PeeringDB 18
    ProblemPeeringDB hasThe export has
    Port speed differs100G200G
    • In the entry with IPv4 195.66.226.179: set Speed to 200000 (200G) (now 100000).
  2. United Kingdom LONAP London, United Kingdom · PeeringDB 53
    ProblemPeeringDB hasThe export has
    Port speed differs100G200G
    • In the entry with IPv4 5.57.82.110: set Speed to 200000 (200G) (now 100000).

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

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 Fibrus'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 300G across 3 exchanges.

United Kingdom LINX LON1 London, United Kingdom 195.66.226.179 2001:7f8:4::3:162a:2 100G 15 routes Both Speed differs
United Kingdom LINX Manchester Manchester, United Kingdom 195.66.244.96 2001:7f8:4:2:0:3:162a:1 100G 16 routes Both
United Kingdom LONAP London, United Kingdom 5.57.82.110 2001:7f8:17::3:162a:1 100G 16 routes Both Speed differs

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

These exchanges have a switch in a facility where Fibrus lists itself in PeeringDB, but don't have Fibrus 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.

Netherlands NL-ixAmsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands 672 Telehouse - London (Docklands North Two)
United Kingdom LINX LON2London, United Kingdom 315 Telehouse - London (Docklands North Two)
France nineAmsterdam, Bordeaux, Frankfurt, Genève, Lille, London, Lyon, Marseille, Milano, Montpellier, Paris, Zurich, France 160 Telehouse - London (Docklands North Two)
United Kingdom Equinix ManchesterManchester, United Kingdom 19 Equinix MA4 - Manchester, Synergy House
Facilities (2)

The buildings Fibrus lists in PeeringDB, and how many of the exchanges in each it's on.

United Kingdom Telehouse - London (Docklands North Two)London 2 of 5
United Kingdom Equinix MA4 - Manchester, Synergy HouseManchester 0 of 1