Lisbon is our closest city to Portugal, Madeira, the Azores and north-eastern Brazil, and the one where only AMD EPYC builds are offered. Latency floors to 12 destinations, the workloads that fit, honest cases for Madrid, Marseille or Ashburn, and prices from €449 a month.
A Lisbon dedicated server sits on the western edge of Europe, and that is both its strength and its limit. Portugal's capital is the closest of our cities to Portuguese users, to the Atlantic islands and, by straight-line distance, to north-eastern Brazil. It is also the furthest from the middle of the continent, and it is the one city where we offer only AMD EPYC builds, so the entry price is higher than elsewhere. This guide covers who Lisbon serves well, the latency it buys, the workloads that suit it and when Madrid or another city is the better buy.
Portugal itself. Porto is 274 km from Lisbon, a floor of 2.7 ms against 16.7 ms from Frankfurt.
The Atlantic islands. Madeira and the Azores are part of Portugal and of the EU. Funchal is 9.7 ms from Lisbon; Ponta Delgada is 14.5 ms. From Madrid, the next-nearest of our cities, those floors are 14.6 and 19.1 ms; from Marseille, 22.7 and 26.8 ms.
Subsea cables to the south and west. Portugal's coast has become a landing point for new Atlantic systems. EllaLink, launched in June 2021, links Sines in Portugal with Fortaleza in Brazil and has a branch to Funchal. Google's Equiano cable lands at Sesimbra, south of Lisbon, and runs down Africa's west coast to near Cape Town.
Portugal is in the EU, so a Lisbon server keeps the primary copy of your data inside the Union.
The method matches the rest of this series: straight-line distance divided by 100 gives the round-trip floor, then real cable routes add 30 to 50% plus a millisecond or two of router time. Treat the transatlantic rows as rough:
| From Lisbon to | Great-circle | Theoretical floor | Working estimate |
|---|---|---|---|
| Porto | 274 km | 2.7 ms | 5–6 ms |
| Seville | 313 km | 3.1 ms | 5–7 ms |
| Madrid | 502 km | 5.0 ms | 8–10 ms |
| Casablanca | 589 km | 5.9 ms | 9–11 ms |
| Funchal (Madeira) | 973 km | 9.7 ms | 14–17 ms |
| Barcelona | 1,006 km | 10.1 ms | 14–17 ms |
| Ponta Delgada (Azores) | 1,447 km | 14.5 ms | 20–24 ms |
| Paris | 1,453 km | 14.5 ms | 20–24 ms |
| London | 1,585 km | 15.8 ms | 22–26 ms |
| Frankfurt | 1,890 km | 18.9 ms | 26–30 ms |
| Fortaleza | 5,602 km | 56.0 ms | 74–86 ms |
| São Paulo | 7,949 km | 79.5 ms | 104–121 ms |
Read the table in two halves. The top half is Lisbon's home ground: Portugal, Andalusia, Morocco and the islands, all closer from here than from Madrid, Marseille or anywhere further north. Casablanca is 5.9 ms from Lisbon against 8.4 ms from Madrid and 15.6 ms from Marseille.
The bottom half is where honesty matters. Barcelona is 3.4 ms from Marseille and 10.1 ms from Lisbon, so Catalonia belongs to Marseille or Madrid. Paris, London and Frankfurt are 15 to 19 ms away; a service for northern Europe should not be hosted on the Atlantic coast.
Brazil splits too. Fortaleza, where EllaLink lands, has a floor of 56.0 ms from Lisbon against 60.5 ms from Madrid, 62.1 ms from Ashburn and 74.9 ms from Frankfurt. São Paulo is a near tie: 79.5 ms from Lisbon, 76.6 ms from Ashburn. On numbers that close, the actual cable path decides, so measure it before you commit; how to read an MTR report shows what to look for.
Portuguese-market services. Shops, media and SaaS products aimed at Portugal get single-digit round trips to Porto, with the data held inside the country.
Services for Madeira and the Azores. Madeira and the Azores are far from every mainland data-centre city, and a Lisbon server takes about 5 ms off the floor to each compared with Madrid, and more than half compared with Marseille.
A European node for Brazilian users in the north-east. Portuguese-language services with an audience in both Portugal and Brazil can run one origin in Lisbon that sits closest to Portugal and to Fortaleza at the same time. For users concentrated around São Paulo, test against Ashburn first.
Storage-heavy and compute-heavy work. Because every Lisbon build is EPYC-based, the entry server has 24 cores, 48 threads, DDR5 memory and ten NVMe slots. Databases, build farms and transcoding start on modern hardware here.
Your users are in northern or central Europe. Paris, London and Frankfurt sit 15 to 19 ms away on the floor alone.
Your budget is set for a Xeon entry box. Lisbon is offered on the AMD EPYC builds only. If €209 for a dual Xeon on 1 Gbps is the plan, Lisbon is not on the menu. Madrid is: it sells the Xeon tiers, sits 5.0 ms from Lisbon, and still reaches Porto at 4.2 ms. The Madrid dedicated server guide covers that option.
Your audience is in Catalonia or southern France. Marseille is closer to Barcelona than Lisbon by about 7 ms of floor.
You need Latin America beyond Brazil's north-east. For Mexico, Colombia and the south of the continent, Ashburn's floors are lower than any European city's.
Lisbon and Madrid are 502 km apart, a 5.0 ms floor. That makes them a natural Iberian pair: two countries, two failure domains, close enough that replication between them is cheap and either can take the other's traffic during an outage.
The Madrid side can be lighter: unmetered KVM VPS from €29 a month is sold there (not in Lisbon), which makes a cheap monitoring node or test box.
City is a free option at checkout, but Lisbon is the exception: only the AMD EPYC builds can be placed here. Every entry build below has 10 NVMe slots:
| Guaranteed bandwidth | Entry configuration in Lisbon | Per month |
|---|---|---|
| 1 Gbps unmetered | Single EPYC 9254, 24 cores, 128 GB DDR5 | €449 |
| 10 Gbps unmetered | Single EPYC 9254, 24 cores, 128 GB DDR5 | €1,169 |
| 25 Gbps unmetered | Single EPYC 9254, 24 cores, 128 GB DDR5 | €2,244 |
Pick an EPYC build on the tier's page and choose Lisbon in the location selector. Stock differs by city, so a build may be on the shelf here or built to order; most in-stock builds are online within an hour of payment. The unmetered dedicated server buyer's guide compares every tier by cost per delivered terabyte.
Before ordering a Lisbon dedicated server, settle four things:
Teams whose users are in Portugal, Madeira or the Azores, and Portuguese-language services that also reach north-eastern Brazil.
The city itself adds nothing at checkout, but Lisbon is only offered on AMD EPYC builds. The entry server there is a Single EPYC 9254 at €449 a month on 1 Gbps, against €209 for the dual Xeon entry build sold in cities such as Madrid.
For Fortaleza the floor is lower from Lisbon, 56.0 ms against 62.1 ms. For São Paulo the two are close, 79.5 ms against 76.6 ms, so test both routes with your own users before deciding.
Yes. Portugal is an EU member state, so the server and its primary data sit inside the Union. Backups and processor contracts still need their own check.
Madrid sits in the middle of the Iberian Peninsula, so Valencia, Seville, Bilbao and Porto are all within 4.2 ms of floor, against 11.7 to 18.3 ms from Frankfurt. Here is what a Madrid server covers, why Latin America belongs in Ashburn instead, and what it costs.
HTTP floods arrive as real TCP and TLS sessions, often light on bandwidth, so network-layer scrubbing lets them through. Cloudflare's 2025 figures, HTTP/2 Rapid Reset, a working nginx limit_req and limit_conn config, timeouts, private origins, and where the 10 Tbps + Layer 7 tier fits.
Paris anchors France's largest online market and reaches London, Brussels and Amsterdam in a few milliseconds. Latency floors from Paris, the workloads that suit it, when Marseille is the better French seat, and what a server costs.