Uptimepage

Monitor history

get_monitor_history

Read-only

One monitor's history over a window (1h/24h/7d/30d): uptime, latency series, a per-region split of the same window, failures with error text, and incident windows. Pass region to narrow it to one probe region and tell a partial outage from a total one. Read-only.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	The monitor id (from `list_monitors`).
`region`	No	Narrow uptime, the latency series, and the region breakdown to one probe region (an id the monitor is assigned to, from `get_monitor.regions`). Omit for every region together.
`window`	Yes	Time window: `1h`, `24h`, `7d`, or `30d`.

Output Schema

TableJSON Schema

Name	Required	Description
`region`	No	The region this answer was narrowed to, or `null` for all of them.
`uptime`	No	Uptime percentage over the window. `null` when the window holds no checks — that is unknown, not zero. Unfiltered it counts confirmed incidents; under a `region` filter it is that region's raw check rate, so the two are not comparable.
`regions`	Yes	Per-region split of the same window, so a partial outage is visible. Always every region the monitor runs in, including under a `region` filter, and empty when it runs in only one. Regions that ran no checks in the window are omitted; this reads per-minute data, which is kept for 30 days, so at the far edge of a `30d` window a region can be short of samples or absent while the headline numbers still cover it.
`failures`	Yes	Confirmed failures on the monitor as a whole. A `region` filter does not narrow these: an incident is raised for the monitor, not per region.
`incidents`	Yes	Incident windows on the monitor as a whole, unnarrowed by `region` for the same reason as `failures`.
`latency_series`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 9, 2026

changedOutput schema / $defs / IncidentWindow / properties / counts_as_downtime / description

Previous value: -"`false` when this window is listed but explains none of the `uptime` gap."New value: +"`false` when this window is listed but kept out of `uptime`."

addedOutput schema / $defs / IncidentWindow / properties / impact

Added value: +{
+  "description": "`major_outage`, `partial_outage` or `degraded`. A counted window\nexplains the `uptime` gap by it: a major outage in full, a partial\noutage for 30% of its length, a degraded one not at all.",
+  "type": "string"
+}

addedOutput schema / $defs / IncidentWindow / properties / recovered

Added value: +{
+  "description": "Stretches inside the window the monitor was back up in before the\nfailure returned. `uptime` does not count them.",
+  "items": {
+    "$ref": "#/$defs/RecoveredStretch"
+  },
+  "type": "array"
+}

addedOutput schema / $defs / IncidentWindow / properties / recovering_since

Added value: +{
+  "description": "RFC 3339 moment the monitor came back up while the incident waits out\nits recovery period. `uptime` stops counting the window here.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

changedOutput schema / $defs / IncidentWindow / required

Previous value: -[
-  "opened_at",
-  "counts_as_downtime"
-]New value: +[
+  "opened_at",
+  "counts_as_downtime",
+  "impact",
+  "recovered"
+]

addedOutput schema / $defs / RecoveredStretch

Added value: +{
+  "description": "A stretch an incident was back up in.",
+  "properties": {
+    "from": {
+      "description": "RFC 3339 start.",
+      "type": "string"
+    },
+    "until": {
+      "description": "RFC 3339 end, when the failure came back.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "from",
+    "until"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedSep 2, 2026

addedOutput schema / $defs / IncidentWindow / properties / counts_as_downtime

Added value: +{
+  "description": "`false` when this window is listed but explains none of the `uptime` gap.",
+  "type": "boolean"
+}

changedOutput schema / $defs / IncidentWindow / required

Previous value: -[
-  "opened_at"
-]New value: +[
+  "opened_at",
+  "counts_as_downtime"
+]

First observedAug 11, 2026

TDQS

Score is being calculated.

All Uptimepage tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.