Start with the exact service and symptom
Record the service name and the action that fails: opening the website, signing in, sending a message or calling an API. Different features can fail independently. Search the UptimeScout directory and open the individual service page instead of assuming that every similarly named service is the same product.
Keep the time of your failed attempt. A screenshot without a timestamp is difficult to compare with a changing signal. If the problem concerns one account, avoid posting personal information in a public discussion.
Read region and time before the status
A status is meaningful within its observation context. Choose the country relevant to your users and read its timestamp and freshness. A result from another region can help with comparison, but it does not replace the local observation.
Read the last observation time and the freshness indicator. An old operational result should not override a fresh local failure. Likewise, a disruption signal does not prove that every user or feature is affected.
Compare the current result with history
Choose the three-hour view to understand the immediate period, then twelve hours or a day for context. Each column groups saved observations. Select a column to see the time window and the mix of states inside it.
An isolated elevated observation and a repeated disruption signal deserve different follow-up. Empty intervals mean there were no usable observations in that interval. Do not fill those intervals mentally with either an outage or successful operation.
Check what remains uncertain
Compare another device or connection if it is available and consult the service’s official help or status information. If other sites work but a single feature fails, gather the exact error rather than repeatedly refreshing the whole service.
For a support report, include the service page link, selected region, observation time and your own symptom. These details let the recipient distinguish a regional signal from a device-specific issue. UptimeScout is evidence for investigation, not a replacement for the service operator’s diagnosis.
Make the same workflow repeatable
An application can retrieve the current signal through GET /v1/status and save the region and observed_at with its own incident notes. Teams investigating several dependencies can use batch status. The integration guide explains authentication, error handling and why unknown must remain a distinct state.
Content reviewed on 18 November 2026.
Markdown


