---
title: Deliverability | SendHQ Docs
description: Understand provider events, sender-identity reputation, daily ramping, and automatic recovery.
canonical: https://sendhq.cc/docs/deliverability
last-updated: 2026-09-07
---
# Deliverability

Understand provider events, sender-identity reputation, daily ramping, and automatic recovery.

## Events

SES notifications produce delivery, bounce, complaint, reject, open, and click events. Provider message IDs connect notifications to the original SendHQ email without crossing workspace boundaries.

## Reputation isolation

SendHQ calculates its circuit breaker for each normalized From email address inside a workspace. A failing bulk identity therefore does not locally pause a clean transactional identity. Suppressions remain workspace-local. The underlying SES tenant is still shared by identities in that workspace, so an AWS account or tenant enforcement action can affect more than one identity.

## Thresholds

In a rolling seven-day window, at least two bounces among five sends at a 10% or higher bounce rate throttle an identity; at least three among ten sends pause it. One complaint at 0.05% or higher throttles; two at 0.1% or higher pause.

## Paused sending and recovery

A paused From identity receives `423` before provider submission. Stop the triggering stream, inspect events and recipients, and correct its source. There is no manual unpause switch: the identity returns to active automatically on its next send attempt after the rolling metrics fall below every threshold.

## Inspect state

`GET /deliverability/reputation` lists the last evaluated state for each exact sender identity. An identity appears after its first send attempt, and its row updates when a later attempt evaluates the rolling window.

## Metrics

`GET /deliverability/stats` aggregates delivery events across the workspace for 30 days; it is not the seven-day per-identity circuit-breaker calculation. Provider acceptance, recipient-server delivery, opens, and clicks represent different outcomes.