comparing monitoring as code
Which uptime monitors have a Terraform provider?
Plenty of monitoring vendors will tell you they support Terraform. Fewer will tell you the provider is a community fork that was archived in 2023, or that it manages checks but cannot touch the status page you are paying them for. Here is the state of it, checked against the Terraform Registry rather than against marketing pages.
the registry, not the marketing page
| Uptimepage | Pingdom | StatusCake | Statuspage | UptimeRobot | OneUptime | |
|---|---|---|---|---|---|---|
| provider from the vendor | yes | none | yes | none | yes | yes |
| who maintains it | Uptimepage | community forks | StatusCake | individuals | UptimeRobot | OneUptime |
| registry tier | community | community | partner | community | community | community |
| newest release | Jul 2026 | 2020, archived | Oct 2023 | 2022 · 2024 | Jul 2026 | Jul 2026 |
| manages monitors | yes | yes | yes | no product | yes | yes |
| manages status pages | yes | no | no | objects only | yes | yes |
| manages alert channels | yes | yes | yes | no | yes | yes |
Registry tiers are official (HashiCorp-built), partner (vendor-verified) and community (everything else). Community does not mean third-party: UptimeRobot and OneUptime both publish from their own verified GitHub organizations under a community badge, and so does Uptimepage. Ours carries the same community badge as theirs, which is exactly why we are telling you to read the repository rather than the badge.
No provider exists in a SolarWinds- or Pingdom-owned namespace on the Terraform Registry. The most-downloaded community provider, russellcardullo/pingdom, is archived and self-describes as no longer maintained; last release 2020, last commit 2023. Living forks are maintained by an unrelated media company and by individuals, and none manages status pages.
StatusCake's provider is partner tier and its repository is active, but it has shipped no new release since v2.2.2 in October 2023 and it carries no status-page resource, though StatusCake sells status pages.
Atlassian publishes no Statuspage provider. The two community options manage components and incidents on a page you created by hand; neither creates the page itself.
Better Stack, Checkly, Uptime.com, UptimeRobot and OneUptime all manage monitors and status pages in Terraform, as Uptimepage does. Grafana and Datadog manage synthetic checks and no status page, because neither sells one.
Verified against the Terraform Registry and each provider's repository on 14 July 2026. Providers ship often, so check the registry before you decide.
Read the registry tier carefully
The Terraform Registry has three tiers: official means HashiCorp built it, partner means the vendor is verified, and community means everything else. Community does not mean third-party. UptimeRobot and OneUptime both publish providers from their own verified GitHub organizations that still carry a community badge, and UptimeRobot's README calls its provider official. So the badge alone will not tell you whether a vendor stands behind the thing. Who owns the repository, and when it last shipped, will.
The gap nobody advertises: status pages
This is the one that catches teams out. A provider that manages checks is common. A provider that also manages the status page, its components and its incidents is not. Pingdom sells status pages, and not one of its community providers can manage them. StatusCake sells status pages, and its own partner-tier provider has no status-page resource at all. Grafana and Datadog manage synthetic checks and nothing resembling a status page, though in fairness neither sells one. If your goal is the whole thing in code, checks and the public page together, that shortlist collapses fast.
Where the incumbents actually stand
Pingdom has no provider in any SolarWinds- or Pingdom-owned namespace. What exists is thirty-odd community forks, and the most-downloaded of them, russellcardullo/pingdom, is archived: its own description reads no longer maintained, its last release was in 2020 and its last commit in 2023. Living forks are kept by an unrelated media company and by individuals. Atlassian publishes nothing for Statuspage either; the two community providers manage components and incidents on a page you created by hand, and cannot create the page itself. StatusCake is the honest middle: a real partner-tier provider from the verified StatusCake organization, repository still active, but no new release since v2.2.2 in October 2023.
Who does this well, including our rivals
Credit where it is due, because a comparison page that only flatters its author is worthless. Better Stack, Checkly, Uptime.com, UptimeRobot and OneUptime all ship vendor-maintained providers that manage monitors and status pages, and most of them shipped a release this month. Better Stack's covers on-call policies too. Uptimepage is not alone here and does not claim to be. The gap is specific and it is with the incumbents above, the ones most teams are actually migrating away from.
Where Uptimepage fits
The Uptimepage provider covers the three things together: monitors, status pages and alert channels, against the same REST API the dashboard uses, with scoped tokens so a Terraform run gets a write-scoped credential rather than an all-or-nothing key. Declare a check, the page it appears on and the channel that gets paged, review it in a pull request, and apply. There is an MCP server on the same API if you would rather ask an assistant what is broken. Hosted free with no card, or self-host the whole thing under AGPL.
the monitor, the page, and the component that links them
resource "uptimepage_target" "api" {
name = "api"
interval = 60
check = {
type = "http"
http = {
url = "https://example.com/healthz"
expected_status = { kind = "exact", exact = 200 }
}
}
}
resource "uptimepage_status_page" "public" {
slug = "acme"
name = "Acme Status"
}
resource "uptimepage_status_page_component" "api" {
status_page_id = uptimepage_status_page.public.id
target_id = uptimepage_target.api.id
}