---
name: uptimerobot-monthly-uptime-report
description: "On the 1st of each month: last month's uptime across your UptimeRobot monitors, the incidents and their length, and the monitors below target. Use when the user asks for this, or when it runs on a schedule."
---

# UptimeRobot monthly uptime report

On the 1st of each month: last month's uptime across your UptimeRobot monitors, the incidents and their length, and the monitors below target.

Agencies send clients an uptime figure every month, and small SaaS teams quote one in their status update. UptimeRobot has the numbers, but its dashboard shows rolling windows per monitor, so a calendar-month figure for 18 monitors means a CSV and some arithmetic.

The agent asks the API for each monitor's uptime over exactly last month, lists the outages with their durations, and averages across monitors. Monitors under your target, 99.9% by default, are named with the incidents behind them, which is the part a client will ask about.

## Two ways to get the data

Use the API or MCP route when you have an MCP server, a CLI or an API token for the app. Otherwise, if you can drive a browser the user is signed in to (Claude in Chrome, a Playwright or Chrome DevTools MCP server), use the browser route. Say which one you used.

## Route A: API or MCP server

### What you need

- A read-only UptimeRobot API key (Integrations > API) in `UPTIMEROBOT_API_KEY`. The API is on every plan, Free included; the Free plan allows 10 requests a minute.
- Your uptime target if it is not 99.9%, and a client prefix convention if one report should cover several clients.

If something is missing, say what and stop; do not invent numbers.

### Steps

1. **Fetch monitors with last month's uptime** (UptimeRobot): `POST https://api.uptimerobot.com/v2/getMonitors` with a read-only `api_key`, `custom_uptime_ranges=<start>_<end>` (Unix timestamps for the first and last second of last month), `logs=1`, `log_types=1-2`, `logs_start_date` and `logs_end_date` for the same month. Page with `offset` and `limit=50`.
2. **Collect the outages**: From each monitor's `logs`, keep the down events (`type` 1) with their `datetime` and `duration` in seconds. Leave out paused monitors (`status` 0) and say how many were skipped.
3. **Compute the month**: Overall uptime is the average of the monitors' `custom_uptime_ranges` values. List monitors below the target, count incidents and find the longest outage. Group by a client prefix in the monitor name if you report per client.
4. **Report**: The month's uptime and the change from the month before, monitors below target with their incidents, and a short sentence per long outage that a client can read.

## Route B: the browser

### What you need

- Signed in to UptimeRobot on the account or team that owns the monitors; a Read-only team member role is enough.

If something is missing, say what and stop; do not invent numbers.

### Steps

Start at https://dashboard.uptimerobot.com/monitors. The user is signed in already; never type passwords or codes, and ask if a sign-in page appears.

1. **List the monitors**: The **Monitors** page lists every monitor with its current status and short-window uptime. Note which ones are paused (grey, "Paused") so you can leave them out and say how many you skipped. If you have more than one team, pick the right one from the account switcher first.
2. **Read last month's incidents**: Open **Incidents** in the left menu, set the date filter to last calendar month, and read each incident's monitor, start time and duration. Where the list is long, use **Export** if your plan shows it, otherwise scroll until the first day of the month.
3. **Read uptime per monitor**: For each monitor below target, open it and set the time range on the detail page to a custom range covering last month (the preset tabs are rolling 24 hours, 7 days, 30 days and 365 days, so a calendar month needs the custom picker). Read the uptime percentage and the response-time chart.
4. **Compute the month**: Overall uptime is the average of the monitors' monthly uptime. Where a monitor had no incident, count it as 100%. For monitors under 99.9%, list the incidents and total downtime; name the longest outage with its date.
5. **Report**: Last month's uptime against the month before, the monitors below target with their incidents, skipped paused monitors, and a two-sentence summary a client can read.

Note: The dashboard's default uptime figures are rolling windows, so September read on October 1 is not quite the calendar month; the custom range on the monitor page or the arithmetic from incidents fixes that. With more than about 30 monitors this route is a stopgap; the API gives the whole month in one call.

## The report

