Your dependencies publish incidents on status pages nobody watches at 3am. This integration crawls them for you and turns each newly published incident into a Clarion issue — so a vendor outage reaches your queue as fast as one of your own alerts.
Estimated time: 2 minutes per page. You need only the status page URL.
Prerequisites
- The public URL of a status page you want watched
- The page must be an Atlassian Statuspage or an Instatus page
Connect
- In Clarion, open Integrations and find Status Page.
- Click Connect — the integration activates immediately; there is no credential.
- Add a monitor per page, pasting its URL.
Clarion detects the provider and resolves the machine-readable source automatically: the incidents.json v2 API for Atlassian Statuspage, or the validated RSS/Atom feed for Instatus (which often lives on a different host).
Set a default severity per monitor so a page whose incidents always matter to you can be escalated harder than one that rarely does.
How the crawl works
Each page is polled every two minutes. Clarion tracks the newest incident it has seen plus a set of recent incident ids, which is what makes new-incident detection reliable across both providers.
The first poll seeds the page rather than importing its entire history — you get the next incident, not a backlog. A page that is quiet on its first poll is still marked as seeded, so the first real incident afterwards is queued rather than being mistaken for backlog.
Per-monitor sync health is tracked like every other poller, so a page that moves or breaks surfaces as an integration health issue rather than going quietly silent.
Where it helps
Status-page incidents give an agent the cheapest possible answer to “is this us?”. A spike in errors that coincides with your CDN publishing a degradation is a very different investigation from the same spike with every vendor green.
Disconnect
Click Disconnect on the integration page, or disable an individual monitor to stop watching one page. 
