A long list of cities looks good on a hosting site. Before you count them, ask what stands behind each one: whose building it is, who is on the floor at night, how many carriers the site has, and whether the cities are joined by the provider's own backbone or each one buys its transit alone. Some providers have good answers for every city. Many have a few racks and one or two uplinks per site, and that is what we decided not to build.
All our servers are in Sofia, and the money went into the network out of Sofia: Juniper MX304 routers at the border, ten transit carriers, peering at more than 25 European exchanges, more than 100 PNI ports into content, cloud and hosting networks, and our own DWDM wavelengths to the nine other points of presence. Those nine are network sites: routers, exchange ports and, in five of them, a scrubbing cluster. No customer server runs there.
Distance sets a floor. Light in fibre needs about 1 ms of round trip for every 100 km, so Frankfurt can never be closer to Sofia than about 14 ms, or London than about 20. Above that floor the path decides: how far the fibre wanders, how many networks the packet crosses, whether it is handed over at an exchange or carried by a transit carrier, and whether the route is chosen for speed or for the fewest AS hops. A server in a thinly connected site can be closer on the map and still take the long way round. From our network it is about 31 ms to Frankfurt and 42 ms to London, as the table below shows.
With one site, what a server needs can be next to it. The warehouse of parts and whole servers and the engineers on the floor are in the building where your server runs. An attack that enters the backbone in another city is dropped at the cluster there, before it heads for Sofia.
Sometimes one site in Sofia is the wrong answer. If your service has to survive losing a whole city, it needs a copy in another one. If your users are mostly in Western Europe, a server in Frankfurt, Amsterdam or London is 30 to 40 ms closer to them than one in Sofia, and for games, voice or trading that decides it. Sofia makes sense when your users are spread over Central and Eastern Europe, the Balkans and Turkey, with the big Western exchanges still 31 to 42 ms away.