ixreport

GoFibre

AS205847 · GoFibre

GoFibre Holdings Limited

2Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Network ServicesType
OpenPeering policy
2Using the route servers
1To fix in PeeringDB
4Facilities in PeeringDB

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

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

PeeringDB fix list Printable page · CSV

One thing to fix in GoFibre's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-11-19 18:41 UTC.

Make the changes on GoFibre'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 (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 Kingdom LINX LON1 London, United Kingdom · PeeringDB 18
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 50G100G + 50G
    • In the entry with IPv4 195.66.228.1: set Speed to 100000 (100G) (now 50000).

Exchanges over time

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

Map

Where GoFibre'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 120G across 2 exchanges.

United Kingdom LINX LON1 London, United Kingdom 195.66.227.208
195.66.228.1
2001:7f8:4::3:2417:1
2001:7f8:4::3:2417:2
2 × 50G 6 routes Both Speed differs
United Kingdom LINX Scotland Scotland, United Kingdom 195.66.246.60
195.66.246.200
2001:7f8:4:3:0:3:2417:1
2001:7f8:4:3:0:3:2417:2
2 × 10G Up, 0 routes Both

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

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

United Kingdom NCL-IXNewcastle, United Kingdom 11 Stellium 1
Facilities (4)

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

United Kingdom DataVita DV1 LanarkshireGlasgow 1 of 1
United Kingdom Pulsant Edinburgh SC-1 (South Gyle)Edinburgh 1 of 1
United Kingdom Stellium 1Newcastle 0 of 1
United Kingdom Brightsolid Aberdeen Data CentreAberdeen No exchange