← Back to Cloudflare History
major✓ Resolved

Email Security delivery impacted by Spamhaus listing

CloudflareWed, Aug 12, 2026, 03:04 PM
Status
resolved
Duration
2h 21m
Updates
4
Coverage
0 articles

INCIDENT TIMELINE

✓ ResolvedWed, Aug 12, 2026, 05:25 PM
This incident has been resolved.
monitoringWed, Aug 12, 2026, 04:48 PM
All IPs previously listed by Spamhaus are now clean. Monitoring the propagation of that change to downstream systems.
investigatingWed, Aug 12, 2026, 04:30 PM
We are continuing to investigate this issue. Customers using O365 will be impacted only if they have not completed the required setup. Please check your setup and ensure the connector includes all egress IPs: https://developers.cloudflare.com/cloudflare-one/email-security/setup/pre-delivery-deployment/prerequisites/m365-email-security-mx/#2-configure-enhanced-filtering
investigatingWed, Aug 12, 2026, 03:07 PM
We are continuing to investigate this issue.
investigatingWed, Aug 12, 2026, 03:04 PM
We are currently investigating an issue where customers that use Spamhaus for additional filtering of email downstream from the Cloudflare Email Security service are rejecting emails from IPs in the 134.195.26.0/23 block. This IP block should be allowed for all customer downstream systems to avoid treating the Email Security service as an originator of mail. We recommend all Cloudflare Email Security customers disable Spamhaus filtering in downstream systems.

📊 TECHNICAL DETAILS

Internal ID
b6830dab-d216-45d9-b21a-950c349a96f1
External ID
fdyjr0t87mrb
🕐 Started
Wed, Aug 12, 2026, 03:04 PM
🔄 Last Updated
Wed, Aug 12, 2026, 05:25 PM
✓ Resolved
Wed, Aug 12, 2026, 05:25 PM
MAJOR
Impact Level
2h 21m
Total Duration
4
Status Updates
Affected Components
Email Security (Area1)Email Security (Zero Trust)
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we automatically generate one.
0 / 100 requests100 more needed