Home

Website incidents: triage by business impact

A homepage outage is visible, but a silent failure in an enquiry or registration flow can be just as urgent. Prioritise by affected users, lost transactions and whether a safe workaround exists.

First alert

Record the last verified success separately from the first report. Give one coordinator the incident timeline and a contact for each dependency. Share the affected route, time and observed behaviour without copying customer records into group messages.

Last success → First alert → Reconciliation
Last success → First alert → Reconciliation

Which requests fall inside the incident window?

If visitors can browse but cannot enquire, publish an already approved alternative contact route where appropriate. Remove the temporary notice only after the normal destination confirms a test enquiry.

Illustrative record: Last confirmed receipt (08:45 · REF-17) / First verified recovery (09:30 · REF-24)
Use the last confirmed receipt as the starting boundary for reconciliation, not the first complaint. Ask the business owner to close the gap against its own intake records.

Acceptance evidence · First verified recovery

Recover the journey, verify it at its destination and assign someone to reconcile requests from the affected window. Close the incident after documenting the recovery evidence and the follow-up owner.

Send DigiWeb the affected URL, observed time and first failing step

Let’s start with
what you need.

Tell us about your project or the website issue you need to resolve. DigiWeb will work through the next steps with you.

info@digiweb.com.vn0902 604 802Nguyễn Đức Thái · Founder DigiWeb