All systems operational
Redirects run at the edge, apart from the console and the API, so a problem in one rarely reaches the others. A delay in click recording shows up as late numbers, never as a slower redirect.
A day the console holds no record of is drawn as no data, never as working. Days are UTC.
Incidents
Posted by a person while one is happening, updated as it moves, and listed for 90 days after.
No incidents recorded in the last 90 days.
What each part covers
So a red row tells you what it means for your links.
Redirects
Answered by Cloudflare’s network, nearest the visitor. A link used recently is answered from cache, so it keeps redirecting even while the database is unreachable.
Click recording
Clicks go through a queue into the database. A delay here shows as late numbers in analytics, reports and webhooks; a redirect never waits for it.
Console and API
Signing in, and creating, editing and reporting on links. The API is the console’s own routes under /api, so the two usually move together.
Email delivery
Sent in the background. A send that fails is retried for about five hours before it is given up, so a slow email is usually a late one, not a lost one.
Something wrong that is not shown here?
Tell a person, with the short link and the time you saw it.