Custom guide
How an assessment runs
A practical walkthrough of the Latency & Uptime Assessment—from preparation through measurement windows to the closing readout—so you know what to expect before you request a brief.
Typical sequence
- Brief and scoping call. You list applications, journeys, and constraints. We confirm whether a full assessment or a Path Mapping Workshop is the better first step.
- Access and inventory. Read-only telemetry, approved synthetic endpoints, and a path inventory for in-scope journeys.
- Measurement windows. At least one busy-hour and one quieter window in Korea Standard Time, sampled on an agreed cadence.
- Analysis. Latency percentiles paired with path samples; uptime notes for gaps during the engagement.
- Readout and handoff. Ranked contributors, written findings, and a measurement plan your team can continue.
Prepare before kickoff
- Name a technical contact who can approve synthetic traffic windows.
- List production-like endpoints you are willing to sample.
- Share recent incident notes or synthetic check history, even if incomplete.
- Flag change freezes and known maintenance that overlap candidate windows.
- Decide whether kickoff or readout should be on-site in Daegu or at your office.
What you receive
A findings document, ranked delay contributors, uptime observation notes for the review period, and a recommended ongoing measurement cadence. You do not receive a hosted dashboard licence or ongoing staffing.
When a lighter start fits better
If journeys are still disputed inside your organisation, begin with a Path Mapping Workshop. If you are closing a single event, an Incident Latency Review may be enough. Cadence advisory suits teams who already measure but struggle to review consistently.