Override Incident Dates and Times
Set custom start and end times for incidents on status pages so stakeholders see the real customer-impact window. All Quiet keeps your internal audit timestamps unchanged.
Published: Thursday, 27 August 2026
You can now set custom start and end times for incidents on status pages so stakeholders see the real customer-impact window. All Quiet keeps your internal audit timestamps unchanged.
How It Works
| Feature | Description |
|---|---|
| Setup | Turn on Override Dates & Times when you Create Incident, Declare Incident, or Affect Services. |
| Status pages | Custom times drive the service uptime graphs, duration calculations, and the public timeline. |
| Internal history | All Quiet retains actual system timestamps and labels your custom inputs as Actual affecting start or Actual affecting end. |
| Public API | Set statusPageStartOverride and statusPageEndOverride. |
Limitations
- Each override needs both a date and a time. Values cannot be in the future or more than 30 days in the past. When you set both, the end time must follow the start time.
- While an incident remains open, status pages show Ongoing. The custom end time applies after you resolve the incident.
- You cannot set date overrides from Slack, Microsoft Teams, or Mattermost. Status page subscriber emails also ignore custom times.
More updates
-
New
Publish and Unpublish Comments
Retroactively publish internal comments to status pages or hide public comments. Control stakeholder communication during and after an incident.
-
New
Give Every Agent Least-Privilege API Access
Scoped organization API keys for pipelines and Terraform, plus personal access tokens that never exceed the linked user's live roles — so agents can triage, check on-call, and configure integrations under least privilege.
Updated August 27, 2026