SparkPost Status
Real-time updates of SparkPost issues and outages
SparkPost status is Operational
SparkPost Mailbox Provider Service Interruption
Every email you send drives someone to your site - is it converting them?
Outages aren't the only thing that costs you visitors.
Get a visual audit that shows exactly where your site loses conversions.
Free, takes 2 minutes.
Active Incidents
No active incidents
Recently Resolved Incidents
Beginning 2026-08-26 around 23:00 UTC, we are observing a significant increase in hard bounces for messages sent to recipients at privaterelay.appleid.com, the relay domain used by Sign in with Apple. Affected messages are rejected by Apple's mail servers with the SMTP response 550 5.1.1 user not found.
Our investigation confirms this originates upstream at the receiving mailbox provider, not within our platform. Delivery to all other domains, including icloud.com, me.com, and mac.com, remain unaffected and are performing normally. A substantial share of the affected addresses delivered successfully as recently as 2026-08-26, indicating the rejections do not reflect genuine invalid recipients.
Impact: Because these are hard bounces, affected recipient addresses may be automatically added to your suppression list, which will prevent future sends to those recipients even after the underlying issue is resolved.
Action required: None at this time. We recommend you do not attempt to manually clean or re-import affected suppression entries while the issue is ongoing. We are working directly with Apple on a resolution. Once resolved, we will remove suppression entries created by this event and will confirm the scope and timing in a follow-up update.
We will post our next update within 4 hours or sooner if the situation changes.
SparkPost Outage Survival Guide
SparkPost Components
SparkPost Application (WebUI)
SparkPost Application - USA
SparkPost Application - EUROPE
SparkPost SMTP Delivery (Outbound Message Delivery)
SMTP Delivery - USA
SMTP Delivery - EUROPE
SparkPost Transmissions API
Transmissions API - USA
Transmissions API - EUROPE
SparkPost SMTP API
SMTP API - USA
SMTP API - EUROPE
SparkPost Metrics API
Metrics API - USA
Metrics API - EUROPE
SparkPost Events API
Events API - USA
Events API - EUROPE
SparkPost Relay Webhooks Delivery Service
Relay Webhooks - USA
Relay Webhooks - EUROPE
SparkPost Sending Domains API
Sending Domains API - USA
Sending Domains API - EUROPE
SparkPost Suppression List API
Suppression List API - USA
Suppression List API - EUROPE
SparkPost Event Webhook Delivery Service
Event Webhooks - USA
Event Webhooks - EUROPE
SparkPost Engagement Tracking Service
Engagement Tracking Service (redirecting clicks and serving opens) - USA
Engagement Tracking Service (redirecting clicks and serving opens) - EUROPE
SparkPost Mailbox Provider Service Interruption
Beginning 2026-08-26 around 23:00 UTC, we are observing a significant increase in hard bounces for messages sent to recipients at privaterelay.appleid.com, the relay domain used by Sign in with Apple. Affected messages are rejected by Apple's mail servers with the SMTP response 550 5.1.1 user not found.
Our investigation confirms this originates upstream at the receiving mailbox provider, not within our platform. Delivery to all other domains, including icloud.com, me.com, and mac.com, remain unaffected and are performing normally. A substantial share of the affected addresses delivered successfully as recently as 2026-08-26, indicating the rejections do not reflect genuine invalid recipients.
Impact: Because these are hard bounces, affected recipient addresses may be automatically added to your suppression list, which will prevent future sends to those recipients even after the underlying issue is resolved.
Action required: None at this time. We recommend you do not attempt to manually clean or re-import affected suppression entries while the issue is ongoing. We are working directly with Apple on a resolution. Once resolved, we will remove suppression entries created by this event and will confirm the scope and timing in a follow-up update.
We will post our next update within 4 hours or sooner if the situation changes.