Monitoring · Available on All tiers

"How long were we down?" should have a real answer.

Every incident gets a timeline — first failed check, which regions failed, and when it recovered — so the postmortem is a fact, not a guess.

Start Free → See pricing

Free forever plan, no card required.

Why it matters

Incident history

Without a real incident record, "how long was checkout broken?" turns into an argument between Slack timestamps and someone's memory. Customers ask the same question, and "we're not totally sure" is not an answer that builds trust. It shows up worst in the postmortem: one person swears the outage started at 2:14 because that's when their phone buzzed, another points to a Slack message timestamped 2:31, and neither of those is necessarily when the first check actually failed. Multiply that uncertainty across every incident your team has ever had, and you end up with a reliability story built on vibes instead of data — which falls apart the moment a customer or a stakeholder asks for specifics. A real, automatically captured timeline turns that argument into a fact everyone can just look up. It's the difference between a reliability story you can actually stand behind and one that's mostly reconstructed after the fact. It also means the next postmortem starts from agreed-upon facts instead of a debate about whose recollection is more accurate.

Automatic timelines

No manual logging — every state change is captured the moment it happens, with no one having to remember to write it down. That matters most in the middle of an actual incident, when whoever's responding is focused on fixing the problem, not pausing to jot down a timestamp nobody has time to format correctly under pressure. It's one less thing to worry about getting right while everything else is already going wrong. The record exists whether or not anyone remembers to create it, which is exactly when it matters most.

Region-level detail

See exactly which region(s) reported the failure, not just a single up/down flag with no context. That detail is often the fastest clue to what actually went wrong — a failure isolated to one region points at a routing or regional infrastructure issue, while a failure across every region points squarely at your own server or application. That's often the fastest way to tell a real outage apart from a routing hiccup local to one part of the world. It turns a vague sense that "something regional happened" into an actual, specific diagnosis.

Feeds your reports

Automations' incident summary report rolls this straight into a scheduled email — no copy-pasting required. Whoever needs a weekly or monthly reliability summary — a manager, a client, your own records — gets it delivered automatically, instead of someone spending an afternoon assembling a report by hand from a dashboard. It's the kind of automation that turns a recurring chore into something nobody has to think about again. It's one fewer manual step standing between an incident happening and someone actually being informed about it.

FAQ

Incident history, answered.

Do I have to log incidents myself?

No — every state change is captured automatically the moment it happens. There's no manual logging step and nothing to remember to write down, even in the middle of actively responding to the incident when logging it yourself would be the last thing on your mind. The timeline is simply there, waiting, whenever you go looking for it. It's simply there, automatically, the way a car's odometer just keeps counting without anyone resetting it.

How much incident history do I get?

15 days on Free, 90 days on Starter, and 365 days on Team — with region-level detail on every incident, not just a single up/down flag. That's enough runway to spot a recurring pattern, like an endpoint that flakes every few weeks, well before it would otherwise register as anything more than a one-off annoyance. Longer retention on the paid tiers reflects how much more useful a pattern becomes the further back you can see it. Even the shorter retention on Free is enough to look back at your most recent incidents in full detail.

Can I get incident history out of the dashboard?

Yes — Automations' incident summary report rolls your incident history into a scheduled email, so nobody has to copy-paste a timeline into a report by hand. Set it once and it keeps landing in the right inbox on schedule — weekly, monthly, whatever cadence fits — pulling from the same automatically captured timeline as the dashboard, so the report and what you'd see if you logged in always agree. It's one less recurring task on someone's calendar every month. It arrives whether or not anyone remembers to go looking for it that week.

Get Started

Incident history. Free, starting now.

Start Free →