How fast is redirhub.com?
Measured from Washington, D.C., Frankfurt and Tokyo (average) on October 22, 2026. Test it again, or try your own URL.
Result · Overall (average of 3 locations) · median of 5 runs
Faster than 79% of redirects tested in the last 7 days.
redirhub.com answered in 15 ms. The 7-day average is 131 ms across 78 tested URLs.
- 1https://redirhub.com/301
- 2https://www.redirhub.com/200
Nothing: no extra hops, no plain HTTP, and the chain ends on a working page.
Reproduce it
Run the same test yourself
Copy this into a terminal on macOS or Linux. It already holds your URL, so paste it and press Enter. Only curl is needed.
Your numbers will differ from ours: they depend on where you run it and your network.
for u in 'https://redirhub.com/'; do
for i in $(seq 5); do
curl -s -o /dev/null --max-redirs 0 --max-time 10 \
-w '%{time_namelookup} %{time_connect} %{time_appconnect} %{time_starttransfer} %{http_code}\n' "$u"
done | sort -n -k4 | awk -v u="$u" '{r[NR]=$0} END{split(r[int((NR+1)/2)],m," ");
printf "%-28s %s DNS %4.0f connect %4.0f TLS %4.0f first byte %4.0f ms\n", u, m[5], m[1]*1000, (m[2]-m[1])*1000, (m[3]>0?m[3]-m[2]:0)*1000, m[4]*1000}'
doneThe benchmark
How “faster than X%” is worked out
The number comes from the redirects people test on this page, plus a fixed list of well-known redirects measured every day, so each location always has a baseline.
Every test is kept for 7 days
Each URL tested here stores its median first-byte time and test location. One entry per URL, so testing the same link ten times doesn't tilt the result.
Compared like for like
By default your result is the average of all three locations, ranked against every URL measured from all three. Test from one location and it is ranked only against URLs tested from there, so Tokyo is never compared with Washington, D.C.
Your rank is a percentile
“Faster than 82%” means 82% of the URLs tested in the last 7 days took longer than yours.
By provider
How fast is each redirect provider?
As of 2026-10-23, 25 providers were measured from Washington, D.C., Frankfurt and Tokyo (average) over the last 7 days. Fastly was the fastest, at a median 12 ms. Every provider with at least one tested URL is listed with its median first byte. Open one for its locations, rank and where its time goes.
- Fastly redirect speed6 URLs12 ms
- Microsoft Azure redirect speed1 URL15 ms
- RedirHub redirect speed11 URLs16 ms
- Akamai redirect speed3 URLs24 ms
- Google redirect speed1 URL38 ms
- redirect.pizza redirect speed3 URLs49 ms
- Vercel redirect speed1 URL53 ms
- Short.io redirect speed2 URLs55 ms
- Amazon CloudFront redirect speed2 URLs55 ms
- Meta redirect speed1 URL59 ms
- Dub redirect speed1 URL64 ms
- Cloudflare redirect speed7 URLs92 ms
- YouTube redirect speed1 URL93 ms
- TinyURL redirect speed2 URLs99 ms
- Envoy redirect speed4 URLs101 ms
- Bitly redirect speed3 URLs123 ms
- LinkedIn redirect speed1 URL139 ms
- Amazon redirect speed1 URL140 ms
- Buffer redirect speed1 URL154 ms
- Cuttly redirect speed1 URL250 ms
- Rebrandly redirect speed1 URL266 ms
- nginx redirect speed3 URLs300 ms
- urllo redirect speed5 URLs313 ms
- Spotify redirect speed1 URL317 ms
- BL.INK redirect speed2 URLs390 ms
Method
What the test measures
DNS
Looking up the redirect's domain.
Connect
Opening a TCP connection to the closest server.
TLS
The HTTPS handshake and certificate check.
Server wait
Until the 301 and its Location header arrive.
Only the redirect response is timed, not the destination page, so a slow destination does not count against the redirect. Hops are counted separately. The tool runs on Vercel Functions in Washington, D.C., Frankfurt and Tokyo, not on our redirect network, and alternates A and B on every run.
The benchmark figures are free to reuse: credit RedirHub and link to this page. CC BY 4.0
FAQ