What Changed This Summer on serverlist.dev

Three months, ten new hosting providers, and a stack of features that quietly changed what serverlist.dev is for. It started as a price table. It is turning into the place where you can actually finish a hosting decision, and then keep an eye on it afterwards.

Here is what shipped between June and August 2026, and, more usefully, what to do with it. Everything below is in the changelog with exact dates.

Ten new providers

The catalogue grew by ten providers this summer, and the mix says something about where the market is going: a Swiss IaaS provider, a French alternative to the hyperscalers, two bare metal specialists, and a handful of smaller European hosts that consistently undercut the big names.

• June 9: quicksrv (ClearStack B.V.)
• June 18: easyname
• July 18: Prepaid-Hoster.de
• July 19: UpCloud
• August 10: Cherry Servers
• August 15: Zenlayer
• August 15: Scaleway
• August 16: cloudscale
• August 18: Alwyzon
• August 19: Hexabyte

Every one of them is imported on the same schedule as everything else, with the same fields: price, specs, locations, traffic, hourly billing, and, new this summer, virtualization type.

Alongside that came r/BuyFromEU, a page that narrows the catalogue down to providers that are companies registered in the European Union, rather than US providers renting rack space in Frankfurt. Where the hardware physically stands stayed a separate filter, because the two questions are genuinely different.

Benchmarks stopped being a side page

The biggest shift of the summer is that real world performance data moved out of its own corner and into the main comparison. Geekbench 7 results are now parsed out of submitted YABS runs, and the average score shows up directly in the CPU column of the server table. Two new sidebar filters let you set a single core and multi core Geekbench floor, which is the most effective way to filter out cheap vCPU cores that benchmark like a potato.

The Has YABS Benchmark filter narrows the table to servers where somebody actually ran the script, so you are comparing measured numbers instead of datasheets. Columns that hold several values now also let you choose what to sort by: CPU by cores, frequency, architecture or Geekbench score, disk by size or type, and networking by bandwidth or traffic limit.

Add virtualization type, which tells you whether a plan is real KVM or container based, and admin notes, which put context on availability, quirks and offers behind the info icon in a row, and the table now carries most of what you would otherwise dig out of forum threads.

Your account grew up

Saved servers landed on August 1. You can bookmark up to 50 servers you are considering. Logged in, the list syncs to your account, logged out it stays in your browser. The sidebar has a saved servers only toggle, so your shortlist becomes a filtered view of the full table instead of a separate page that goes stale.

You can now also sign in with GitHub next to Discord, and link both to the same account, so either one takes you back to the same subscriptions. A Discord account is no longer needed to watch prices at all.

Price alerts are no longer Discord DM only either. Add up to five Discord webhooks in your workspace and price changes get posted straight into a channel your team reads. Each subscription picks its own destination, and you can change that afterwards. Every notification is additionally published as a personal RSS feed, so you can follow your alerts in the reader you already have open.

The newest feature: GPU filters

Shipped on August 21, the GPU comparison got the filter set it was missing: GPU model, VRAM, VRAM bandwidth, CUDA cores, FP32 TFLOPS and monthly price, plus no rising costs and hourly billing available. Locations can now be selected by region instead of one country at a time.

If you have been picking GPU instances by eyeballing model names, this is the update that makes the page usable. At least 24 GB of VRAM, hourly billing, in the EU, under a fixed monthly ceiling is now four clicks.

Smaller, but worth knowing: the changelog now shows when the data was last updated, separately from when the software last changed.

The fast path: a fitting server in about two minutes

The efficient order of operations is hard limits first, soft preferences last. Filtering is free, scrolling is not.

1. Set the price ceiling first, it removes more rows than anything else. Turn on no rising costs if you do not want a promotional price that jumps at renewal, and hourly billing available if the workload is short lived.
2. Set the two specs you cannot compromise on, usually RAM and disk, as floors rather than exact values.
3. Pick your region. The location filter has region quick select, so all of the EU is one click, not twelve.
4. Add a Geekbench floor if the workload is CPU bound, or tick has YABS benchmark if you simply refuse to buy unmeasured hardware.
5. Sort by price ascending or the property you care about most. The table is infinite scroll, so you can keep scrolling until you find a server that fits.
6. Select exactly one server. The table then highlights every other row against it in green and red. This is the fastest scan in the product and the most overlooked one.
7. Check the currency and VAT toggle in the header before you compare final numbers across countries.

Then save the two or three that survive and share the URL. Filters and columns all live in the query string, so the link reproduces exactly what you are looking at. Two minutes, and you have a shortlist you can defend.

The slow path: making the best decision, not the fastest one

The fast path finds a server that fits today. The rest of the platform exists for the decision you will still be paying for in eighteen months. Used together, the pieces compound.

Shortlist, do not decide

Save six to eight candidates instead of picking one. Saved servers cost nothing to hold, and the point of every step below is to let candidates disqualify themselves.

Check the price history before you trust the price

Every server has a price chart on its comparison page, and the pricing history section tracks the market by RAM tier, from 4 GB to 64 GB, plus CPU and memory price indices. That answers questions a snapshot cannot. Is this cheap price a launch promotion or a stable position? Does the provider raise prices quietly every spring? Is the whole 32 GB tier drifting down, so waiting a month is the better move? A provider that has held its price for two years is worth a small premium over one that has not.

Verify the hardware with benchmarks, not marketing

Open the YABS runs for your candidates and compare disk I/O and network throughput across runs on the same plan. The spread between runs tells you about noisy neighbours, which an average score hides. Prefer verified runs, submitted by users who linked the run to their account. If a candidate has no runs at all, that is information too, and if you already rent the machine, submitting your own run through the YABS API is a single command.

Subscribe to the servers you did not pick

This is the step almost everyone skips. Put a subscription on your top three, including the two you rejected. You are allowed 25 of them. You get notified when a price changes and when a server stops being available, which is the early warning that a plan is being retired. Route them to a Discord webhook in your infrastructure channel or to your RSS reader so they arrive where you already work.

Use the Discord bot for the follow up loop

The bot in our Discord community takes a maximum price when you watch a server, so the alert fires when it crosses your number rather than every time it moves. You can pull up a single server or a whole provider without leaving the channel where your team is arguing about it, list and cancel what you are watching, and pin your currency and VAT so quoted numbers match your invoices.

Let the account tie it together

Sign in with Discord or GitHub, link both, and either one lands in the same workspace. Saved servers, saved filters, subscriptions, notification targets, claimed benchmark runs and the full notification history live in one place, and every alert is written to your workspace even when a delivery channel fails.

The combined effect is that your shortlist stays alive instead of rotting in a browser tab. Three months from now, when a plan you rejected drops by thirty percent or the one you chose gets retired, you find out on the day it happens, with the benchmark data and the price curve already in front of you.

What is next

More providers, more notification channels beyond Discord, and more of the benchmark data pulled into the places where you are already looking. If a provider is missing, or a filter you need is not there, tell us on Discord. Most of this summer's list came from exactly that.