# Connector: Statuspage (statuspage)

Purpose: incidents, scheduled maintenances and component degradations on Atlassian Statuspage instances (/api/v2/summary.json). Sensor type: STATUSPAGE, tier S by default. Normalization: keyed list — incident:<id>, maintenance:<id> (title = name — status, latest update body, impact, created/updated), component:<id> for non-operational components, plus an overall indicator item. compareFields: status, title, updatedAt → incident created / updated / resolved, maintenance scheduled, component degraded/restored. Sensor extra keeps the indicator and counts. Non-Atlassian pages: Google-style JSON (incidents.json: Google Cloud, Firebase, Workspace) and Salesforce Trust are handled by the jsonlist connector; Heroku's own API by http (JSON mode); status.io/instatus pages are not supported (they return HTML) — use their RSS/history feed when available. Verified: 2026-09-08 on 23 status pages (OpenAI, Anthropic, Cloudflare, GitHub, Vercel, Netlify, Coinbase, Kraken, Reddit, MongoDB, Elastic, HashiCorp, Groq…). Tests: tests/fixtures/statuspage.json.