# UptimeScout: How to Check Whether a Service Had an Outage in a User’s Region

https://jsonscraper.com/blog/uptimescout-check-service-outage-user-region

Author: Michael Johnson

Published: 2026-11-20T11:33:44+00:00

Updated: 2026-11-20T11:33:44+00:00

A practical walkthrough: collect regional observation history and distinguish a fresh signal from an unknown interval

When users in one country report problems but the team sees the service operating normally, it is most useful to check observations for their region specifically. The UptimeScout API lets you request the history of a selected service by regional code and returns intervals along with the number of measurements. The result is a verifiable table for investigating a report: interval time, resolution, signal distribution, and sample count.



![Article: UptimeScout: How to Check Whether a Service Had an Outage in a User’s Region
Summary: Regional availability checks can help determine whether a user-reported incident coincided with UptimeScout observations. Follow a reproducible process: select a service and region, request its history, check data freshness and resolution, then save the result alongside the original response.
Image role: cover — the central idea
Section: 
Visual subject: Editorial photograph of a folded regional outage ](https://jsonscraper.com/assets/uploads/journal/2026/11/1cd4023e50fafa3c2411a7c5fc1a0f4b.png.hero.webp)

The region and time window define the scope of an availability check.© jsonscraper · AI-generated

 

The practical scenario here is diagnosing a suspected regional outage. Inputs include a service ID from the UptimeScout catalog, a region code such as US or GB, and a history window. The result helps compare the time of a user report with the service’s observations. The API describes the data as signals of observed availability; checking the service is useful for narrowing down the question, not as a replacement for your own application checks.

 

## Confirm the service and region first

 

Start with the catalog: find the required service by name or search query, then record its exact ID. The [UptimeScout OpenAPI specification](https://uptimescout.com/openapi.json) describes search through GET /v1/services and the q, service, region, limit, and offset parameters. For a diagnostic report, it is better to store the ID rather than just the display name, so a repeated request addresses the same catalog entry.

 

The region is specified separately using a two-letter code. Be sure to save it with the result: a response for US and one without a regional filter answer different questions. If the description needs to be shown in Russian, the lang=ru parameter controls description localization, while region selects the observations. The documentation explicitly distinguishes these two purposes.

 

## Request history instead of a single status

 

To investigate an incident, use /v1/history with the required service parameter and the selected region. The hours parameter sets the history window; the specification allows values from 1 to 2160 hours. The request also supports lang. According to the OpenAPI specification, authorization uses a license with the Bearer scheme. In a practical implementation, keep the key in an environment variable and do not write it to request logs.

 

```
import os
import requests

response = requests.get(
    "https://api.uptimescout.com/v1/history",
    headers={"Authorization": f"Bearer {os.environ['UPTIMESCOUT_LICENSE_KEY']}"},
    params={"service": "github", "region": "GB", "hours": 24, "lang": "ru"},
    timeout=30,
)
response.raise_for_status()
data = response.json()
print(data)
```

 

This is a minimal request example, not a published result from a real investigation. The github ID and GB region are example parameters: choose the service and region relevant to your task before using it. It is useful to save the entire response as JSON, adding the retrieval time and request description in separate fields in your audit system. This makes it possible to repeat the investigation and see exactly which data snapshot was used.

 

## Resolution and gaps are part of the result

 

In the history array, the important fields are observed_at, resolution_seconds, aggregated, samples, and counts. Resolution gives the duration of the time interval; samples shows how many observations went into the aggregate, and counts contains the signal distribution. Consider them together: a row with a small number of samples carries different weight in an analysis than an aggregate with many observations.



![Article: UptimeScout: How to Check Whether a Service Had an Outage in a User’s Region
Summary: Regional availability checks can help determine whether a user-reported incident coincided with UptimeScout observations. Follow a reproducible process: select a service and region, request its history, check data freshness and resolution, then save the result alongside the original response.
Image role: supporting illustration 2 — a different specific aspect
Section: Resolution and gaps are part of the result](https://jsonscraper.com/assets/uploads/journal/2026/11/a171063a93107bb525c54a0ee477e61a.png.hero.webp)

How to read history: region, time slots, resolution, and gaps.© jsonscraper · AI-generated illustration

 

UptimeScout describes history as time slots with different intervals depending on the selected window: one- and five-minute intervals for short periods, hourly intervals for a day, and daily intervals for longer periods. Older saved aggregates may have coarser resolution. Therefore, do not conclude that “the outage began at exactly this minute” if a row represents an hourly or daily aggregate. Use the actual resolution_seconds value and the effective_start and history_resolution fields in the response to define the limits of what can be concluded.

 

Treat a missing interval as unknown. The specification explicitly says to check for gaps as unknown intervals: an empty space in the history does not, by itself, indicate either normal operation or an outage. This simple reporting rule prevents gaps from being incorrectly filled with a “green” status or zeros.

 

## Compare the history with the current signal

 

If you need to check the state at the time of a report, request /v1/status for the same service and region. In the service object, consider status, observed_at, and stale together; the documentation presents these fields as a way to understand the signal’s state and freshness. The top-level status describes the API request result, while service.status describes the availability signal for a specific service. This distinction is particularly useful in automated reports: a successful HTTP response and the state of an external service are different things.

 

For multiple dependencies, you can use /v1/statuses, then request history only for the services and regions where an anomaly occurred. The specification also provides /v1/summary and /v1/incidents. For diagnosing the latter endpoint, keep its precise role in mind: it returns recent elevated disruption signals, not incidents confirmed by the provider itself. Treat the result as a reason to investigate, not as a definitive conclusion about the cause.

 

## How to report findings without speculation

 

In each report row, save the service ID, region, requested period, observed_at, resolution_seconds, samples, counts, and a note about gaps. Add a link to the user report or internal incident separately from the API fields. Then compare the time range with application logs, regional traces, and the user’s report. If the aggregate’s time boundaries are wider than the incident, phrase the finding accordingly: observations for the selected region and requested window contain the following signals, at the stated resolution and sample count.

 

This analysis gives the on-call engineer a useful choice: investigate the external service’s regional side, or continue diagnosing the user’s own application and network. Reproducibility depends on saving the request parameters and original JSON, while the quality of conclusions about timing depends on explicitly accounting for resolution, samples, and unknown intervals. That is the practical outcome for an availability case: not just a current status label, but a record bounded by region and time that a colleague can verify.
