Live  /  SparkPost  /  Incident

SparkPost: Increased message delays in US and EU due to DNS resolution errors

SparkPost · sparkpost.comMinor incidentResolved2026-10-11 20:57 UTC
Public — what happened

Summary

SparkPost reported that some outgoing email in its US and EU regions was being held up and delivered late, with the problem beginning around 14:40 UTC on October 11, 2026. The company said messages were not lost or rejected, but customers might see more delay events than usual in their webhooks, logs and reports. SparkPost said the cause was a validation problem on part of its internal DNS systems tied to a scheduled change in the internet's root DNS signing key, and it rolled out the updated keys. A fix was in place by 18:17 UTC, and the incident was marked resolved at 20:57 UTC.

Affected

SMTP Delivery - USA, SMTP Delivery - EUROPE

As listed on SparkPost’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach SparkPost against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for SparkPost: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the SparkPost report →

More from SparkPost

Covered in The Squid’s Ink, Week 42, 2026, our weekly internet health report.

The full archive is on the SparkPost status & history page.

Related: SparkPost status & history. SquidGrid is not affiliated with SparkPost.