TORNADO
AS49964
TORNADO TELECOM S.R.L.
Tools: Where can I peer with TORNADO? · Where should TORNADO peer next? · Compare TORNADO 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 TORNADO's PeeringDB record, from what its exchanges publish: 1 to add. As of 2026-11-19 12:40 UTC.
Make the changes on TORNADO's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.
Add these exchanges (1)
On the exchange's own member list, but not in TORNADO's PeeringDB record. Add one entry per connection with these values.
-
IPv4 194.53.172.105 IPv6 2001:7f8:26::a504:9964:1 Speed 1000 Mbps (1G) RS peer No PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
Exchanges over time
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 1 |
| Nov 18, 2026 | 1 |
| Nov 17, 2026 | 1 |
| Nov 16, 2026 | 1 |
| Nov 15, 2026 | 1 |
| Nov 14, 2026 | 1 |
| Nov 13, 2026 | 1 |
| Nov 12, 2026 | 1 |
| Nov 11, 2026 | 1 |
| Nov 10, 2026 | 1 |
| Nov 9, 2026 | 1 |
| Nov 8, 2026 | 1 |
| Nov 7, 2026 | 1 |
| Nov 6, 2026 | 1 |
| Nov 5, 2026 | 1 |
| Nov 4, 2026 | 1 |
| Nov 3, 2026 | 1 |
| Nov 2, 2026 | 1 |
| Nov 1, 2026 | 1 |
| Oct 31, 2026 | 1 |
| Oct 30, 2026 | 1 |
| Oct 29, 2026 | 1 |
| Oct 28, 2026 | 1 |
| Oct 27, 2026 | 1 |
| Oct 26, 2026 | 1 |
| Oct 25, 2026 | 1 |
| Oct 24, 2026 | 1 |
| Oct 23, 2026 | 1 |
| Oct 22, 2026 | 1 |
| Oct 20, 2026 | 1 |
| Oct 19, 2026 | 1 |
| Oct 18, 2026 | 1 |
| Oct 17, 2026 | 1 |
| Oct 16, 2026 | 1 |
| Oct 15, 2026 | 1 |
| Oct 14, 2026 | 1 |
| Oct 13, 2026 | 1 |
| Oct 12, 2026 | 1 |
| Oct 11, 2026 | 1 |
| Oct 10, 2026 | 1 |
| Oct 9, 2026 | 1 |
| Oct 8, 2026 | 1 |
| Oct 7, 2026 | 1 |
| Oct 6, 2026 | 1 |
| Oct 5, 2026 | 1 |
| Oct 4, 2026 | 1 |
| Oct 3, 2026 | 1 |
Map
Where TORNADO'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.
| BNIX Brussels, Belgium | 1G | Not in PeeringDB |
These exchanges have a switch in a facility where TORNADO lists itself in PeeringDB, but don't have TORNADO 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 | |
| NetIXSofia, Bulgaria | 204 | |
| BelgiumIXBrussels, Ghent, Leuven, Antwerp, Hasselt, Belgium | 32 | |
| Global Peer ExchangeWashington, United States | 6 |
Facilities (10)
The buildings TORNADO lists in PeeringDB, and how many of the exchanges in each it's on.
| Digital Realty BRU1 - BrusselsBrussels | 1 of 4 | |
| LCL Brussels (Diegem)Brussels | 1 of 3 | |
| LCL AntwerpAntwerp | 0 of 2 | |
| Level(3) BrusselsBrussels | 1 of 2 | |
| antwerpdcAntwerp | 0 of 1 | |
| brusselsdcZaventem | 0 of 1 | |
| nLighten Gent BRU1Merelbeke | 0 of 1 | |
| LCL Wallonia OneGembloux | No exchange | |
| WDCVillers-le-Bouillet | No exchange | |
| Woluwedal 102Sint-Lambrechts-Woluwe | No exchange |