External Status Page monitor
What it checks
An External Status Page monitor reads an upstream service's public status page or supported feed. It reports Down when the page cannot be read, an active incident affects the selected scope, or a component in scope reports degraded performance or an outage. Planned maintenance is allowed.
This monitors what the provider reports. It complements direct website/API checks; an operational status page alone does not prove every request to that provider succeeds. To publish your own page, use Status pages.
Plans
External Status Page monitoring is included in Pro and Business. It is unavailable on Free. The restriction applies to creation, cloning and resuming after a downgrade, through the dashboard, API and MCP.
Create it
- Open New monitor and choose External Status Page.
- Enter a friendly name and the public Status page URL, such as
https://www.githubstatus.com. - Leave Status page provider on Auto, or choose the provider you know the page uses.
- Optionally enter Components to watch, one name per line, and a Component group.
- Choose the interval, available probe regions and alert channels, then click Create monitor.
The default and built-in minimum interval are 5 minutes, subject to your plan's limits. Advanced settings offer timeout and retries.
Providers
| Provider | Input |
|---|---|
| Auto | Detect the supported page/feed format automatically. |
| Atlassian Statuspage | A public page using Statuspage's JSON data. |
| incident.io | A public incident.io status page. |
| OneUptime Status Page | A public status page made with OneUptime. |
| RSS / Atom | The public feed URL. |
For an unsupported format, Auto may only establish that the page is reachable. Check the reported provider, components and incidents in Details before relying on the monitor for provider-health detection.
Choose the scope
Leave components and group empty to watch the whole page. To watch specific services, use their displayed component names. * matches part of a name, for example API*. A group limits the components considered; component names are then matched inside that group.
You can specify up to 30 component names, each up to 120 characters, and a group up to 120 characters. The Details card reports unmatched names so you can correct a typo or a provider rename. A component with no match is not evidence that the intended service is healthy.
Read the result
Details show the provider, overall status for the selected scope, component statuses, active incidents and unmatched components. The normal alert settings apply. Incidents outside a selected component/group do not count as incidents in that monitor's scope.
API and MCP
Use type: "external_status_page", the page/feed URL in target and an external_status_page settings object containing provider, component_names and component_group. See the API example and MCP examples.