“My internet is slow” is not a ticket an ISP can act on. They need when it happened, whether the router was reachable, and whether the loss was to their network or just one website. A screenshot of a speed test taken after the outage ended does not help.
A menu bar monitor that is already running can capture the window you will otherwise forget. The useful artifacts are a timestamped history graph, packet loss, and a CSV you can attach to the ticket.
What evidence actually moves a ticket
- Start and end times in your local timezone, not “last night.”
- Latency and packet loss to a stable public host (for example 1.1.1.1 or 8.8.8.8), not only to the site that felt broken.
- Gateway health for the same window. If the router stayed green, you can say the LAN was up.
- A CSV or log you did not type by hand after the fact.
How to capture it with PingStatus
Leave PingStatus running. When the line degrades, the history graph already has the dip, the loss spikes, and the state-change markers. Export that range to CSV and attach it. Mention that gateway monitoring stayed healthy (or did not). That single sentence tells the agent whether to send you through Wi-Fi troubleshooting or to look at the last mile.
If you need a longer window, use a 24-hour view or keep the Mac from sleeping while you collect. A one-hour graph that missed the dropout will not persuade anyone.
What to write in the ticket
Keep it short: the interval, the target you pinged, packet loss percent, whether the gateway stayed reachable, and that a CSV is attached. You are not arguing. You are handing them a timeline they can match to their own counters.
PingStatus keeps a history graph and can export CSV, so the next outage is a file — not a memory.
Get PingStatus on the Mac App Store