Who keeps the chart.

It does not decide — the internet does, and that is the point. The same address is announced from all sixteen stations, and each network along the way picks the route it considers shortest under BGP. A visitor in Tampere reaches Helsinki because their ISP's path to Helsinki is the cheapest one it knows.

The honest caveat: BGP measures hops and policy, not milliseconds, so occasionally a route is short on paper and slow in practice. We watch for that, and when we find one we adjust our announcements rather than pretending it cannot happen.

Yes. SAN certificates are issued and renewed automatically by default, which suits most people. If you need your own chain, upload a PEM bundle in the dashboard and it reaches every station in under a minute.

You can also pin a stricter profile than our default — a minimum of TLS 1.3, a restricted cipher list, or mandatory OCSP stapling — per hostname rather than for the whole account.

The station withdraws its BGP announcement, so within a few seconds that address stops being routed there and traffic lands at the next-nearest site. Sessions in flight are cut and retried by the client; sessions that have not started never notice.

In practice this means a station failure costs affected users a handful of milliseconds of extra latency, not an outage. The capacity is sized so that the loss of any one core site is absorbed by its neighbours.

Change the CNAME back. Your origin was serving the content the whole time — we never became the only copy of anything, and there is no proprietary format to unpick.

Configuration exports as JSON, logs are yours to keep, and we do not hold the last month hostage behind a cancellation notice. A trial that ends simply stops.