Network diagnostics intake

Your name *

Email *

Organization

Leave blank if this is personal rather than for a business.

Phone

What kind of environment? *

What kind of problem? *

What is happening? *

The symptom as you observe it, not what you think is causing it. Both are useful, but keep them separate.

When did it start? *

A date if you have one. Say if it has always been this way.

What changed around then?

Weather event, provider work, new hardware, firmware or software update, config change, a move, a new tenant on the network.

What is affected? *

Which devices, users, sites, services, or applications. Be specific.

What still works normally? *

Just as useful as what is broken. It is what narrows the cause.

Is there a pattern to it?

Time of day, load, particular users or devices, only after a reboot, only on one link.

What have you already ruled out?

What is in the path? *

Everything between the affected device and where the traffic is going. Modem, router, firewall, switches, access points, provider and circuit type. Makes, models, and firmware versions where you have them.

Can you reproduce it on demand? *

Diagnostic output

Paste anything you have. Ping, traceroute, mtr, pathping, MTU probes, throughput tests, DNS lookups, interface counters, switch logs. Raw output beats a summary every time.

What has already been tried?

Including anything a provider, vendor, or previous engineer did, and what they concluded.

What is this costing you?

Time, money, downtime, or work that cannot happen. It sets how deep the investigation should go.

Captures, logs, screenshots, diagrams

Packet captures, device logs, screenshots, topology diagrams. Up to 10 MB total here.

Link to larger captures

Anything over 10 MB: share a link instead. Any service is fine.