SysOps Incident Recovery

Recovery

Operations view focused on mean time to resolution, delay drivers, and where the team can reduce recovery time.

Session requiredAuthenticated routes expect a real session token or cookie.API base: https://dev.sysopsai.net/apiSign in
What MTTR Means

Track how long it takes to restore service, not just how many tickets close.

The MTTR analysis page is now route-native in `apps/web`, making recovery-time analysis part of the core shell instead of a side demo artifact.

Audience: IT manager, operations lead, incident ownerBest use: weekly ops review and monthly service improvementRelated question: what is slowing us down?
down 42 min
4.6 hrs

Overall MTTR, priority incidents

steady
7.2 hrs

MTTR, Sev-2 incidents

27% of total
27%

Blocked time share

better by 38 min
1.4 hrs

Median triage to ownership

Resolution Time By Incident Category

Use this to spot where the team is structurally slower, not just where the ticket count is high.

Network and vendor-linked work are slowest
Remote access / network6.8 hrs average
Public data / reporting pipeline5.7 hrs average
Identity / access3.3 hrs average
Collaboration tools2.4 hrs average