Traffic, queue & uptime calculator
Calculate traffic capacity, queue wait times, server sizing, and allowed downtime for any service or venue.
The same sums answer "how many tills, agents or servers do we need so nobody waits long?" for a shop, a support line or a website. For a web server it goes on to work out sustained bandwidth, monthly transfer, concurrent workers, vCPUs and RAM from your own traffic, the downtime each uptime promise (SLA) allows, and a hardened NGINX or Caddy config with TLS 1.3, security headers and a rate limit. Everything is worked out on this device.
Queue and wait time
How: on average arrivals × time each are being served at once (Little's law); the chance of waiting and the average wait come from the Erlang C formula, which call centres use for the same sum. Arrivals are taken as random, as they are in a shop or on a phone line.
Domain search & packages
Type a name and Verse asks the registry of every ending (.no, .com, .net, .org, .info, .biz) at once whether it is registered, through RDAP (rdap.org), and shows who holds each taken one and when it expires. Verse does not register domains or sell hosting: a free name is registered at any registrar, which also confirms the price and whether the name is reserved.
Type a name, like example, and search: each ending's registry answers whether it is registered.
| Domain | Status | What the registry says | Name Unit asks |
|---|
| Plan | Storage | Price | Server |
|---|---|---|---|
| Small | 20 GB | Kr. 9 / mnd | Servere i Norge |
| Medium | 40 GB | Kr. 19 / mnd | Servere i Norge |
| Large | 80 GB | Kr. 29 / mnd | Servere i Norge |
Name Unit's own pages disagree on these plans (read 2026-10-29): its front page lists 9, 19 and 29 kr a month for 20, 40 and 80 GB, its web hosting page 15, 30 and 60 kr for 30, 60 and 120 GB, and its comparison page 10, 20 and 40 kr for 20, 40 and 80 GB. Ask them which price holds before you buy. The yearly domain prices in the search above are from its web hosting page.
Capacity
Shared vs exclusive
A crowded shared host splits its cores between tenants; an exclusive server keeps all of them. The same traffic, in numbers:
| Setup | Capacity | Your load | Readout |
|---|---|---|---|
| Shared host, 4 busy tenants | |||
| Exclusive server |
Uptime and SLA
Allowed downtime per period, for a 365-day year. Your SLA row is the one in bold:
| SLA | Year | Month | Week | Day |
|---|---|---|---|---|
| 99% | 3d 15h 36m | 7h 18m | 1h 40m 48s | 14m 24s |
| 99.9% | 8h 45m 36s | 43m 48s | 10m 5s | 1m 26s |
| 99.95% | 4h 22m 48s | 21m 54s | 5m 2s | 43s |
| 99.99% | 52m 34s | 4m 23s | 1m | 9s |
Server config
A hardened starting point sized to the numbers above: TLS 1.3, HSTS, a content security policy, nosniff, referrer and permissions policies, and a rate limit. Read it, then copy or download it.
This is a worked example: 50 requests/s, 200 KB replies, 40 ms of worker time, 128 MB per worker and a 99.9% SLA. Change a number and it becomes yours, and it stays on this device.