The Deliverability tab on the [Reports](/reports/messages-dashboard) page helps you understand whether your email is reaching inboxes. SendOps tracks every bounce and complaint event from AWS SES and surfaces key metrics, per-provider deliverability with trend deltas, latency data, and suppression information. ## Headline metrics The top of the Deliverability tab displays the following metrics for the selected date range: | Metric | Description | |--------|-------------| | **Hard Bounce %** | The percentage of sent messages that resulted in a hard bounce (permanent delivery failure). | | **Soft Bounce %** | The percentage of sent messages that resulted in a soft bounce (temporary delivery failure). | | **Total Bounce %** | The combined bounce rate (hard + soft bounces). | | **Complaint Rate** | The percentage of sent messages that generated a spam complaint. | AWS monitors your sending reputation continuously. If your bounce rate exceeds **5%** or your complaint rate exceeds **0.1%**, SES may place your account under review, limit your sending, or suspend it entirely. SendOps displays these thresholds as reference lines so you can see how close you are at a glance. ## SES Account Status Alongside the headline rates, the Deliverability tab surfaces the current status of your AWS SES account, read live from SES. This tells you at a glance whether AWS itself will let your mail go out: | Indicator | What it tells you | |-----------|-------------------| | **Sending enabled** | Whether SES is currently allowing your account to send at all. If sending is disabled, no mail will leave regardless of your reputation. | | **Sandbox vs. production** | Whether your account is still in the SES sandbox (can only send to verified addresses) or has been granted production access. See [SES Sandbox & Production Access](/sending-email/ses-sandbox). | | **Enforcement status** | AWS's current enforcement state for the account — `HEALTHY` when there are no issues, or a warning/review state when AWS has flagged your sending. | | **VDM (Virtual Deliverability Manager)** | Whether AWS's Virtual Deliverability Manager is enabled on the account, which unlocks additional SES deliverability insights. | ## Bounce Reasons A bar chart shows categorized bounce reasons, breaking down why messages bounced. This helps you distinguish between list quality issues (invalid addresses), mailbox-full conditions, policy rejections, and other bounce categories so you can take targeted corrective action. ## Complaint Reasons A breakdown of complaint reasons with percentages, showing why recipients reported your messages as spam. Use this to identify patterns — for example, a high percentage of "moved to junk" complaints may indicate content or frequency issues. ## Deliverability by Provider The Deliverability by Provider table shows per-provider sending volume, deliverability rates, and how those rates have shifted versus the equal-length period immediately before the one you're viewing. The top eight providers by current-period sends are listed individually, with the long tail aggregated under **Other**. The provider list is derived from your actual sending data — your top destinations show up automatically, whether they're US providers (Gmail, Microsoft, Yahoo, Apple), European providers (Free.fr, Orange, GMX, Web.de, Yandex, Mail.ru, Libero, Seznam, etc.), or APAC providers (Naver, QQ, NetEase, Sina, Daum, Rediff, etc.). SendOps recognises common alias domains (gmail.com + googlemail.com → Gmail; outlook.com + hotmail.com + live.com + msn.com + regional TLDs → Microsoft; Yahoo regional TLDs → Yahoo; etc.) so they collapse under one canonical name. Domains SendOps doesn't recognise appear under the raw recipient domain, so nothing is hidden from view. | Column | Description | |--------|-------------| | **Provider** | The receiving provider, derived from the recipient email domain. | | **Sends** | Total messages sent to recipients at this provider. | | **Deliveries** | Messages confirmed delivered. | | **Bounces** | Messages that bounced. | | **Bounce %** | Bounces as a percentage of Sends. The annotation underneath shows the change in percentage points versus the prior period. | | **Complaints** | Messages that generated spam complaints. | | **Complaint %** | Complaints as a percentage of Sends, with the prior-period delta underneath. | | **Rejects** | Messages that AWS SES refused to send (typically due to content rejection or recipient suppression). | | **Reject %** | Rejects as a percentage of attempted messages (Sends + Rejects, since rejected messages are not counted in Sends), with the prior-period delta underneath. | Click any column header to sort by that column. **Other** always appears at the bottom regardless of sort, since it is a residual rather than a ranked provider. The trend deltas (the small `+0.40pp` / `-0.05pp` annotations under each rate) are the primary signal for spotting deliverability issues: a provider whose bounce or complaint rate has crept up versus the prior period is the one to investigate, even if the absolute rate is still under the SES thresholds. Positive deltas (rates getting worse) appear in red; negative deltas (rates improving) appear in green. Brand-new providers with no prior-period activity show no delta, since there's nothing to compare against. ## Delivery Latency The Delivery Latency section shows how long it takes for messages to be accepted by recipient mail servers. Three percentile metrics are displayed: | Metric | Description | |--------|-------------| | **P50** | The median delivery latency — half of messages are delivered faster than this. | | **P95** | 95% of messages are delivered within this time. | | **P99** | 99% of messages are delivered within this time. Only the slowest 1% take longer. | A chart visualizes latency trends over the selected date range, making it easy to spot degradation or improvement over time. ## Suppression List The Suppression List viewer shows email addresses that have been suppressed. Suppressed addresses are those that SES will not attempt to deliver to, typically due to previous hard bounces or complaints. Use this section to review which addresses are suppressed and understand the reasons. If you've confirmed an address is safe to mail again — for example, a recipient has fixed their mailbox — you can **remove it from the suppression list** directly from this viewer. SES will then attempt delivery to that address on future sends. Removing an address requires the `suppression.manage` permission; by default this is granted to **Owner** and **Org Admin** roles. This SES suppression list is distinct from SendOps's own [Undeliverable List](/reports/undeliverable-list), which layers additional configurable rules on top of the raw AWS signals. ## Improving deliverability If your rates are trending in the wrong direction, here are the most effective steps: 1. **Clean your recipient list.** Remove addresses that have hard-bounced. Implement double opt-in for new subscribers to ensure valid addresses. 2. **Monitor complaint sources.** Check which campaigns or message types are generating complaints. A high complaint rate on a specific channel or template is a signal to revisit the content or frequency. 3. **Use a dedicated domain for transactional email.** Separate transactional email (order confirmations, password resets) from marketing email by using different domains or subdomains. This isolates reputation issues. 4. **Authenticate your email properly.** Ensure SPF, DKIM, and DMARC are correctly configured. See [DNS Configuration](/domains/dns-configuration) for setup details. 5. **Warm up new domains gradually.** If you add a new sending domain, start with low volume and increase over days or weeks. Sudden high-volume sending from an unknown domain triggers ISP suspicion. For a deeper walkthrough of common deliverability issues and how to resolve them, see [Deliverability Problems](/troubleshooting/deliverability-problems). ## What's next? - Review the [Reports Overview](/reports/messages-dashboard) to investigate individual bounced or complained messages. - Check [Engagement Metrics](/reports/engagement-metrics) to see how recipients interact with your delivered email. - Set up [Notifications](/notifications/configuring-notifications) to get alerted when bounce or complaint rates cross a threshold.