ixreport

Fastrack Technology

AS58580 · Managed Data Solutions

9Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
NSPType
SelectivePeering policy
8Using the route servers
7To fix in PeeringDB
7Facilities in PeeringDB

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

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

PeeringDB fix list Printable page · CSV

7 things to fix in Fastrack Technology's PeeringDB record, from what its exchanges publish: 7 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on Fastrack Technology'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 (7)

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. ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7fa:11:4:0:e4d4:0:1 2001:7fa:11:4:0:e4d4:0:2
    • In the entry with IPv4 218.100.52.112: set IPv6 to 2001:7fa:11:4:0:e4d4:0:1 (now empty).
    • In the entry with IPv4 218.100.52.116: set IPv6 to 2001:7fa:11:4:0:e4d4:0:2 (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 LINX LON1 London, United Kingdom · PeeringDB 18
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:4::e4d4:1
    • In the entry with IPv4 195.66.226.202: set IPv6 to 2001:7f8:4::e4d4:1 (now empty).
  3. United States MegaIX Ashburn Ashburn, United States · PeeringDB 1178
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2606:a980:0:3::30
    • In the entry with IPv4 206.53.170.48: set IPv6 to 2606:a980:0:3::30 (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.

  4. Australia MegaIX Melbourne Melbourne, Australia · PeeringDB 779
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:dea:0:30::87
    • In the entry with IPv4 103.26.71.135: set IPv6 to 2001:dea:0:30::87 (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.

  5. United States MegaIX Seattle Seattle, United States · PeeringDB 1174
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2606:a980:0:4::12
    • In the entry with IPv4 206.53.171.18: set IPv6 to 2606:a980:0:4::12 (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.

  6. Singapore MegaIX Singapore Singapore, Singapore · PeeringDB 965
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:ded::1b
    • In the entry with IPv4 103.41.12.27: set IPv6 to 2001:ded::1b (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.

  7. Australia MegaIX Sydney Sydney, Australia · PeeringDB 780
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:dea:0:10::50
    • In the entry with IPv4 103.26.68.80: set IPv6 to 2001:dea:0:10::50 (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

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

Map

Where Fastrack Technology'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 82G across 9 exchanges.

United States Equinix Ashburn Ashburn, United States 206.126.237.121 10G Yes PeeringDB
Australia IX Australia Sydney (NSW-IX) Sydney, Australia 218.100.52.112
218.100.52.116
2 × 10G Yes Both IPv6 not in PeeringDB
United Kingdom LINX LON1 London, United Kingdom 195.66.226.202 10G 7 routes Both IPv6 not in PeeringDB
United States MegaIX Ashburn Ashburn, United States 206.53.170.48 10G Yes Both IPv6 not in PeeringDB
Australia MegaIX Melbourne Melbourne, Australia 103.26.71.135 1G Both IPv6 not in PeeringDB
United States MegaIX Seattle Seattle, United States 206.53.171.18 10G Yes Both IPv6 not in PeeringDB
Singapore MegaIX Singapore Singapore, Singapore 103.41.12.27 1G Yes Both IPv6 not in PeeringDB
Australia MegaIX Sydney Sydney, Australia 103.26.68.80 10G Yes Both IPv6 not in PeeringDB
United States SIX Seattle Seattle, United States 206.81.80.76 10G Yes Both

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

These exchanges have a switch in a facility where Fastrack Technology lists itself in PeeringDB, but don't have Fastrack Technology 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 Equinix LD8 - London, Docklands
Singapore Equinix SingaporeSingapore, Singapore 473 Equinix SG3 - Singapore
United Kingdom LINX LON2London, United Kingdom 315 Equinix LD8 - London, Docklands; Equinix LD6 - London, Slough
United Kingdom LONAPLondon, United Kingdom 311 Equinix LD8 - London, Docklands; Equinix LD6 - London, Slough
Poland 1-IX EUNew-York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Hong Kong, Poland 283 Equinix LD8 - London, Docklands
Singapore SGIXSingapore, Singapore 277 Equinix SG3 - Singapore
Australia EdgeIX - SydneySydney, Australia 230 Equinix SY1/SY2 - Sydney; Equinix SY3 - Sydney; NEXTDC S1
Australia Equinix SydneySydney, Australia 219 Equinix SY1/SY2 - Sydney; Equinix SY3 - Sydney
Bulgaria NetIXSofia, Bulgaria 204 Equinix LD8 - London, Docklands; Equinix SY1/SY2 - Sydney; Equinix SY3 - Sydney and 2 more
Singapore BBIX SingaporeSingapore, Singapore 169 Equinix SG3 - Singapore
Singapore DE-CIX ASEANSingapore, Singapore 140 Equinix SG3 - Singapore
Australia IX Australia Melbourne (VIC-IX)Melbourne, Australia 106 NEXTDC M1
Australia EdgeIX - MelbourneMelbourne, Australia 73 NEXTDC M1
United Kingdom Equinix LondonLondon, United Kingdom 53 Equinix LD8 - London, Docklands; Equinix LD6 - London, Slough
Türkiye EURASIA-IX.NETIstanbul, Türkiye 6 Equinix LD8 - London, Docklands
United States Global Peer ExchangeWashington, United States 6 Equinix LD8 - London, Docklands; Equinix SG3 - Singapore
Australia ixFabricGlobal, Australia 2 Equinix SY3 - Sydney
Facilities (7)

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

United Kingdom Equinix LD8 - London, DocklandsLondon 1 of 9
Singapore Equinix SG3 - SingaporeSingapore 1 of 7
Australia Equinix SY3 - SydneySydney 2 of 6
United Kingdom Equinix LD6 - London, SloughSlough 1 of 5
Australia Equinix SY1/SY2 - SydneySydney 2 of 5
Australia NEXTDC M1Melbourne 1 of 3
Australia NEXTDC S1Sydney 2 of 3