FUSE2
AS20832 · Fuse 2 Communications
Tools: Where can I peer with FUSE2? · Where should FUSE2 peer next? · Compare FUSE2 with another network
This network elsewhere: its registry history on RIR Tracker
PeeringDB fix list Printable page · CSV
One thing to fix in FUSE2's PeeringDB record, from what its exchanges publish: 1 to check. As of 2026-11-19 12:40 UTC.
Make the changes on FUSE2's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If FUSE2 has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
LINX Manchester Manchester, United Kingdom · PeeringDB 583Not on its IX-F export or website members list
IPv4 195.66.244.112 IPv6 2001:7f8:4:2::5160:1 Speed 1000 Mbps (1G)
Exchanges over time
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 2 |
| Nov 18, 2026 | 2 |
| Nov 17, 2026 | 2 |
| Nov 16, 2026 | 2 |
| Nov 15, 2026 | 2 |
| Nov 14, 2026 | 2 |
| Nov 13, 2026 | 2 |
| Nov 12, 2026 | 2 |
| Nov 11, 2026 | 2 |
| Nov 10, 2026 | 2 |
| Nov 9, 2026 | 2 |
| Nov 8, 2026 | 2 |
| Nov 7, 2026 | 2 |
| Nov 6, 2026 | 2 |
| Nov 5, 2026 | 2 |
| Nov 4, 2026 | 2 |
| Nov 3, 2026 | 2 |
| Nov 2, 2026 | 2 |
| Nov 1, 2026 | 2 |
| Oct 31, 2026 | 2 |
| Oct 30, 2026 | 2 |
| Oct 29, 2026 | 2 |
| Oct 28, 2026 | 2 |
| Oct 27, 2026 | 2 |
| Oct 26, 2026 | 2 |
| Oct 25, 2026 | 2 |
| Oct 24, 2026 | 2 |
| Oct 23, 2026 | 2 |
| Oct 22, 2026 | 2 |
| Oct 21, 2026 | 2 |
| Oct 20, 2026 | 2 |
| Oct 19, 2026 | 2 |
| Oct 18, 2026 | 2 |
| Oct 17, 2026 | 2 |
| Oct 16, 2026 | 2 |
| Oct 15, 2026 | 2 |
| Oct 14, 2026 | 2 |
| Oct 13, 2026 | 2 |
| Oct 12, 2026 | 2 |
| Oct 11, 2026 | 2 |
| Oct 10, 2026 | 2 |
| Oct 9, 2026 | 2 |
| Oct 8, 2026 | 2 |
| Oct 7, 2026 | 2 |
| Oct 6, 2026 | 2 |
| Oct 5, 2026 | 2 |
| Oct 4, 2026 | 2 |
| Oct 3, 2026 | 2 |
Map
Where FUSE2'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.
| LINX LON1 London, United Kingdom | 1G | Both | |
| LINX Manchester Manchester, United Kingdom | 1G | PeeringDB only |
These exchanges have a switch in a facility where FUSE2 lists itself in PeeringDB, but don't have FUSE2 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.
| Equinix ManchesterManchester, United Kingdom | 19 |
Facilities (2)
The buildings FUSE2 lists in PeeringDB, and how many of the exchanges in each it's on.
| Equinix MA1 - Manchester, Williams/KilburnManchester | 1 of 2 | |
| ANS - MAN6Manchester | No exchange |
Recent changes Search them
- Oct 29, 2026 [IXF] AS20832 FUSE2 dropped from LINX Manchester's IX-F list (still in PeeringDB)
- Oct 29, 2026 [WEB] AS20832 FUSE2 dropped from LINX Manchester's website list (still in PeeringDB)