Questions, answered
What teams usually ask us before they move traffic onto the network.
Where does the network run?
The core is in Amsterdam, with backbone sites in 41 cities across Europe and North America. Edge sites sit inside the major internet exchanges in each region, so most users reach us in under 10 ms.
How is a route chosen?
Every edge site probes every path to every destination continuously. Routes are recalculated every few seconds from the measured latency and loss, not from static weights.
If a path degrades, traffic is moved before sessions time out. Your users see a slightly different round trip, not an error.
Do we need to change our application?
No. You point DNS or announce your prefixes to us, and traffic starts arriving at our edge. Your servers keep the same addresses and certificates.
How long does onboarding take?
A first route is usually live within a week. Larger moves are done region by region, with a rollback path at every step.
Who answers when something breaks?
Network engineers, around the clock. There is no first-line script to get through: the person who picks up can read the routers.
What do you do with our traffic data?
We keep aggregated flow metadata for 14 days to run the network, and we never inspect payloads. The details are on the security page.
How is the service priced?
By committed bandwidth per region, with bursting above the commitment billed at the same rate. There are no per-request fees.
How do we get started?
Email info@tnffx.com with where your users and servers are. An engineer will reply with the routes we would use and the latency you can expect.