Troubleshoot a network connectivity or performance problem
A structured, layer-by-layer diagnosis plan with the commands to run, what each result means, and the likely fix.
The prompt
Help me troubleshoot a network problem.
Symptom: [what is failing - e.g. "users in one VLAN can't reach the file server", "VPN drops every 20 minutes", "slow access to a cloud app"]
Who and what is affected: [one user / one site / everyone; specific apps or services]
When it started and what changed: [recent changes, updates, new devices, config pushes]
Environment: [on-prem, AWS, Azure, hybrid; key devices and vendors - firewalls, switches, SD-WAN, VPN, ZTNA/SASE]
What I've already checked: [results so far]
Output I can share: [PASTE ping, traceroute, logs, or config snippets with IPs, hostnames, and secrets masked]
Work through it like this:
1. Restate the problem and the scope, and list the most likely causes ranked by probability given my evidence.
2. A step-by-step diagnosis from the bottom up (physical/link, IP and routing, DNS, firewall and security policy, application), with the exact commands or console checks for my platform and what a good vs. bad result looks like.
3. For each likely cause, the fix and how to confirm it worked.
4. Security checks: whether a policy, certificate, or access rule change could explain it, and fixes that do not weaken security (no "allow any" rules as a permanent fix).
5. Rollback steps for any change, and what to monitor afterward.
Only reason from the evidence I give. Mark assumptions clearly and tell me what extra output would narrow it down. Remind me to follow my change-control process before touching production.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Software Development prompts
What to fill in
- one user / one site / everyone; specific apps or services
- recent changes, updates, new devices, config pushes
- results so far
How this prompt is built
This prompt follows the Chain-of-Thought structure (Chain-of-thought prompting). A chain-of-thought prompt asks the model to work through a problem step by step before giving its answer, which tends to help on reasoning, planning and multi-part questions.
Related prompts
- Build a working app, tool, or game from a descriptionTurns a plain-English idea into a complete, runnable app — web tool, dashboard, or browser game.
- Fix a Git problemStep-by-step help for merge conflicts, undoing mistakes, branching, and recovering lost work.
- Write a script to automate a repetitive taskBash, Python, or PowerShell scripts that automate a task safely, with instructions to run them.
- Find which change caused a regressionCreates a systematic plan to pinpoint the commit, deploy, or config change that broke something that used to work.