Advanced Incident Routing History

Advanced Routings now include a History tab. This feature provides a complete history trail of every routing decision.

• Execution Visibility: View exactly which rule was triggered and the changes applied.

• 30-Day Retention: All Quiet stores routing history for 30 days. This history is available starting 12 May 2026.

• Expanded Data: Click any row to see the specific conditions, actions, and channels involved in a routing event.

• Access Control: Team members with read-only permissions can still view the History tab to assist with troubleshooting.

Per-Incident Routing Details

Additionally, you can now view Routing rule executions directly within the Properties sidebar of any incident.

It includes outcome badges and deep links to help support teams jump directly to the relevant routing rule.

All Quiet now provides a detailed history of all notifications. Users and admins can track delivery results for every alert to ensure critical information reaches the right person.

Feature Overview

The Notification History tool tracks all outbound communication methods:

• Email

• SMS

• Voice Calls

• Push Notifications

Key Capabilities

• Delivery Outcomes: View the real-time status of every notification.

• Error Reporting: Access specific error details when a delivery fails.

• Contextual Links: Navigate directly to the related incidents from the log.

• Admin Support: Team admins can open an overlay within Incident Details to audit delivery per user and event.

Data Retention and Availability

• Release Date: May 11, 2026

• Retention Period: All Quiet stores notification logs for 30 days.

Navigation Paths

All Quiet Terraform Provider v3.0.0 is now available. This update introduces a breaking change to provide greater flexibility in how you manage users and their incident notification settings.

Key Benefits

• Decoupled Management: Separate user identity from notification preferences.

• Choice in Provisioning: Choose between fully managed setups or lightweight user creation where members configure their own settings.

• Granular Control: Manage notification rules as independent resources.

Breaking Change Overview

In version 3.0.0, we moved incident notification settings out of the allquiet_user resource. You must now use the new allquiet_user_incident_notification_settings resource to define how users receive alerts.

Required Action

You must update your Terraform configuration before your next deployment. If you upgrade the provider without updating your code, Terraform will fail because the old schema no longer exists.

Impact on Existing Users

This change only affects how Terraform manages configurations. It does not modify the settings of users you already provisioned. Their current notification rules remain active in the All Quiet platform.

Why We Made This Change

Version 3.0.0 allows you to decide how much control Terraform exerts over a user's experience.

1. Fully Managed Provisioning: Use both allquiet_user and allquiet_user_incident_notification_settings if you want to enforce specific phone numbers and notification rules.

2. Lightweight Provisioning: Use only allquiet_user. This creates the account and lets the team member set their own notification preferences within the All Quiet app later.

This separation simplifies the management of organizations with diverse notification needs.

Migration Guide

Follow these steps to upgrade to version 3.0.0:

1. Upgrade the Provider: Update your Terraform required_providers block to version 3.0.0.

2. Update User Resources: Remove the incident_notification_settings block from all allquiet_user resources.

3. Add Notification Resources: For users who require Terraform-managed settings, create a new allquiet_user_incident_notification_settings block. Link it to the user via the user ID.

4. Optional Self-Service: If you prefer new users to manage their own settings, omit the new notification resource for those specific accounts. For old users, you can also later delete allquiet_user_incident_notification_settings to allow self-management.

Example Migration

Before (v2.x.x):

resource "allquiet_user" "admin" {
  email = "[email protected]"
  incident_notification_settings {
    # old configuration here
  }
}

After (v3.0.0):

resource "allquiet_user" "admin" {
  email = "[email protected]"
}

resource "allquiet_user_incident_notification_settings" "admin_settings" {
  user_id = allquiet_user.admin.id
  # define notification rules here
}

If you need help with your specific configuration, contact our support team or refer to the technical documentation for detailed resource attributes.

Copy full incident data and event timelines as Markdown from the All Quiet web app or Public API. This feature provides structured data for postmortems, internal tickets, and AI analysis.

Feature Overview

Practical Applications

• Incident Retrospectives: Generate factual timelines for postmortem reports instantly.

• Ticketing: Paste incident context into internal support tickets or runbooks for better visibility.

