Status and incidents

Transparency during incidents builds trust. Subscribe before you need it—during an outage you will not want to hunt for the status page URL.

​

Status page

Bookmark the status page for component health and historical incidents.

​

Components

Understand which component maps to your integration path (API vs auth vs attachments) so partial outages make sense.

​

Subscriptions

Subscribe to email or RSS updates for maintenance windows.

​

On-call

Mirror status subscriptions into your incident channel so whoever is on-call sees updates without checking email.

​

Postmortems

Major incidents include summaries with remediation steps for transparency.

​

Your runbooks

After a vendor incident, update your internal runbook with workarounds you discovered—future you will thank past you.