Status pages
Learn the current status page availability and how to prepare incident updates.
Status pages are not available yet. The Status pages navigation item currently opens a page marked Coming soon.
Prepare for status pages
Plan components around recognisable services such as Dashboard, Public API, or Webhooks. Do not expose internal deployment names that do not help customers understand impact.
Keep the list short enough to scan. Several monitors can support one customer-facing component when they represent the same experience.
Prepare incident updates
A useful update answers three questions:
- What customer-facing behaviour is affected?
- What is the team doing now?
- When should readers expect the next update?
State what is known. Do not guess at a cause. Use the same service names in planned status pages, the incident record, and support communication.
Current checkpoint behaviour
Incident checkpoints are available now. The incident page calls them Public updates. Status page delivery and integration delivery are not available yet.
Use checkpoints to keep responders aligned. Use your approved customer channel for public updates until status pages are available.
Public means durable
Treat every planned status update as customer communication. Keep internal investigation notes in the incident record.
See feature availability for the current product state.
Last updated on