Speed & reliability
Redirects answered at the edge, in under 50 ms.
A Kilo link resolves on Cloudflare’s edge network - close to the person who clicked - by reading a single pre-compiled value. It never waits on a database, so the redirect is just as fast everywhere, not just near one server.
< 50 ms
Typical edge redirect, worldwide
1
KV read per redirect - no database on the hot path
0
Raw IP addresses stored, on any product
How it stays fast - and honest about it
- 01
One read on the hot path, never a database
When a link is clicked, the redirect reads one compiled value from Cloudflare KV at the edge and answers. The database that holds your links, rules, and analytics is never touched on that path - so a slow query or a busy region can’t slow a redirect down.
- 02
Analytics never block the click
The quality verdict, geo, device, and referrer for a click are written after the visitor has already been sent on their way, independently of the redirect. Measurement runs behind the response, never in front of it.
- 03
Links don’t 404
A link that’s paused, archived, or past its campaign window doesn’t break - it resolves to a branded page that explains what happened, carried in the same compiled value the redirect already reads. No dead end, and no database lookup to decide it.
Live status, in the open
Current component states, a timeline of any incident, and 90 days of history live on the status page. We publish what broke and when - component by component - rather than a single green light, and you can subscribe there to be told when something changes.
Open the status page→Fast answers
- How fast is a Kilo redirect?
- A Kilo link is answered at Cloudflare’s edge, typically in under 50 milliseconds, because the redirect reads one pre-compiled value from KV and never queries a database. It’s served close to the person clicking, so the speed holds up worldwide rather than only near one datacenter.
- What happens if the database is down?
- The redirect path doesn’t use the database, so a click still resolves. The database backs the dashboard, analytics writes, and billing - all off the hot path - so an issue there can delay a report or a settings change, but not the redirect itself.
- Where can I see if Kilo is up?
- The status page shows the live state of each component, any open incident, and 90 days of history. It’s the single place we report degradations, and you can subscribe there to be notified when something changes.
Put a link through it.
Open the dashboard