Fastrack Technology
AS58580 · Managed Data Solutions
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.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001: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.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:7f8:4::e4d4:1 - In the entry with IPv4 195.66.226.202: set IPv6 to 2001:7f8:4::e4d4:1 (now empty).
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2606: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.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001: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.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2606: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.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001: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.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001: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
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 9 |
| Nov 18, 2026 | 9 |
| Nov 17, 2026 | 9 |
| Nov 16, 2026 | 9 |
| Nov 15, 2026 | 9 |
| Nov 14, 2026 | 9 |
| Nov 13, 2026 | 9 |
| Nov 12, 2026 | 9 |
| Nov 11, 2026 | 9 |
| Nov 10, 2026 | 9 |
| Nov 9, 2026 | 9 |
| Nov 8, 2026 | 9 |
| Nov 7, 2026 | 9 |
| Nov 6, 2026 | 9 |
| Nov 5, 2026 | 9 |
| Nov 4, 2026 | 9 |
| Nov 3, 2026 | 9 |
| Nov 2, 2026 | 9 |
| Nov 1, 2026 | 9 |
| Oct 31, 2026 | 9 |
| Oct 30, 2026 | 9 |
| Oct 29, 2026 | 9 |
| Oct 28, 2026 | 9 |
| Oct 27, 2026 | 9 |
| Oct 26, 2026 | 9 |
| Oct 25, 2026 | 9 |
| Oct 24, 2026 | 9 |
| Oct 23, 2026 | 9 |
| Oct 22, 2026 | 9 |
| Oct 21, 2026 | 9 |
| Oct 20, 2026 | 9 |
| Oct 19, 2026 | 9 |
| Oct 18, 2026 | 9 |
| Oct 17, 2026 | 9 |
| Oct 16, 2026 | 9 |
| Oct 15, 2026 | 9 |
| Oct 14, 2026 | 9 |
| Oct 13, 2026 | 9 |
| Oct 12, 2026 | 9 |
| Oct 11, 2026 | 9 |
| Oct 10, 2026 | 9 |
| Oct 9, 2026 | 9 |
| Oct 8, 2026 | 9 |
| Oct 7, 2026 | 9 |
| Oct 6, 2026 | 9 |
| Oct 5, 2026 | 9 |
| Oct 4, 2026 | 9 |
| Oct 3, 2026 | 9 |
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.
| Equinix Ashburn Ashburn, United States | 10G | PeeringDB | |
| IX Australia Sydney (NSW-IX) Sydney, Australia | 2 × 10G | Both IPv6 not in PeeringDB | |
| LINX LON1 London, United Kingdom | 10G | Both IPv6 not in PeeringDB | |
| MegaIX Ashburn Ashburn, United States | 10G | Both IPv6 not in PeeringDB | |
| MegaIX Melbourne Melbourne, Australia | 1G | Both IPv6 not in PeeringDB | |
| MegaIX Seattle Seattle, United States | 10G | Both IPv6 not in PeeringDB | |
| MegaIX Singapore Singapore, Singapore | 1G | Both IPv6 not in PeeringDB | |
| MegaIX Sydney Sydney, Australia | 10G | Both IPv6 not in PeeringDB | |
| SIX Seattle Seattle, United States | 10G | Both |
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.
| NL-ixAmsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands | 672 | |
| Equinix SingaporeSingapore, Singapore | 473 | |
| LINX LON2London, United Kingdom | 315 | |
| LONAPLondon, United Kingdom | 311 | |
| 1-IX EUNew-York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Hong Kong, Poland | 283 | |
| SGIXSingapore, Singapore | 277 | |
| EdgeIX - SydneySydney, Australia | 230 | |
| Equinix SydneySydney, Australia | 219 | |
| NetIXSofia, Bulgaria | 204 | |
| BBIX SingaporeSingapore, Singapore | 169 | |
| DE-CIX ASEANSingapore, Singapore | 140 | |
| IX Australia Melbourne (VIC-IX)Melbourne, Australia | 106 | |
| EdgeIX - MelbourneMelbourne, Australia | 73 | |
| Equinix LondonLondon, United Kingdom | 53 | |
| EURASIA-IX.NETIstanbul, Türkiye | 6 | |
| Global Peer ExchangeWashington, United States | 6 | |
| ixFabricGlobal, Australia | 2 |
Facilities (7)
The buildings Fastrack Technology lists in PeeringDB, and how many of the exchanges in each it's on.
| Equinix LD8 - London, DocklandsLondon | 1 of 9 | |
| Equinix SG3 - SingaporeSingapore | 1 of 7 | |
| Equinix SY3 - SydneySydney | 2 of 6 | |
| Equinix LD6 - London, SloughSlough | 1 of 5 | |
| Equinix SY1/SY2 - SydneySydney | 2 of 5 | |
| NEXTDC M1Melbourne | 1 of 3 | |
| NEXTDC S1Sydney | 2 of 3 |