Connect status pages
Know when a service you depend on is down before your users tell you.
- You need
- No token Status pages are public
- The form asks
-
- Connector name
- You can watch
-
- Incidents
- Component status
- Overall status
- Access
- GET of the page's public summary only
The Status pages connector reads the public Statuspage JSON API (/api/v2/summary.json) of a status page: its open incidents, its components and its overall indicator, in one request per check. It needs no account and no key.
Add the connector
Open Settings › Connectors, click +, choose Status pages, give it a name (status is suggested) and click Add Connector. There is nothing to sign in to.
Pick a page
Every monitor names its page: one of the listed services, or any status page’s address (status.example.com) that serves the Statuspage JSON API, including pages hosted by incident.io.
Listed, each checked to serve it: 1Password, Airtable, Akamai, Anthropic (Claude), Asana, Bitbucket, Box, CircleCI, Clerk, Cloudflare, Confluence, Cursor, Datadog (US1), DigitalOcean, Discord, Dropbox, Elastic Cloud, Expo, Figma, Fly.io, GitHub, Grafana Cloud, HashiCorp, HubSpot, Jira, LaunchDarkly, Linear, Mailgun, MongoDB Cloud, Netlify, New Relic, Notion, npm, OpenAI, PlanetScale, Postman, Reddit, Render, Resend, Segment, Sentry, Shopify, Snowflake, Supabase, Twilio, Twitch, Vercel, Zapier and Zoom.
Not listed because their pages do not serve that API: Slack, Stripe, Heroku, GitLab, PagerDuty, Docker, Fastly, Okta and Auth0.
The three monitor kinds
| Kind | Query | What alerts |
|---|---|---|
| Incidents | page:github |
Each open incident, and each update posted to it |
page:openai impact:major -updates |
New incidents of major or critical impact only | |
| Component status | page:cloudflare component:ID -maintenance |
A component (every one unless picked) going degraded or into an outage; back to operational clears, and a new outage alerts again |
| Overall status | page:github level:major |
The indicator reaching the level (minor unless given); maintenance never alerts |
The editor lists the page’s components by name; the query keeps their ids.
Clicking a row opens the alert in CoIsland. An incident shows its status, impact, components and its whole timeline of updates, “Resolved” once it is. A component shows its status now and the open incidents naming it.
Troubleshooting
- “status.example.com: this is not a Statuspage status page (its summary.json is not Statuspage JSON).” The page uses another service. Its RSS or Atom history feed, if it has one, works with the RSS / Atom connector.
- “Nothing at status.example.com/api/v2/summary.json (HTTP 404).” Same cause.
Stuck? Open an issue on GitHub, or write to hello@coisland.app.