- **Uptime last month** across all monitors, with the month before.
- **Below target**: each monitor, its uptime, incidents and total downtime.
- **Incidents**: count and the longest outage with its date.
- **Skipped**: paused monitors.
- A client-ready paragraph if you report to clients.

## Post it to Briefkin

When `BRIEFKIN_TOKEN` is set, or `~/.config/briefkin/env` exists (the installer from https://briefkin.dev/docs writes it), also send the result to the user's Briefkin board as one card. Keep the `item_key` the same on every run so the card updates in place, use a new `event_id` per run, and put today's real numbers in place of the example ones. If the request fails, say so once and carry on.

```bash
[ -n "${BRIEFKIN_TOKEN:-}" ] || . ~/.config/briefkin/env
curl -sS -X POST "${BRIEFKIN_URL:-https://briefkin.dev}/v1/events" \
  -H "authorization: Bearer $BRIEFKIN_TOKEN" \
  -H "content-type: application/json" \
  -d @- <<'JSON'
{
  "v": 1,
  "event_id": "uptimerobot-monthly-uptime-report/<date of this run, e.g. 2026-10-16>",
  "item_key": "uptimerobot-monthly-uptime-report",
  "project": "Acme",
  "source": "UptimeRobot monthly uptime report skill",
  "kind": "metric",
  "title": "99.94% uptime in September across 18 monitors",
  "metric": {
    "label": "Uptime last month, all monitors",
    "value": 99.94,
    "unit": "%",
    "better": "higher",
    "period_start": "<start of the period, ISO 8601>",
    "period_end": "<end of the period, ISO 8601>"
  },
  "glance": [
    {
      "type": "Grid",
      "props": {
        "columns": 3
      },
      "children": [
        {
          "type": "Stat",
          "props": {
            "label": "Monitors",
            "value": 18
          }
        },
        {
          "type": "Stat",
          "props": {
            "label": "Incidents",
            "value": 7
          }
        },
        {
          "type": "Stat",
          "props": {
            "label": "Longest outage",
            "value": "1h 30m"
          }
        }
      ]
    }
  ],
  "widget": [
    {
      "type": "Table",
      "props": {
        "columns": [
          "Monitor",
          "Uptime",
          "Incidents",
          "Downtime"
        ],
        "align": [
          "left",
          "right",
          "right",
          "right"
        ],
        "rows": [
          [
            "api.example.com",
            "99.52%",
            3,
            "3h 27m"
          ],
          [
            "shop.example.com",
            "99.71%",
            2,
            "2h 05m"
          ],
          [
            "docs.example.com",
            "99.81%",
            1,
            "1h 22m"
          ],
          [
            "Nightly backup heartbeat",
            "99.88%",
            1,
            "52m"
          ]
        ]
      }
    },
    {
      "type": "Callout",
      "props": {
        "text": "Four monitors missed 99.9%. The longest outage was api.example.com on Sep 18, 90 minutes during a database failover. The other 14 monitors had no downtime.",
        "tone": "info"
      }
    }
  ],
  "size": "md"
}
JSON
```

Widgets come from the Briefkin catalog (https://briefkin.dev/v1/catalog). Without a token, just give the user the report.

Set `period_start` and `period_end` to the window the number covers: the tile names it from them ("Last 7 days", "Today", "This month"). For a count right now (open items, a balance), send `"period_label": ""` so no period shows; for another name, send it as `period_label` (at most 24 characters).

## Run it on a schedule

Suggested: 1st of the month at 9:00 (`0 9 1 * *`). From cron, with the agent signed in on that machine:

```bash
0 9 1 * * claude -p "Run the uptimerobot-monthly-uptime-report skill"
# Codex: codex exec, Gemini CLI: gemini -p, Copilot CLI: copilot -p, OpenCode: opencode run
```

Or use the agent's own scheduler (Claude Code routines, Codex automations, Claude or ChatGPT scheduled tasks): https://briefkin.dev/skills/uptimerobot-monthly-uptime-report#schedule

Source: https://briefkin.dev/skills/uptimerobot-monthly-uptime-report
