Status

Status unavailable right now

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.

The console did not answer, so this page shows no state rather than a guess. Try again in a minute.
Redirects every short link, on every domainNot known right nowUnknown
Console console.brevily.comNot known right nowUnknown
API console.brevily.com/apiNot known right nowUnknown
Click recording clicks reaching analytics, reports and webhooksNot known right nowUnknown
Email delivery invitations, sign-in codes, receiptsNot known right nowUnknown
90 days agoOperationalDegradedDownNo dataToday

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.

The incidents cannot be shown while the status is unavailable.

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.