---
title: "Public status page (issue"
method: GET
path: "/{token}"
tags: ["Public"]
---

# Public status page (issue

`GET /{token}`

## Request

- Base URL: `https://status.uptimemonitoring.com`
- URL: `https://status.uptimemonitoring.com/{token}`
- Auth: none required

Unauthenticated — the token is the only credential, same shape as
`/feed/{token}`. Served on its own host (`STATUS_PAGE_URL`), not
under `/api/v1`; a request to this path on the API host 404s. Any
method other than `GET` on this path (`HEAD`/`POST`/`PUT`/`DELETE`)
also 404s, never 405. A token that doesn't match the pattern below
gets the same 404 without a database lookup. Carries `Age` (seconds
the served copy has aged at the origin) and `Cache-Control: public,
max-age=<N>`, where `N` is the full freshness lifetime the view was
cached under — 60 for a settled view, 5 for one where the live
status currently disagrees with the open incident rows — never
reduced by `Age`, since a cache already subtracts `Age` from
`max-age` itself; both headers are computed the same way on the
RSS/Atom/JSON/badge siblings below.

## Path parameters

- `token` string, required

## Response `200`

HTML status page.

## Other responses

- `404`: Unknown or malformed token, a page that is off, a deleted monitor, or a suspended account — all indistinguishable, and all five status-host formats (`/{token}`, `/{token}/feed.rss`, `/{token}/feed.atom`, `/{token}/status.json`, `/{token}/badge.svg`) return this identical shape. A malformed token (wrong length, prefix, or a non-hex/uppercase character) never reaches the database lookup the other cases do.
- `500`: The token lookup, the view build, or the format's own render step failed for a reason other than the deliberately indistinguishable 404 cases above — a connection failure, query timeout, or scan error. Distinct from `503` below, which is specifically the shared view-build deadline expiring.
- `503`: The shared view-build deadline (`StatusPageBuildTimeout`, 10s) was exceeded while this request was still live — e.g. database slowness. Distinct from a client disconnecting mid-build, which writes no response at all. Every one of the five status-host formats returns this identical shape, including the `Retry-After` header.

---

[API](https://skmtc.dev/uptimemonitoring/apis/uptimemonitoring-com-api.md) · [All operations](https://skmtc.dev/uptimemonitoring/apis/uptimemonitoring-com-api/llms.txt) · [OpenAPI document](https://skmtc.dev/uptimemonitoring/apis/uptimemonitoring-com-api/revisions/ddcb2a8bc70f?raw)