Frankfurt hosting, with the evidence attached

The European Central Bank, the exchange and the densest concentration of banking supervision on the continent sit here, with DE-CIX humming away in the same skyline. Vendor questionnaires are a normal part of the week, and a firm that cannot answer one loses the mandate rather than the argument.

So this page is written as evidence. What the commitments actually are, what the numbers actually say, which parts of a site the exchange next door cannot help with, and how a trade-fair week behaves.

We publish 10–35 ms round trip for Western and Northern Europe to our London origin, described as indicative for a well-connected consumer network rather than as a guarantee, because that is what it is. Set against the 800 ms Google treats as a good time to first byte, the distance is spending a few per cent of the budget.

The rest of the answer is architectural: NVMe storage, a LiteSpeed cache built into the server and OPcache on current PHP 8.x, so a cached page is answered without booting the application and an uncached one is still cheap to build. A reviewer can verify the cache claim in one request by reading the response header.

Trade-fair traffic is people skimming company profiles between halls, which is the most cacheable behaviour there is. Those pages serve pre-built and never touch the database, so the busiest week of your year should be the most boring week for the server. Bandwidth runs 500 GB a month on Sprint, 1 TB on Turbo and 2 TB on Nitro.

Check the ratio before the fair rather than during it. Request your top ten URLs twice each, record which return a cache hit on the second attempt, and fix whatever is blocking the rest — usually a session cookie set sitewide or a personalisation snippet in the header. Ten minutes of work, done in a quiet week.