Same ESP, Different Country | DMARCeye

The same email service provider can have meaningfully different DMARC compliance rates depending on which country its sending IPs sit in. In our Q1 2026 dataset, Amazon's compliance is 99.8% from US-based IPs and 96.5% from German IPs, a 3.3 percentage-point gap from the same vendor. Microsoft's spread is similar: 96.2% from Ireland but 98.3% from the UK. Google is more uniform but still varies by 1.2 points between India and the US. If your mail flows through one of the big providers, your sender reputation depends in part on a routing decision the provider made for you.

This article unpacks the regional-variance finding from DMARCeye's Q1 2026 industry report. The full report, with all 12 chart views and methodology, is below.

What the Q1 Data Shows by Country

We attributed mail to providers by the network owner of the sending IP, then split each provider's volume by the country its IPs are located in. The top three multi-country providers in Q1 2026, by their compliance spread:

• Amazon · United States: 99.8%
• Amazon · United Kingdom: 98.7%
• Amazon · Germany: 96.5%
• Microsoft · UK: 98.3%
• Microsoft · France: 96.3%
• Microsoft · Ireland: 96.2%
• Google · India: 98.7%
• Google · United States: 97.5%

The widest spread on a single provider is Amazon at 3.3 points (US to Germany). Microsoft sits at 2.1 points (UK to Ireland). Google at 1.2 points is the most uniform of the three. None of these are catastrophic gaps, but for senders running close to the deliverability edge, two or three points can be the difference between mail landing in the inbox and mail drifting to spam.

Why the Same Vendor Varies by Region

The Q1 data shows the variance; it doesn't tell us why any specific country lags or leads. The reasons below are patterns we see across customers, not findings from the dataset:

• Regional IP-block reputation accumulates separately. Mail servers track sender reputation by IP. When a vendor adds capacity in a new region, the new IPs start with a clean slate. Some of that slate fills with legitimate mail; some fills with abuse from customers in the region. Over time, a region's IP pool develops a reputation that's slightly different from the vendor's other regions.
• Customer mix differs by market. Microsoft 365 in Ireland and Microsoft 365 in the UK are the same product, but the customers using them aren't. A region with more SMB customers, more new domains, or more customers who haven't been prompted to set up DKIM, will show lower aggregate authentication rates even if the underlying infrastructure is identical.
• Resellers and data-center pools route differently. Some vendors use distinct outbound IP pools per region. Others share IPs across regions and route based on the customer's account location. The country attribution we use is based on where the IP is registered, which doesn't always match where the sender or receiver is.
• Compliance moves slowly in some regions. Markets where DMARC enforcement adoption is lower will show lower per-region compliance for any vendor with customers in that market. Vendor reputation is partly the vendor's, partly the customer base's.

What This Means for Your Deliverability

If your ESP uses regional IP pools and your account routes through a region with weaker compliance, your mail inherits some of that region's reputation. The practical effects:

• Cold-list send rates may differ silently. A campaign that lands in the inbox at a 95% rate from US IPs and 92% from EU IPs isn't an obvious failure. It's a slow, regional drift you only notice when you slice the data by recipient region.
• New customers on a vendor inherit existing reputation. When you sign up for a provider, you don't pick the IP pool. Your initial deliverability is partly your own account warm-up and partly the regional pool you happen to land in.
• Authentication still matters more than location. Regional variance is a few points. Setting up SPF and DKIM alignment correctly is a 30-point swing. If you're not sure whether your authentication is set up right, the regional question is a distraction. Fix authentication first.

If you're not sure where you stand, check both records now:

How to Find Out Where Your Mail Actually Sends From

The fastest way to see where your real mail is being sent from, by country and by vendor, is to read your DMARC aggregate reports. The reports identify every sending IP, which lets you trace each IP back to its vendor and region. After two to four weeks of reports, you'll have a clear picture of which regions you depend on for which kinds of mail. DMARCeye's free plan covers one domain and collects those reports for you. Most senders discover their mail runs through one or two big vendors; indeed, our Q1 2026 report also shows how Klaviyo and Amazon SES alone sign more than half the mail in our dataset.

If you don't currently have DMARC reports flowing in, the steps are: publish a DMARC record at p=none with a reporting address, wait for reports, then read them. Our complete DMARC implementation guide covers the full path. Google and Yahoo's sender requirements require this anyway for senders above 5,000 messages per day.

The Practical Takeaway

The same vendor with the same product can show different DMARC compliance rates depending on which region's IPs you're routed through. The spread isn't huge, two to three points on the worst case, but for senders living near the deliverability cliff, that's the margin between landing and not landing. The fix is the same fix that solves most authentication problems: read your reports, know which regions you actually depend on, and tighten authentication on every legitimate sender. Regional variance is a real signal but not a primary driver. If your authentication is right, the regional difference is noise. If your authentication is wrong, the regional difference is the least of your problems.