ixreport

Fibrecast

AS198690 · Fibrecast

FIBRECAST LTD

3Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
–Type
OpenPeering policy
3Using the route servers
3To fix in PeeringDB
3Facilities in PeeringDB

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

Make the changes on Fibrecast'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 (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. United Kingdom LINX LON1 London, United Kingdom · PeeringDB 18
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:4::3:822:1
    Port speed differs10G4G
    • In the entry with IPv4 195.66.228.103: set IPv6 to 2001:7f8:4::3:822:1 (now empty); set Speed to 4000 (4G) (now 10000).
  2. United Kingdom LINX Scotland Scotland, United Kingdom · PeeringDB 745
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:4:3:0:3:822:1
    • In the entry with IPv4 195.66.246.40: set IPv6 to 2001:7f8:4:3:0:3:822:1 (now empty).
  3. United Kingdom LONAP London, United Kingdom · PeeringDB 53
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:17::3:822:1
    • In the entry with IPv4 5.57.82.208: set IPv6 to 2001:7f8:17::3:822:1 (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

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 Fibrecast'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 30G across 3 exchanges.

United Kingdom LINX LON1 London, United Kingdom 195.66.228.103 10G 6 routes Both IPv6 not in PeeringDBSpeed differs
United Kingdom LINX Scotland Scotland, United Kingdom 195.66.246.40 10G 6 routes Both IPv6 not in PeeringDB
United Kingdom LONAP London, United Kingdom 5.57.82.208 10G 6 routes Both IPv6 not in PeeringDB

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

These exchanges have a switch in a facility where Fibrecast lists itself in PeeringDB, but don't have Fibrecast 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 GNM-IXAmsterdam, Netherlands 741 Telehouse - London (Docklands North)
Netherlands NL-ixAmsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands 672 Telehouse - London (Docklands North)
United Kingdom LINX LON2London, United Kingdom 315 Telehouse - London (Docklands North)
Bulgaria NetIXSofia, Bulgaria 204 Telehouse - London (Docklands North)
France nineAmsterdam, Bordeaux, Frankfurt, Genève, Lille, London, Lyon, Marseille, Milano, Montpellier, Paris, Zurich, France 160 Telehouse - London (Docklands North)
United Kingdom Kent Internet Exchange PointKent, United Kingdom 102 Telehouse - London (Docklands North)
Romania Balcan-IXBucharest, Romania 29 Telehouse - London (Docklands North)
Türkiye EURASIA-IX.NETIstanbul, Türkiye 6 Telehouse - London (Docklands North)
United States Global Peer ExchangeWashington, United States 6 Telehouse - London (Docklands North)
Facilities (3)

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

United Kingdom Telehouse - London (Docklands North)London 2 of 11
United Kingdom Pulsant Edinburgh SC-1 (South Gyle)Edinburgh 1 of 1
United Kingdom Brightsolid Dundee Data CentreDundee No exchange