We’re introducing Mailgun alongside SendGrid to improve the reliability of Shipup’s email delivery and help maintain notifications if SendGrid experiences an outage.
What is Mailgun, and why do we use it?
Mailgun is an email delivery provider and a Shipup subprocessor. Shipup will use it to send tracking notifications, carrier notifications and platform emails, such as password resets, tracker digests and reports.
Using two providers reduces our dependency on a single service and helps protect email deliverability. For emails distributed between both providers, regular traffic keeps Mailgun’s sending infrastructure active and ready to handle additional traffic during an incident.
Where is Mailgun headquartered?
Mailgun is headquartered in San Antonio, Texas, United States.
Where is data stored and processed?
Shipup uses Mailgun’s European Union region to store and process email messages and associated delivery data.
What data does Mailgun process?
Mailgun processes recipient email addresses, email subjects and bodies, and the metadata and delivery logs needed to send emails and monitor delivery. Email content may include shopper or merchant information contained in the notification.
Recipient activity is also stored when consent is enabled.
How long is data retained?
For Shipup’s Mailgun configuration:
Email subjects and bodies: retained for 3 days.
Message metadata and delivery logs: retained for 30 days.
What changes for you?
How tracking emails are routed depends on your sender domain:
If you use your own authenticated domain, such as
notifications.brand.com, SendGrid remains your normal provider. If a SendGrid incident occurs, Shipup may temporarily route emails through Mailgun using the sendernoreply@tracking.shipup.coinstead of your usual domain.If you use a default Shipup domain, such as
tracking.shipup.co, tracking emails will be distributed between SendGrid and Mailgun even when there is no incident. Your sender domain remains a Shipup domain.
Carrier notifications and platform emails will also be distributed between both providers.
Do you need to take any action?
No action or DNS changes are required for the configurations described above. Shipup manages the rollout and any provider switch during an incident.
When will this take effect?
The release is planned for 16 November 2026. Traffic distributed between the two providers will be introduced progressively.