How fast is Cuttly?
Cuttly redirects answered in a median 333 ms from Washington, D.C. over the last 7 days. That is faster than 7% of all redirects tested here.
By location
Where Cuttly is fast, and where it isn't
Distribution
Cuttly among every redirect tested
Bars: median first-byte time of every URL tested from Washington, D.C. in the last 7 days. Lines: provider medians.
All providers
Redirect speed by provider, last 7 days
Median first byte from Washington, D.C. over the last 7 days. Every provider with at least one tested URL is listed, with how many URLs its figures come from.
| # | Provider | Median | p90 | URLs | |
|---|---|---|---|---|---|
| 1 | Fastly | 11 ms | 14 ms | 5 | |
| 2 | Amazon CloudFront | 11 ms | 13 ms | 1 | |
| 3 | RedirHubUs | 15 ms | 16 ms | 2 | |
| 4 | Short.io | 15 ms | 19 ms | 2 | |
| 5 | Microsoft Azure | 15 ms | 20 ms | 1 | |
| 6 | 17 ms | 18 ms | 1 | ||
| 7 | Meta | 19 ms | 38 ms | 1 | |
| 8 | Bitly | 21 ms | 22 ms | 2 | |
| 9 | Amazon | 25 ms | 37 ms | 1 | |
| 10 | Envoy | 29 ms | 33 ms | 3 | |
| 11 | Cloudflare | 31 ms | 39 ms | 3 | |
| 12 | Rebrandly | 32 ms | 38 ms | 1 | |
| 13 | Dub | 37 ms | 44 ms | 1 | |
| 14 | Buffer | 40 ms | 43 ms | 1 | |
| 15 | Akamai | 41 ms | 54 ms | 3 | |
| 16 | 62 ms | 112 ms | 1 | ||
| 17 | TinyURL | 68 ms | 97 ms | 2 | |
| 18 | Vercel | 75 ms | 86 ms | 1 | |
| 19 | YouTube | 79 ms | 84 ms | 1 | |
| 20 | redirect.pizza | 166 ms | 176 ms | 2 | |
| 21 | Spotify | 184 ms | 212 ms | 1 | |
| 22 | urllo | 196 ms | 210 ms | 2 | |
| 23 | BL.INK | 239 ms | 304 ms | 2 | |
| 24 | Cuttly | 333 ms | 1010 ms | 1 | |
| 25 | nginx | 341 ms | 88 ms | 4 |
Cuttly links we measure every day
Open one for its full report: every hop, its status code and the time of each phase, from all three locations.
Bring your links to your own domain. RedirHub serves redirects from 130 Global PoPs, with a ~90ms global average response time.
Method
How these numbers are measured
A fixed list, every day
Well-known redirects and short links are measured every day from Washington, D.C., Frankfurt and Tokyo, so every location always has a baseline.
Plus what people test
Every URL tested on the speed test counts once per location, grouped by the provider that answered it. Entries expire after 7 days, and refused answers (403, 429) are left out.
Same measurement for all
Fresh connection, no redirect following, median of every run. Run the same test with curl →