WIRELESS SERVICE INCIDENT RECORD
Companion guide: https://yenra.com/wireless-infrastructure/
Prepared September 8, 2026. Editable diagnostic worksheet.

Use authorized devices, documented diagnostics and designated test
endpoints with known behavior. Collect evidence before changing a system.
Keep credentials, private keys and unnecessary personal data out of this
record. Reference protected logs in the organization's approved system.

Incident ID / owner / start time / time zone:
Affected location, task and impact:
Client model, OS and authorized identifier:
SSID, AP, switch/port, network/VLAN, gateway as known:
Authentication / DHCP / DNS / upstream / application owners:
Last successful task and recent approved changes:

For each stage, record time, observation, expected behavior, evidence
location, working comparison and remaining hypothesis.
Power and uplink:
Association/authentication:
Address and gateway assignment:
Configured DNS resolver and approved test name:
Upstream connectivity:
Application authentication and completed task:

Compare where applicable:
- New joining client versus a client with an existing session/lease.
- Second authorized device in the same location.
- Same device on an approved working path.
- Wired/wireless paths with equivalent policies.
Failed ping alone is inconclusive if endpoint/filter behavior is unknown.

Earliest failed stage supported by evidence:
Cause hypothesis and next discriminating test:
Escalation owner and evidence summary:
Approved change / rollback procedure / maintenance window:
Post-change fresh join and original task result:
Observation duration and repeat tests:
Recovery evidence, unresolved items and closure owner:
Topology/monitoring/support record updates needed:

Fictional example in guide: new clients fail at 09:05 while established
clients work; addressing evidence at 09:10 points to DHCP. Use the method
of comparing stages; do not assume this is the cause of your incident.