• LLM Context: Provide structured data to internal AI models for summaries and root cause analysis.

How to Access

• Web App: Navigate to incident details and select the Markdown export option.

• API: Use the Public API to retrieve incident data for specific teams or organizations.

Use these exports to improve communication and response speed across your entire engineering organization.

We created a GitHub integration to support flexible workflows between your code and your on-call alerts. You can now sync GitHub issues and All Quiet incidents in three ways.

Integration Options

How it Works

• Outbound (All Quiet to GitHub): All Quiet creates a GitHub issues when you forward an incident automatically, manually or via specific routing rules. The system updates the GitHub issues as the incident status changes.

• Inbound (GitHub to All Quiet): New GitHub issues trigger All Quiet incidents based on your criteria. You can also configure GitHub to resolve or reopen incidents.

• Two-Way Sync: This mode keeps both platforms identical. It ensures your team sees the same data whether they work in GitHub or the All Quiet app.

Why this matters

This update reduces manual work and prevents data silos. By linking GitHub issues directly to our incident management system, your workflows are automized and information is automatically handled in sync across both systems.

Here’s how to set it up: https://docs.allquiet.app/integrations/outbound/github

We updated our Public API to include audit logs for both EU and US regions. This update allows teams to automate security workflows and programmatically manage compliance data.

New API Endpoints

LLMs and automated scripts can now access audit events through these specific endpoints:

Regional API Documentation

Access the full Swagger documentation for your organization's region:

• US Region: https://allquiet.app/api/public/swagger-ui/index.html

• EU Region: https://allquiet.eu/api/public/swagger-ui/index.html

SIEM Integration and Export

This update enables automated data exports of All Quiet audit logs to Security Information and Event Management (SIEM) tools like:

• Splunk

• SentinelOne

• IBM QRadar

• Rapid7

• Wazuh

• New Relic

Technical Details

• Regions: Available in EU and US data residency zones.

• Plan: Requires the Enterprise add-on for Auditing.

• Benefit: Reduces manual compliance work and speeds up incident forensics.

• Security: To access your organization’s audit logs via the public API, a valid API key is mandatory.

—> Learn more about our audit logs: https://docs.allquiet.app/advanced/auditing

All Quiet now integrates with Observium. You can forward network alerts directly to your on-call teams using a lightweight alert transport script and inbound webhooks. This integration helps you centralize network monitoring and reduce MTTR through automated incident workflows.

How the Integration Works

All Quiet processes Observium alert statuses to manage the incident lifecycle automatically. This ensures your team only sees actionable alerts.

• Incident Creation: All Quiet opens or updates incidents when alert_status = 0.

• Auto-Resolution: All Quiet resolves incidents when alert_status = 1.

• Noise Reduction: The integration ignores delayed (2) and suppressed (3) alerts to prevent unnecessary on-call notifications.

Data Mapping and De-duplication

To maintain a clean incident feed, All Quiet uses specific logic to group related alerts and provide full context to responders.

Key Benefits for Incident Management

• Reliability: Automated syncing ensures your status pages reflect real-time network health.

• Efficiency: Responders receive all necessary metrics within the All Quiet app, reducing the need to context-switch.

• Focus: Advanced filtering stops suppressed alerts from waking up your teams.

Learn more: https://docs.allquiet.app/integrations/inbound/observium

Pro Tip: Use this integration to bridge the gap between your network operations and your developer teams for faster cross-functional incident response.

We updated All Quiet to give you precise control over your incident communication. You can now customize how much data your status pages reveal to the public or internal stakeholders.

Enhanced Privacy Settings

The new privacy controls allow you to balance transparency with security. You can adjust these settings directly in your organization's dashboard:

Secure Access Management

Reliability requires trust, and trust requires secure data handling. When you enable password protection, All Quiet ensures:

• Encryption: All passwords use industry-standard encryption.

• Complexity: Passwords must be at least 6 characters long.

• Full Coverage: Protection extends to the status page API and visual badges.

Why Use These Controls?

Many teams need to communicate incidents without exposing sensitive internal workflows. These updates help you maintain professional status pages while protecting your operational privacy. You decide exactly what your customers see during downtime.