Report scope and timing
State whether the symptom affects one user device, one network, or all reported connections. Include when it began and any visible terminal alarm. Use operator-approved observations, not unsupervised network scanning.
Separate commercial and safety services
Describe the purpose of the affected service. Do not assume that crew internet can replace a required safety communications service. Where safety equipment is involved, follow the vessel’s escalation procedures and seek the appropriate technical route.
Keep credentials out of the inquiry
Do not include account passwords, public IP addresses, access tokens, firewall rules, or remote access codes. Identify the relevant provider and account reference only as needed through an approved channel. Ask which party owns the next diagnostic step.
Information to prepare
- Terminal make and model
- Affected users or services
- Visible alarms and start time
- Provider reference through a controlled channel
This page is a planning aid. It does not authorize equipment changes, replace manufacturer instructions, determine vessel readiness, or establish a company approval. Use the vessel’s procedures and an appropriately qualified and approved delivery route.