# Deliverability Provider Humanic uses Resend which is a modern email API designed for developers, focusing on simplicity, reliability, and strong deliverability for transactional and marketing emails. Resend, Amazon SES, and Mailgun all offer strong deliverability rates, but there are differences in performance and features: * **Resend** consistently reports near 100% uptime and high inbox placement rates due to its multi-region routing, built-in authentication (DKIM, SPF), and 24/7 monitoring. It is designed for developers and prioritizes transactional email reliability, with real-time insights and automated failover for maximum delivery consistency.​ * **Amazon SES** has a 2025 average inbox placement rate of about 85.66%, with roughly 11.31% of emails landing in spam and 2.89% not reaching recipients. SES benefits from Amazon's global infrastructure and is known for reliability, especially for bulk and transactional emails, but deliverability can vary by industry and sender reputation.​ * **Mailgun** has an average inbox placement rate of 81.81%, with about 14.28% of emails sent to spam and 3.30% lost. Mailgun’s deliverability is strong for most use cases, but performance can be lower for sensitive industries like finance or dating.​ In summary, Resend and Amazon SES tend to outperform Mailgun in deliverability, with Resend offering modern tools for monitoring and optimization, while Amazon SES leverages AWS’s robust infrastructure. Mailgun remains a solid choice but generally has slightly lower inbox placement rates --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://humanic.gitbook.io/humanic/campaign-execution-and-monitoring/email-deliverability/deliverability-provider.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.