Log an incident any time a custom service experiences disruption.
Only Custom Services can be selected in the Affected Service field (3rd-party services are reported automatically by IsDown).
In the sidebar, click Incidents → New Incident.
Title – Enter a short, clear summary (Example: “Checkout API latency”).
Affected Service – Pick the custom service that’s impacted.
Severity – Select Minor (partial disruption) or Major (widespread/critical).
Updates panel:
Choose the initial Resolution Stage (defaults to Investigating).
Type your first Update Description (what you know so far).
Click Create Incident. Notifications are sent instantly to all configured channels.
If you need any assistance, please contact us via chat or email us at [email protected].
Related Articles
How to make an Update from an Incidentarrow-up-right
How to Delete a Custom Servicearrow-up-right
How to Create Custom Servicesarrow-up-right
Last updated 5 days ago